tags 440150 + wontfix thanks On Thu, Aug 30, 2007 at 10:02:18AM +0200, Jö Fahlke wrote:
> In my syslog I get the following line from tinc:
> Aug 30 09:27:37 jupiter tinc.planets[4052]: Can't bind to 0.0.0.0 port
> 655/tcp: Address already in use
>
> Apparently, binding a socket to the ipv6 adress :: will also bind it
> to the ipv4 address 0.0.0.0 unless /proc/sys/net/ipv6/bindv6only is
> set to 1. It would be nice if tincd would not explicitly bind to
> 0.0.0.0 or if it would not a pointless warning in this case.
The problem is that tinc cannot see if binding to :: really also makes
it listen on 0.0.0.0 or not. So disabling the warning might hide a
problem for some users. Anyway, it's the kernel's fault, because its
default behaviour is not RFC compliant.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
