I have send this message to BTS and rejected. m...@linux.it (Marco d'Itri) writes: >> Default value of net.ipv6.bindv6only should revert to 0. > This has already been discussed on debian-devel and I do not see any new > arguments here.
I have already read debian-devel archive, but I was not able to found necessity to change default value of net.ipv6.bindv6only to 1. Anyone, could you teach me why net.ipv6.bindv6only need to be set to 1 globally, and why other good programs need to be changed? I think it should revert. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576633 ----------------------------------------------------------- Default value of net.ipv6.bindv6only should revert to 0. 1. RFC 3493 explicitly allows applications to use AF_INET6 socket to receive IPv4 connection. 2. If some applications want to restrict their use of an AF_INET6 socket to IPv6 communications only, they can use IPV6_V6ONLY. It is effective even if net.ipv6.bindv6only is 0. (In addition, RFC 3493 explicitly says IPV6_V6ONLY is turned off (0) by default.) 3. Default value of net.ipv6.bindv6only is 0 in Linux kernel and other Linux distributions. We should never introduce such meaningless incompatibility. If an application does not work with net.ipv6.bindv6only = 1, it does not mean that program is broken. But if an application does not work with net.ipv6.bindv6only = 0, it's broken as Linux application. ----------------------------------------------------------- -- Kazuo Oishi -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r5msss71....@molech.giraffy.jp
