> On 2016/05/17 08:27, Brent Cook wrote: > > This patch came by way of the openntpd github. Linux (and possibly others) > > will attempt to bind to 0.0.0.0 when binding to '::' and return an error if > > it can't, unless IPV6_V6ONLY is set. > > Do you see why they're doing this? > > In an OS where IPV6_V6ONLY=0 is the default (i.e. allowing v4 on > v6 sockets), someone binds to :: expecting to pick up all traffic. > > Now another user's process binds to 0.0.0.0.
I am saying such code has no place in base. However regarding these other systems -- Is this problem exclusive to a particular set of programs that open sockets? Or is it a problem for all programs? If it is problem for all programs... Do all of them do it? Why don't all of them do it? How do we get to the point where all programs do the setsockopt? We don't? OK, I get it. Good reason to not bring up an ipv6 connection.
