On Wed, Dec 28, 2016 at 10:07 PM, Dmitry Melekhov <[email protected]> wrote:
> On Wed, Dec 28, 2016 at 1:43 AM, Dmitry Melekhov < <[email protected]>
> [email protected]> wrote:
>
>> Just installed 2.4 on windows 7.
>>
>> Connecting to on server, tun is set to, let's say to 10.1.10.6,
>>
>> everything is fine.
>>
>> Disconnect.
>>
>> Change remote in config, connect to another server,
>> tun address should be 192.168.31.6, gui says so,
>>
>> but real address on tun is 10.1.10.6.
>>
>>
>> Reboot solves problem, but on next connection sequence it is reproduced.
>>
>
>
> I tried to reproduce this but fortunately no luck :)
>
> As Gert said, logs please. Also please include an output of ipconfig /all
> showing the settings on tun adapters with each connection up.
>
> I sent logs to Gert already...connection
>
> but, afair, only failed connection..
This rings a bell. I've seen connection failures in the past when the same
tap adapter is used with different remotes in a succession. The connection
fails with something like repeated "TEST ROUTES: 0/0 succeeded len=-1 ret=0
a=0 u/d=down" which indicates setting IP by dhcp didn't succeed. Without
logs, not sure that's what you are seeing, though.
Never seen it lately as I now use explicitly named dev nodes (--dev-node
name option) so that each connection uses a fixed adapter node. And no idea
why it happens. Could be tap-driver related so someone else may have a clue.
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
