Package: tinc Version: 1.0.8-1 Severity: wishlist 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
lsof shows that tinc is using an IPv6 socket to make IPv4 connections instead (IP's censored by me) tincd 4052 root 5u IPv6 11926 TCP *:tinc (LISTEN) tincd 4052 root 7u IPv6 35204 TCP 192.168.xxx.xxx:tinc->xxx.xxx.xxx.xxx:42613 (ESTABLISHED) 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. I reported the same issue against openssh-server in Bug#439661. Thanks for your work, Jö. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tinc depends on: ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii liblzo2-2 2.02-3 data compression library ii libssl0.9.8 0.9.8e-6 SSL shared libraries ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime tinc recommends no packages. -- debconf information: * tinc/restart_on_upgrade: true -- "Ich habe eine Maschine erfunden, die den Kommerz aus Weihnachten entfernt." -- "Lass uns ganz viele davon bauen und für viel Geld verkaufen." -- http://www.nichtlustig.de/toondb/021220.html
signature.asc
Description: Digital signature
