On 02/03/2021 19:18, tincanteksup wrote:
Ok,
it seems i misunderstood the problem, so I'll start over.
See this forum thread for full details:
https://forums.openvpn.net/viewtopic.php?f=6&t=31945#p98073
But in summary:
My first mistake was not understanding the use of AF_INET6.
I now understand that AF_INET6 will/does work for IPv4 also.
The log in this post shows that --proto udp leads to the same log line:
`Could not determine IPv4/IPv6 protocol. Using AF_INET6`
and the VPN still works using only IPv4.
https://forums.openvpn.net/viewtopic.php?f=6&t=31945#p98106
So what was the problem then ?
It appears a Windows Update has interfered in DHCP somehow.
(There have been two reports on the forum which look the same)
The solution to this problem was to use --dhcp-renew in the
config to force DHCP renewal. No other steps worked.
eg. --route-delay 60 60 did not help.
My question now is:
Is it possible for openvpn to detect that DHCP has failed
and to error out immediately ?
Otherwise, the user is left thinking that their VPN is working
and they can even connect to it and receive their client IP but
the server is completely non-functional and only a minor indication in
the log as to the reason.
Thanks
Both users were using the GUI, so is it possible that the GUI could
handle this error ?
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
