* Gert Doering > I *thought* that both proto udp and proto udp6 would create an IPv6 socket > bound to :: with IPV6_V6ONLY set to 0 (= accepting IPv4 and IPv6 packets > to any address). Only "proto udp4" should listen to 0.0.0.0.
This is not how git master behaves for me. "proto udp" and "proto udp4" both yield an IPv4-only socket (AF_INET): tore@greed:~$ sudo lsof -i :1194 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME openvpn 31739 nobody 5u IPv4 19461864 0t0 UDP *:openvpn Only "proto udp6" yields an dual-stacked socket (AF_INET6 + !IPV6_V6ONLY), but I cannot use this because "multihome" fails for IPv4 clients (which are the majority of my users). tore@greed:~$ sudo lsof -i :1194 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME openvpn 32126 nobody 5u IPv6 19464798 0t0 UDP *:openvpn FWIW, "proto tcp-server" also yields an IPv4-only socket. "proto tcp6-server" works (also for IPv4 clients). > Now, --multihome is a different issue - I accept that this isn't working > right in various scenarios, and we need to fix this. But at least dual- > stacked servers with "proto udp" are expected to work. Per the above, I cannot see that it does... I can submit a separate bug report about this if you wish. That said, I would be perfectly happy to simply use "proto udp6" instead, IFF "multihome" had worked correctly. Tore
