From d97943e983f9ae9c48cfc2c6084bfec5049189e2 Mon Sep 17 00:00:00 2001 From: Arne Schwabe Date: Fri, 26 Oct 2012 14:41:24 +0200 Subject: - Increase Version - Add FAQ Entry for energy consumption --- res/values/strings.xml | 2 ++ 1 file changed, 2 insertions(+) (limited to 'res/values/strings.xml') diff --git a/res/values/strings.xml b/res/values/strings.xml index 69fb9e35..a0d1a4f0 100644 --- a/res/values/strings.xml +++ b/res/values/strings.xml @@ -227,4 +227,6 @@ Translation OpenVPN Log Import OpenVPN configuration + Battery consumption + In my personal tests the main reason for high battery consumption of OpenVPN are the keepalive packets. Most OpenVPN servers have a configuration directive like \'keepalive 10 60\' which translates to a keepalive packet from client to server and server to client every ten seconds. <p> While these packets are small and do not use much traffic, they keep the mobile radio network busy and increase the energy consumption. <p> This keepalive setting cannot be changed on the client. Only the system administrator of the OpenVPN can change the setting. <p> Unfortunatly using a keepalive larger than 60 seconds with udp has problems with some NAT gateways which terminate the state for a connnection after a short timeout (60s in my tests). Using TCP with long keepalive timeout works but has the TCP over TCP problem. (See <a href=\"http://sites.inka.de/bigred/devel/tcp-tcp.html\">Why TCP Over TCP Is A Bad Ide</a>) -- cgit v1.2.3