Trouble with jabber.org and IPv6

Good evening.

I run my own ejabberd server and I've been having, for some time,
a problem federating with jabber.org.  This same machine also has an
IPv6 connection through Hurricane Electric's tunnelbroker.

After poking around some, it became apparent that my machine could connect
to hermes.jabber.org over IPv4, but not the IPv6 interface of hermes6
(2605:da00:5222:5269::2:1).  I couldn't traceroute there.  I tried using
Hurricane Electric's Looking Glass to see if it was just my tunnel
endpoint, but none of the other sites in North America they listed could
traceroute their way to hermes6.jabber.org either.  I was wondering if
anyone else is able to contact jabber.org through IPv6 for
server-to-server federation and if they might give me a pointer.

I also tried two workarounds.  First, I configured ejabberd to use only
IPv4 for outgoing S2S connections.  When this still didn't solve the
problem, I took a look at the traffic with wireshark and found a
dialback request.  Theorizing that the jabber.org server might be trying
to dial back to mine over its IPv6 address, I tried adding an
_xmpp-server SRV record to point to a hostname with ONLY an A record but
no AAAA record and tried again, but that didn't solve the problem
either.  So, as a second question, is there a way to force IPv4 and only
IPv4 for one specific server?

Thank you very much.
_______________________________________________
This is JUser -- a mailing list for end users
of Jabber/XMPP clients.

To unsubscribe, send email to
[email protected]
or go to the following web
page, scroll all the way down,
and type in your email address:

http://mail.jabber.org/mailman/listinfo/juser
_______________________________________________