Eduard Bloch <e...@gmx.de> writes: > #include <hallo.h> > * Marco d'Itri [Fri, Dec 11 2009, 12:23:36AM]:
>> There is no relevant standard that says what the default of IPV6_V6ONLY >> should be. Currently what happens is that every OS except Linux and OS >> X default to 1. An important point is that the kfreebsd ports only >> support a default of 1, so these buggy programs need to be fixed anyway >> to work correctly on them. > From my POV as programmer it's a good change. The old behaviour (i.e. > silent creation of v4 mapped sockets) maybe made the porting (to > Linux/OS-X) of very simple network daemons easier but when you tried to > make the local address binding more flexible then things became PITA. Agreed. > I.e. if you use getaddrinfo output then you need to sort out v6 sockets > out and connect on them, but then you cannot be sure about whether v4 > mapping is active. You can test it by trial-and-error (binding on v4 > versions and checking the results) but then you cannot be sure that they > are bound to you now (at least not without using ugly tricks). Yes, exactly. You end up having to add a bunch of code to special-case IPv4-mapped addresses in annoying ways, and that code isn't always tested because other OSes don't do this dual-binding. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
