Am 25.02.2010 12:53, Fabian Knittel schrieb: > Stefan Bauer schrieb: >> Follow up - tested on a lenny machine which turns me nuts: >> >> bindv6only=0 >> /etc/default/oidentd is without any -a stanzas >> black:/home/sb# lsof -itcp:113 >> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME >> oidentd 19499 oident 6u IPv6 47082698 TCP *:auth (LISTEN) >> >> >> Even though it shows for unknown reasons only a bind to >> ipv6-addresses, the machine answers correctly ident-requests on ipv4 >> and ipv6 address: >> >> tcp6 0 0 [::]:auth [::]:* >> LISTEN root 47082698 19499/oidentd > > That's really weird... I can properly see both sockets (IPv4 and IPv6) > with lsof and netstat (bindv6only=0). > > But I'm running squeeze and linux kernel image 2.6.32-trunk-amd64, so > maybe there's a display bug on lenny somewhere?
I just came up with that question on irc - here is the answer: <sf> Normalerweise werden die ipv4 adressen in den ipv6 adressraum gemappt. Ein IPv6 Socket bekommt dann beides. Ausser Du schaltest dieses verhalten ab (mit /proc/sys/net/ipv6/bindv6only oder setsockopt, man ipv6). [english translation) Basically ipv4 addresses get mapped into the ipv6-address space. A ipv6-socket includes both then. This behavior can changed either by setting bindv6only in /proc or by setting it directly on the socket. Anyway, i'm still unsure, where the problem relies if there is any at all because -a :: is not a workaround it's more an available option to set. As debian sets nowadays bindv6only by default, it works by default. For the ones, wo need to change that, i will include a note in the default/oidentd file. Stefan -- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ---------- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
