tags 503313 + upstream thanks [1] talks about that kernel in Squeeze will have IPv6 hardwired, but there I can still observe two difficulties with the current situation: 1) One of comments to [1] mentions that IPv6 still can be disabled in the kernel (using the ipv6.disable=1 kernel command-line option) which is essentially the same as blacklisting module ipv6. 2) Feature request [2] created by upstream as a consequence of this bug report contains a comment from one of ejabberd developers about difficulties which may arise when using STUN in the presence of proposed socket binding fallback mechanics. Essentially this means that the problem of properly supported IPv6 *and* IPv4 is more complex than it appears on the first glance.
So my feeling is that we should leave this situation "as is" for now until upstream comes up with the implementation for EJAB-1010 or some new possibilities to solve this appear. 1. http://blog.fortytwo.ch/archives/71-IPv6-sucks..html 2. https://support.process-one.net/browse/EJAB-1010 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
