Am 27.02.2010 17:43, Fabian Knittel schrieb:
> With a few tweaks to /etc/gai.conf I managed to change the order:
>
> $ python -c "import socket; print socket.getaddrinfo(None, 'auth',
> 0, socket.SOCK_STREAM, 0, socket.AI_PASSIVE)"
> [(10, 1, 6, '', ('::', 113, 0, 0)), (2, 1, 6, '', ('0.0.0.0', 113))]
> ^^ ^^^^^^^
> IPv6 IPv4
That's how it is displayed in my case. gai.conf is empty. Right now
i dont see, where this behavior comes from. I hope you understand
that i'm very cautious about patching upstream source as long as we
dont have eliminated all the doughts, where this problem really relies.
> With the tweak in effect, oidentd worked without my patch - using only a
> single IPv6 socket which accepted both IPv4 and IPv6. (This would break
> for /proc/sys/net/ipv6/bindv6only=1.)
I can not confirm this either. I just enabled bindv6only and tried
to connect again to oidentd on ipv4 and ipv6:
Mar 1 09:04:34 black oidentd[18481]: Connection from
cl-849.dus-01.de.sixxs.net (2a01:198:200:350::2):39062
Mar 1 09:04:42 black oidentd[18490]: Connection from
p5B0822FB.dip0.t-ipconnect.de (91.8.34.251):1548
black:/home/sb# lsof -itcp:113
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
oidentd 18443 oident 6u IPv6 48082507 TCP *:auth (LISTEN)
oidentd 18443 oident 7u IPv4 48082508 TCP *:auth (LISTEN)
Now it binds two 2 single sockets but that's really no advantage or
disadvantage at all.
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]
