Hi,
(copying in openvpn-users again, others might have more insight as I'm not
really using Windows very much)
On Wed, Dec 28, 2016 at 03:53:18PM +0400, Dmitry Melekhov wrote:
> This is second connection, at first adapter got address 192.168.31.6
This is an interesting problem indeed. OpenVPN tells the tap driver
what to do wrt DHCP, and it just does not "arrive" on the windows side...
[..]
> Wed Dec 28 10:38:54 2016 Set TAP-Windows TUN subnet mode
> network/local/netmask = 10.1.10.0/10.1.10.6/255.255.255.0 [SUCCEEDED]
> Wed Dec 28 10:38:54 2016 Notified TAP-Windows driver to set a DHCP IP/netmask
> of 10.1.10.6/255.255.255.0 on interface
> {BE794D53-798C-40DC-8B64-4CE37589133F} [DHCP-serv: 10.1.10.254, lease-time:
> 31536000]
So, we tell the tap driver what to do.
[..]
> SYSTEM ADAPTER LIST
> TAP-Windows Adapter V9
> Index = 18
> GUID = {BE794D53-798C-40DC-8B64-4CE37589133F}
> IP = 192.168.31.6/255.255.255.0
... but Windows just ignores this.
Now I'm not sure why that happens - windows should completely forget
the DHCP lease when the first OpenVPN connection ends. But then,
Windows...
Are you using the interactive service, and running OpenVPN from the
GUI? If not, you should :-)
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]
------------------------------------------------------------------------------
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
