* Sergei Golovan <[email protected]> [2008-10-24 19:45:03 CEST]: > On Fri, Oct 24, 2008 at 9:04 PM, Jonas Smedegaard <[email protected]> wrote: > >>For ejabberd enabling ipv6 implies disabling ipv4. I'm not sure we > >>want to do that now. > > > > I think not: http://www.ejabberd.im/node/1138 > > The only reason why ipv4 connection was possible in this example is an > ipv4 over ipv6 tunnelling enabled. ejabberd itself listens on ipv6 > socket only.
Erm, I like to differ. As long as the IPV6_ONLY flag doesn't get set and it isn't bound to a specific v6 address only the kernel still accepts v4 connection to the port and handles them accordingly. That's the way Debian ships apache2 since ages and I can't remember any complaint about it. I did put the inet6 option into every single listen statement in my jabber instance and have no trouble at all. I would say it is time to just enable it and be done with it. So long, Rhonda -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
