Connecting fails if AAAA record is present, but no Server listening on IPv6

[anonymous]

When Gajim finds an AAAA-Record, it tries to connect ONLY via IPv6. If the Jabber Server on the Server isn't running on IPv6 (in this case because ejabberd won't run IPv4 and IPv6 on OpenBSD), Gajim just gives up and never tries to connect via v4.

[asterix]

it's not release critical. This kind of behaviour must be rare

[anonymous]

Replying to asterix:

it's not release critical. This kind of behaviour must be rare

unfortunately it isn't, it happens when there is a network error preventing you from reaching the server, like timeout or host unreachable. Since quite a number of jabber servers (amessage, swissjabber) are IPv6 enabled and IPv6 does not always have the same quality as IPv4 yet you can hit it quite easily.

I think this issue is described more detailled in Ticket #1969

[Astro]

In this case a network error can even be a missing AF_INET6 route (i.e. ::/0). Thus I vote for reincreasing the priority of this bug.

[stefan@…]

What is the status of this bug? I also run into it frequently. A fallback to IPv4 if IPv6 is not working should be fine.

[asterix]

do you have an exemple of such a server so I can reproduce before trying to fix it ?

[stefan@…]

totalueberwachung.de has a AAAA record and jabberd2 running on IPv4 only.

[stefan@…]

Were you able to reproduce the bug?

[stefan@…]

Is the server for testing still needed? The admin requested me if he can enable jabberd on IPv4 and IPv6. That would work around the bug but not fixing it though.

[steve-e]

Have you tried svn recently? The patch in #1969 has been applied, but I don't know if this fixes your problem.

[berni@…]

Not completely. I just checked out SVN and ran it

Workstation:

ip -6 route add unreachable <server>

which would basically be the same as "no IPv6" works just fine, failover to IPv4. Could be that this worked before

Same on the router (which then issues a "network unreachable" ICMPv6 message gives

2007-06-19 12:08:49,647 gajim.c.x.transports_nb: ERROR: Connection to 2001:1b10:1000:0:2aa:ff:fe00:202 lost: 101:Network is unreachable [2467067d17ed6bd42c2ee52d3822bec6e77c9fc7]

but _no_ failover to IPv4. No popup though, the status icon just changes back to "disconnected".

Firewalling (dropping packets on the router) has the same effect.

So no, the problem is not fixed yet.

[Bigon]

Ping, what the status of this bug?

[asterix]

(In [88e45f20219fbe1ed85902ceaa66c988aa3e22b6]) try all IPs of a given host in case first one fails. Fixes #2958