Hi, Agreed! Fix the underlying problem, don't put a band-aid on it ... ;-). So do we start from the TAP adapter, which seems to "fail" first, then there is a ripple effect? Or look at OpenVPN - should it really exit, or just report TAP not present, and keep trying to reconnect (would address standby / resume)?
Thoughts? Thanks, ... Russell -----Original Message----- From: David Sommerseth [mailto:open...@sf.lists.topphemmelig.net] Sent: Wednesday, October 28, 2015 6:15 AM To: Gmail <volleynb...@gmail.com>; Selva Nair <selva.n...@gmail.com> Cc: openvpn-devel@lists.sourceforge.net Subject: Re: [Openvpn-devel] Topics for today's (Monday, 26th Oct 2015) community meeting On 27/10/15 07:07, Gmail wrote: > On Oct 26, 2015, at 8:41 AM, Selva Nair <selva.n...@gmail.com > <mailto:selva.n...@gmail.com>> wrote: > >> >> On Mon, Oct 26, 2015 at 11:17 AM, Gmail <volleynb...@gmail.com >> <mailto:volleynb...@gmail.com>> wrote: >> >> Regarding the instability of connection in the windows version: I >> overcame this long ago (and works well to this date) by building a >> tiny script that periodically pings the the ovpn gateway (server). >> If no ping reply then restart the service. Very simple. Perhaps >> this could be built into the code as an option? >> >> >> Oh, please, no... If the TAP driver has stability woes it needs to be >> fixed. True loss of network connectivity is already handled by >> internal pings and ping-restarts. It would be a grave mistake to add >> such options to hide any stability issues. >> >> Cheers, >> >> Selva >> > Your concern is understood and acknowledged. Perhaps the ping-restart > idea is useful in the interim until the cause is located? This will work in regards to ensure that openvpn client and server will have a working connection. Configuring OpenVPN with --ping/--ping-restart (or the --keepalive "macro", which does it even better), is generally recommended and is the best way to provide a more "stable" VPN experience. If anything happens with the TAP driver, OpenVPN will not re-initialize the TAP adapter - thus OpenVPN should stop running. When the TAP driver have an issue, it is just like your Ethernet or WIFI driver have an issue. If the TAP adapter "disappears", it's just like unplugging your network adapter in your computer, in these situations OpenVPN should really stop. So I do agree with Selva, if there are stability issues with the TAP driver, those issues should be fixed in the driver. If there are things outside of OpenVPN or the TAP driver which does funky stuff, that should as far as possible be fixed there. -- kind regards, David Sommerseth
