On Tue, Nov 17, 2015 at 1:03 PM, Gert Doering <g...@greenie.muc.de> wrote: > Why are you seeing AF_UNSPEC there? This is actually more interesting > to me right now than debating possible avenues to fix this :-)
I also see: "Could not determine IPv4/IPv6 protocol. Using AF_INET" in the logs (which points in an quite explicative conditional in socket.c). The configuration entries that might affect this and that are present in my configuration are: local [IPv4 address] lport 443 mode server proto udp server [IPv4 subnet] topology subnet and this happens on a host where I configured just IPv4 (even if the host itself is dual homed). Interestingly, if I configure full IPv6, i.e. I add: local [IPv6 address] proto udp6 server [IPv6 netblock] the problem (and of course above message) goes away. I mistakenly assumed that seeing AF_UNSPEC is OK (from various comments when you grep for AF_UNSPEC). If you think the root of all evil is this value, I will dig further. Thanks!
