Package: netbase Version: 4.40 Severity: normal
The bindv6only parameter doesn't limit its effect to server sockets. As a side effect, it also disables the possibility of addressing ipv4 only hosts with ipv6 compatibility adresses like ::ffff:192.168.0.1. $ cat /proc/sys/net/ipv6/bindv6only 0 $ telnet ::ffff:192.168.0.1 80 Trying ::ffff:192.168.0.1... Connected to ::ffff:192.168.0.1. Escape character is '^]'. ^] telnet> quit Connection closed. $ echo 1 | su0 tee -a /proc/sys/net/ipv6/bindv6only 1 $ telnet ::ffff:192.168.0.1 80 Trying ::ffff:192.168.0.1... telnet: Unable to connect to remote host: Network is unreachable $ IMHO it doesn't keep things simple and - for the client side part of this issue, it forces applications which migrate from ipv4 to ipv6 to keep legacy code. - for the server part of this issue, it is a good thing to unify TCP part of TCP/IP(V4) and TCP/IP(v6). And it's not a sufficient reason for debian to take the wrong way because "all major OSes" go ahead in the wall. I definitly put a 0 in bindv6only. regards, Guillaume -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
