Hi, On Thu, Dec 29, 2016 at 04:12:06PM -0500, Selva Nair wrote: [..] > But to test this bug report I did use the same adapter (still using > --dev-node adapter-name..) and changed the remote and couldn't reproduce > it. But I do see something similar as this report (DHCP fails to set IP) if > I remove the --dev-node line and let it pick an adapter that was previously > used with a different IP. Can't reproduce it consistently, though.
But it seems we have some work to do here...
Maybe "--ip-win32 ipapi" is the answer?
(How do we set IPv4 addresses if the iservice is in use? Still using
DHCP, or always? sometimes? via iservice / ipapi? I never cared too much
for v4 and am too lazy to look right now, apologies :-) )
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
