On Thu, Dec 29, 2016 at 11:34 PM, Dmitry Melekhov <[email protected]> wrote:
> 30.12.2016 00:46, Gert Doering пишет:
> > Now I'm not sure why that happens - windows should completely forget
> > the DHCP lease when the first OpenVPN connection ends. But then,
> > Windows...
>
It won't forget the lease, but should try to renew it and fail (and thus
get a new address) when state changes from media disconnected to connected.
>
> Afaik, it perfectly works with all previous, i.e. before 2.4 versions,
> at least nobody here complained.
>
> I'm not windows user and have no windows installed, and my colleague , I
> asked to test 2.4 on windows is absent for next several days, so
> I can't do more tests, but, for me it looks like tap driver problem.
>
> btw, in our setup this is very important, because we have 2 servers and
> one name, i.e.
> users can randomly connect to one of them and get different ip address...
>
>
On further testing this looks different from the similar looking error I
posted (also see Trac #807)
<https://community.openvpn.net/openvpn/ticket/807>
Tell-tale signs of what I reported are:
(i) there are more than one tap adapters on the system
(ii) when the connection completes without assigning an ip address, the
output of "netsh int ip show addr" shows a disconnected adapter holding the
ip address that openvpn was trying to assign to another.
(iii) manually assigning the ip to the adapter like
netsh int ip set addr "adapter name" static 192.168.31.6 255.255.255.0
192.168.31.1
fails with object already exists error
Selva
------------------------------------------------------------------------------
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
