AirVPN over TOR using LINUX gives Inactivity timeout

[Db9cBuC9 1]

Hello,

I am accessing the internet via a LAN and router. I started TOR then AirVPN on my Windows7 laptop and it works perfectly. I then tried it on my OpenSUSE Linux box and it drops out with an inactivity timeout:-

Wed Apr 10 11:10:10 2013 Initialization Sequence Completed

Wed Apr 10 11:11:10 2013 [server] Inactivity timeout (--ping-restart), restarting

Wed Apr 10 11:11:10 2013 TCP/UDP: Closing socket

Wed Apr 10 11:11:10 2013 /bin/ip route del 10.5.0.1/32

Wed Apr 10 11:11:10 2013 /bin/ip route del 127.0.0.1/32

Wed Apr 10 11:11:10 2013 /bin/ip route del 0.0.0.0/1

Wed Apr 10 11:11:10 2013 /bin/ip route del 128.0.0.0/1

Wed Apr 10 11:11:10 2013 Closing TUN/TAP interface

Wed Apr 10 11:11:10 2013 /bin/ip addr del dev tun0 local 10.5.1.166 peer 10.5.1.165

Wed Apr 10 11:11:10 2013 SIGUSR1[soft,ping-restart] received, process restarting

Wed Apr 10 11:11:10 2013 Restart pause, 5 second(s)

Wed Apr 10 11:11:15 2013 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables

Wed Apr 10 11:11:15 2013 LZO compression initialized

Wed Apr 10 11:11:15 2013 Control Channel MTU parms [ L:1560 D:140 EF:40 EB:0 ET:0 EL:0 ]

Wed Apr 10 11:11:15 2013 Socket Buffers: R=[87380->131072] S=[16384->131072]

Wed Apr 10 11:11:15 2013 Data Channel MTU parms [ L:1560 D:1450 EF:60 EB:135 ET:0 EL:0 AF:3/1 ]

Wed Apr 10 11:11:15 2013 Local Options hash (VER=V4): '958c5492'

Wed Apr 10 11:11:15 2013 Expected Remote Options hash (VER=V4): '79ef4284'

Wed Apr 10 11:11:15 2013 Attempting to establish TCP connection with 127.0.0.1:9150 [nonblock]

Wed Apr 10 11:11:15 2013 TCP connection established with 127.0.0.1:9150

Wed Apr 10 11:11:20 2013 recv_socks_reply: TCP port read timeout expired: Operation now in progress (errno=115)

Wed Apr 10 11:11:20 2013 TCP/UDP: Closing socket

Wed Apr 10 11:11:20 2013 SIGTERM[soft,init_instance] received, process exiting

Any ideas as to what is going wrong here would be gratefully appreciated.

[Staff 9972]

Hello!

It looks like a known OpenVPN 2.1 and 2.2 bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657964

This bug shows up only under very particular circumstances (we are unable to reproduce it on many systems we have tried), as you can read. If possible, try on your OpenSUSE to upgrade to OpenVPN 2.3.

Kind regards

[p4T4toR 0]

I have the same problem,

 

I am using OpenVPN 2.3.2 (I compiled it) on a raspberry pi where Tor v0.2.3.25 is running.

 

Here is the log (just the part after the initial connection, when it fails) :

Mon Jul  8 08:01:30 2013 Initialization Sequence Completed
Mon Jul  8 08:02:32 2013 [server] Inactivity timeout (--ping-restart), restarting
Mon Jul  8 08:02:32 2013 /sbin/route del -net 10.5.0.1 netmask 255.255.255.255
Mon Jul  8 08:02:32 2013 /sbin/route del -net 127.0.0.1 netmask 255.255.255.255
Mon Jul  8 08:02:32 2013 /sbin/route del -net 0.0.0.0 netmask 128.0.0.0
Mon Jul  8 08:02:32 2013 /sbin/route del -net 128.0.0.0 netmask 128.0.0.0
Mon Jul  8 08:02:32 2013 Closing TUN/TAP interface
Mon Jul  8 08:02:32 2013 /sbin/ifconfig tun0 0.0.0.0
Mon Jul  8 08:02:32 2013 SIGUSR1[soft,ping-restart] received, process restarting
Mon Jul  8 08:02:32 2013 Restart pause, 5 second(s)
Mon Jul  8 08:02:37 2013 Socket Buffers: R=[87380->131072] S=[16384->131072]
Mon Jul  8 08:02:37 2013 Attempting to establish TCP connection with [AF_INET]127.0.0.1:9050 [nonblock]
Mon Jul  8 08:02:37 2013 TCP connection established with [AF_INET]127.0.0.1:9050
Mon Jul  8 08:02:42 2013 recv_socks_reply: TCP port read timeout expired: Operation now in progress (errno=115)
Mon Jul  8 08:02:42 2013 SIGTERM[soft,init_instance] received, process exiting

do you have some ideas on what I shoudl try to solve this problem ?

[Staff 9972]

Hello,

 

at a first glance it looks like an old bug which is still unresolved:

 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657964

 

Kind regards

[core901 0]

Hello.

 

Thanks to the AirVpn support staff that helped me to AirVpn over Tor setup.

 

But now I have this "Inactivity timeout" problem.

 

My os Xubuntu 13.10 updated

OpenVpn version 2.3.2 i686-pc-linux-gnu

Tor Browser version 3.5.4-Linux

 

Here is the log:

 

Sun Apr 27 09:24:31 2014 Initialization Sequence Completed
Sun Apr 27 09:25:30 2014 [server] Inactivity timeout (--ping-restart), restarting
Sun Apr 27 09:25:30 2014 SIGUSR1[soft,ping-restart] received, process restarting
Sun Apr 27 09:25:30 2014 Restart pause, 5 second(s)
Sun Apr 27 09:25:35 2014 Socket Buffers: R=[87380->131072] S=[16384->131072]
Sun Apr 27 09:25:35 2014 Attempting to establish TCP connection with [AF_INET]127.0.0.1:9150 [nonblock]
Sun Apr 27 09:25:35 2014 TCP connection established with [AF_INET]127.0.0.1:9150
Sun Apr 27 09:25:40 2014 recv_socks_reply: TCP port read timeout expired: Operation now in progress (errno=115)
Sun Apr 27 09:25:40 2014 /sbin/ip route del 10.5.0.1/32
Sun Apr 27 09:25:40 2014 /sbin/ip route del 127.0.0.1/32
Sun Apr 27 09:25:40 2014 /sbin/ip route del 0.0.0.0/1
Sun Apr 27 09:25:40 2014 /sbin/ip route del 128.0.0.0/1
Sun Apr 27 09:25:40 2014 Closing TUN/TAP interface
Sun Apr 27 09:25:40 2014 /sbin/ip addr del dev tun0 local 10.5.8.202 peer 10.5.8.201
Sun Apr 27 09:25:40 2014 SIGTERM[soft,init_instance] received, process exiting
root@......:/home/............................#

 

Is there somone that knows if this bug/problem is resolved? Or how can I solve it?

 

Thanks.

 

Kind Regards

[iwih2gk 93]

FYI

 

Going the other way; TOR over Air on Linux is working perfectly.  I use 7 on some systems and Linux on several others.  Never an issue with a reversed order.  Didn't want to splinter your thread, just mention that TOR in this fashion is perfect.

[Staff 9972]

Hello.

 

Thanks to the AirVpn support staff that helped me to AirVpn over Tor setup.

 

But now I have this "Inactivity timeout" problem.

 

My os Xubuntu 13.10 updated

OpenVpn version 2.3.2 i686-pc-linux-gnu

Tor Browser version 3.5.4-Linux

 

Here is the log:

 

Sun Apr 27 09:24:31 2014 Initialization Sequence Completed

Sun Apr 27 09:25:30 2014 [server] Inactivity timeout (--ping-restart), restarting

Sun Apr 27 09:25:30 2014 SIGUSR1[soft,ping-restart] received, process restarting

Sun Apr 27 09:25:30 2014 Restart pause, 5 second(s)

Sun Apr 27 09:25:35 2014 Socket Buffers: R=[87380->131072] S=[16384->131072]

Sun Apr 27 09:25:35 2014 Attempting to establish TCP connection with [AF_INET]127.0.0.1:9150 [nonblock]

Sun Apr 27 09:25:35 2014 TCP connection established with [AF_INET]127.0.0.1:9150

Sun Apr 27 09:25:40 2014 recv_socks_reply: TCP port read timeout expired: Operation now in progress (errno=115)

Sun Apr 27 09:25:40 2014 /sbin/ip route del 10.5.0.1/32

Sun Apr 27 09:25:40 2014 /sbin/ip route del 127.0.0.1/32

Sun Apr 27 09:25:40 2014 /sbin/ip route del 0.0.0.0/1

Sun Apr 27 09:25:40 2014 /sbin/ip route del 128.0.0.0/1

Sun Apr 27 09:25:40 2014 Closing TUN/TAP interface

Sun Apr 27 09:25:40 2014 /sbin/ip addr del dev tun0 local 10.5.8.202 peer 10.5.8.201

Sun Apr 27 09:25:40 2014 SIGTERM[soft,init_instance] received, process exiting

root@......:/home/............................#

 

Is there somone that knows if this bug/problem is resolved? Or how can I solve it?

 

Thanks.

 

Kind Regards

 

Hello!

 

It is an OpenVPN bug (see also the message just above your one in this very same thread). The bug is still unresolved  https://community.openvpn.net/openvpn/ticket/328

 

OpenVPN gives up instead of retrying and this causes the problem you experience which is triggered by high latency proxy. An allegedly working patch has been published (it's linked in a comment published in the page in its turn linked above) but it has not been inserted in OpenVPN code. Maybe we might try to re-compile OpenVPN with this patch, we're not sure, we'll be thinking about it.

 

Kind regards

[zhang888 1066]

Dear AirVPN team,

 

Please consider using a lower ping-restart values on your generated configs when the "Tor" checkbox is selected, I think 30 seconds would be a perfect value for most Tor relays.

The default OpenVPN value is 120 seconds, which is not very suitable for many Tor connections.

 

In fact, Visvosity were the first ones to notice that issue and suggest a working fix:

 

https://www.sparklabs.com/support/error_inactivity_timeout_ping_restart/

 

The ping and ping-restart values on the server or client (or both) are invalid or don't match. For example, if the server only sends a ping every 120 seconds, but the client expects a ping every 60 seconds, the connection will be dropped (even through it is still active and working). You should contact your VPN Provider in this instance to find out the correct ping/ping-restart values to use.