Page 1 of 1

WIFI routing problem

Posted: Wed Aug 28, 2013 10:48 am
by soulianis
Hello all,

I have OpenVPN Connect 1.0.1 working fine on iPhone 5 with iOS 6.1.4, but there is one problem that occurs "sometimes" (sorry but I cannot describe it better, thank you for your patience).

I use an OpenVPN tcp server configuration which pushes a route to my internal company network:

Code: Select all

proto tcp
...
push "route AAA.BBB.CCC.DDD 255.255.255.0"
The server address is in a different network, like:

Code: Select all

local WWW.XXX.YYY.ZZZ
All works fine until I enter my company building so that the WIFI connects. At that moment, the iPhone is assigned an address covered by the route pushed by the OpenVPN server. As a consequence, OpenVPN Connect on the iPhone gets a connection timeout and stops the connection. The OpenVPN Connect client log stops with the message "EVENT: DISCONNECT_PENDING".

Now what "sometimes" happens is that the iPhone no longer has network connectivity at all, that is, the "WIFI connected" symbol is displayed but Safari or Email no longer work (activity wheel spins forever).

To cure that I need to disable and re-enable WIFI or enter and leave flight mode or do a warm reboot.

Also, when leaving the company building OpenVPN does not automatically reconnect.

Does somebody here know a solution?

Here is my OpenVPN Connect client configuration on the iPhone:

Code: Select all

client
dev tun
proto tcp
remote ovpn.XXXXXXXXX.com 1194
resolv-retry infinite
nobind
user nobody
group nobody
persist-key
persist-tun
cipher BF-CBC
comp-lzo
verb 3
<ca>
...
</ca>
<cert>
...
</cert>
<key>
...
</key>
Thank you very much for your help!

Re: WIFI routing problem

Posted: Thu Aug 29, 2013 2:07 pm
by soulianis
What I forgot to mention:
My private key is passphrase-protected. Could that be the reason that OpenVPN Connect on iOS does not automatically reconnect when leaving the company WIFI area, after it got a connection timeout?

Re: WIFI routing problem [solved]

Posted: Fri Aug 30, 2013 9:14 am
by soulianis
Setting the Connection Timeout parameter to none appears to have solved the problems.

Sorry for all the trouble. :oops: