On 28/02/2021 21:13, Gert Doering wrote:
Hi,
On Sun, Feb 28, 2021 at 08:02:54PM +0000, tincanteksup wrote:
Clearly, this is no longer the place to ask.
thanks .....................................
Ask, always.
Claim "this is a bug", only if you can back this by more than "oh,
this log line is confusing me".
The context of that log line is complex - socket.c, link_socket_init_phase2(),
and it basically means "local bind, no address family specified, no
--remote known yet, need to choose a protocol for the actual bind() call".
Since IPv6 sockets can handle dual-stack connections, this is what we
do if we do not know yet if the other end is IPv4 or IPv6, and no protocol
is forced ("udp4" or "udp6").
I resubmit this as a genuine bug:
* Openvpn should error out on the rare occasions that it cannot select
the correct protocol, with an error directing the use of v4 or v6.
Openvpn should not proceed to fail.. without error.
I also point you to the documentation:
https://github.com/OpenVPN/openvpn/blob/3338f2d5a2b7f12f314cc53bf0eaa44ba4f2e58c/sample/sample-config-files/server.conf#L34
my2c
Claiming "bug!" without asking or looking into the code first might
cause... not-very-verbose reactions... from developers that might want
to spend their time fixing real bugs.
gert
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
