I think the VPN software is way too touchy.
Seems that way. I rebooted the computer and tried again. This time, got the inactivity error and disconnect like before.
So the Media State setting is not relevant it seems.
Most have a idle timeout as part of the security features, it prevents VPN data replay and MITM attacks on VPN tunnels, disable it or increase the timeout setting.
In terms of a lease, see end of this line :
Dec 30 04:38:40: Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.179.13/255.255.255.252 on interface {7705A231-89E9-48A1-B0BC-289AFC23A14D} [DHCP-serv: 192.168.179.14,
lease-time: 31536000]
I do not know what that number equates too, however there's a few things to consider.
A) On this machine, I haven't any disconnects like that - yet the VPN settings are the same.
B) The client has an option to disconnect clients after XX amount of time. That feature is not checked.
I wish it was that simple!
Here's all the client options:
There's a comment elsewhere that reads :
The restart is occuring because a keepalive ping was not received during
the required time interval.
This usually happens because of short-term network outages. You can make
OpenVPN less sensitive to network outages by using a large keepalive
timeout. For example,
keepalive 10 600
will send a ping every 10 seconds, but only restart if a ping hasn't been
received from the peer for 10 minutes.
Also appended with :
I’ve been seeing bizarre problems with my openvpn client (on linux) over the last couple of days. It would connect, and I could access the network, but the VPN would regularly restart itself and connections would be closed, seeing messages like
Tue May 22 13:19:43 2012 [OpenVPN_Server] Inactivity timeout (--ping-restart), restarting
Tue May 22 13:19:43 2012 TCP/UDP: Closing socket
I saw these problems when I tried my profile on several different computers.
I was unable to find anything on the internet about this (possibly my google fu was weak), but we’ve finally managed to track down the problem. I thought I’d put this here in case other people had the same issue.
This seems to happen when you’re running two openvpn clients with the same profile from different computers. I have two computers I use, and I’d left one idle running the VPN client. When I then tried to connect to the VPN from the other computer I would see this behaviour. I then (foolishly) left that computer trying to use the VPN when I went back to the first computer, so now the problem had mysteriously appeared there too.
http://serverfault.com/questions/104154/why-is-duplicate-cn-not-recommended-in-openvpn
Might be on to something, but the first computer and the Android device are never affected by the status of the second computer.