Hi, On Tue, Nov 17, 2015 at 01:43:50PM +0000, Christian Pellegrin wrote: > 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
I had the suspicion that this happens for the server side - "proto udp"
is the giveaway, as it will pass AF_UNSPEC to getaddrinfo() to get
"what is needed for dual-stack" (which does not always work, but that's
a different story). So, starting out with AF_UNSPEC is good, but the
actual socket later on isn't (it is what getaddrinfo() returns)...
The client side should be sorted out quite nicely now, but seems the
server side could need some more polishing - so thanks for your patch,
and since it already got an ACK by our master of socket.c, I'll merge
it ASAP.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
