On Fri, Mar 02, 2007 at 03:23:53AM -0800, Steve Langasek wrote: > Ok -- the IPv6 support in jabber *is* a problem; loading ipv6 support in the > kernel is not an adequate workaround, because when IPv6 support is compiled > into jabber, it *only* listens on IPv6: > > $ sudo lsof -p 2918|grep TCP > jabberd 2918 jabber 7u IPv6 7526 TCP *:xmpp-client (LISTEN) > jabberd 2918 jabber 10u IPv6 7531 TCP *:xmpp-server (LISTEN) > > Obviously, it's not reasonable to enable IPv6 support at the *expense of* > IPv4 support.
Uhm, by default on linux if you listen on the IPv6 wildcard address, you'll get IPv4 automagically too. For example my output for ssh is the same: $ lsof -p 16733 | grep -i listen sshd 16733 root 3u IPv6 5141804 TCP *:ssh (LISTEN) And i can assure you, that works with ipv4 too :) > The IPv6 support in jabber seems to need a total rework. In the meantime, > I'll prepare an NMU to revert this change from the -3.1 NMU. I can agree with that, the code isn't really good. But thanks to the fact that linux listens on both IPv4 and IPv6 on an IPv6 socket it doesn't break IPv4 compatibility. I just tested that you can even listening on multiple ipv4 addresses even works fine (Not the IP protocol vs. the address): $ lsof -n -p 9152 | grep -i listen jabberd 9152 jabber 7u IPv6 6744306 TCP 127.0.0.1:xmpp-client (LISTEN) jabberd 9152 jabber 8u IPv6 6744307 TCP 145.120.11.130:xmpp-client (LISTEN) jabberd 9152 jabber 11u IPv6 6744310 TCP *:xmpp-server (LISTEN) So imho the NMU which disables ipv6 should be reverted and probably an modprobe ipv6 added to the init script. Sorry for commenting so late, but hopefully it can still be fixed for etch... Sjoerd -- The best defense against logic is ignorance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
