openvpn-devel Mailing List for OpenVPN

Hi, On Mon, Mar 7, 2016 at 3:04 AM, Gert Doering <ge...@gr...> wrote: > > Then its only register-dns that remains... > > Yep. Its semantics are not totally clear to me (the code does more, like > turn off dns cache off/on) and I have no idea whether there's a real API > for that... Yes, it does much more than "ipconfig /registerdns": it restarts dns service, flushes the dns cache, and then does registerdns. Looks like someone decided to throw everything at it. In my own very limited tests I've never seen anything more than registerdns needed to get the DNS server registered. In fact, a manual "dhcp /renew" after the connection comes up also appears to do the job: this is not the same as the --dhcp-renew option, though. But I haven't tested any of this beyond a single windows 7 machine, so cant say for use that ipconfig /registerdns or dhcp renew is enough. Considering that many folks appear to be dependent on this option, we have to keep it as is, I guess. AFAIK, there is no API for either of these. There are some undocumented calls like DnsFlushReseolverCache in dnsapi.dll but there are no official docs on them. The service can be started and restarted using API but its no less pain than using "net stop" and "net start" I suppose we need to just queue this request to the service and let it do it asynchronously in a separate thread. Which is not very unlike the current fork_to_self approach. It shouldn't be hard to add that to interactive.c Selva 

----- Original Message ----- From: "Arne Schwabe" <ar...@rf...> To: "Selva Nair" <sel...@gm...>; "Debbie Tent" <deb...@gm...> Cc: <ope...@li...>; <ope...@li...> Sent: Monday, March 07, 2016 3:40 PM Subject: Re: [Openvpn-devel] Samsung Galaxy S6 to android 6.0.1 powersave > > > Am 07.03.16 um 16:28 schrieb Selva Nair: >> Hi, >> >> On Mon, Mar 7, 2016 at 9:55 AM, <deb...@gm... >> <mailto:deb...@gm...>> wrote: >> >> An interesting tid-bit about Samsung Galaxy S6 to android 6.0.1 >> and OpenVPN Connect >> >> https://forums.openvpn.net/post59478.html#p59478 >> >> >> Sounds, suspiciously similar to the sleep-resume issue we had on >> windows.. The interface probably suspends and openvpn exits? >> > In this case that is again some Samsung "optmization". If there is one > manufacture of Android that consistently breaks things it is Samsung. I > have no idea what new idea they now had to break the VPNService when > combined with powersaving features or if OpenVPN Connect is doing > something wrong but normally the app is notified by an onRevoke call > before the tun device is closed. > > Arne > I just thought it was interesting that somebody found *a* solution to what seems to be a common problem and it was worth letting ppl here know. regards 

 Am 07.03.16 um 16:28 schrieb Selva Nair: > Hi, > > On Mon, Mar 7, 2016 at 9:55 AM, <deb...@gm... > <mailto:deb...@gm...>> wrote: > > An interesting tid-bit about Samsung Galaxy S6 to android 6.0.1 > and OpenVPN Connect > > https://forums.openvpn.net/post59478.html#p59478 > > > Sounds, suspiciously similar to the sleep-resume issue we had on > windows.. The interface probably suspends and openvpn exits? > In this case that is again some Samsung "optmization". If there is one manufacture of Android that consistently breaks things it is Samsung. I have no idea what new idea they now had to break the VPNService when combined with powersaving features or if OpenVPN Connect is doing something wrong but normally the app is notified by an onRevoke call before the tun device is closed. Arne 

Hi, On Mon, Mar 7, 2016 at 9:55 AM, <deb...@gm...> wrote: > An interesting tid-bit about Samsung Galaxy S6 to android 6.0.1 > and OpenVPN Connect > > https://forums.openvpn.net/post59478.html#p59478 > Sounds, suspiciously similar to the sleep-resume issue we had on windows.. The interface probably suspends and openvpn exits? Brings up an interesting question: should power events be handled by openvpn or by the UI or in a service that starts it (if relevant)? My view: although openvpn need not directly handle power events, if an interface driver notifies that it wants to suspend, it should respond to it appropriately by restarting after a pause, for example. On windows, our workaround for a long time was for the GUI to suspend/restart openvpn on power events, though we changed that a while ago to put the onus of restarting back on to openvpn. But one could argue that its the job of the process starting openvpn to respawn it if needed, instead of making it handle all kinds of failure scenarios... Any thoughts on which is a better approach? Selva 

FYI: An interesting tid-bit about Samsung Galaxy S6 to android 6.0.1 and OpenVPN Connect https://forums.openvpn.net/post59478.html#p59478 regards 

Hi, On Sun, Mar 06, 2016 at 05:03:21PM -0500, Selva Nair wrote: > Oh, I missed that. Based on the Trac ticket (#71) discussion on fatal error > after sleep-resume, which was apparently caused by netsh failures treated > as FATAL, and seeing some comments that ipv6 setup needs to use netsh > command, I just assumed this is not done. Sorry for jumping into that > conclusion. Trac#71 is way before iservice was even on the horizon :-) - and yes, OpenVPN itself only uses netsh.exe today, "because this is all I had, back then on Windows XP". When discussing iservice and IPv6, we decided "back then" that iservice should not care about WinXP - because we do not have the permission issues on XP anyway (it wasn't clear back then whether OpenVPN 2.4 would support XP or not, but we decided that we do not need XP support in the iservice). > Then its only register-dns that remains... Yep. Its semantics are not totally clear to me (the code does more, like turn off dns cache off/on) and I have no idea whether there's a real API for that... gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany ge...@gr... fax: +49-89-35655025 ge...@ne...