Ticket #44 (new defect)
s2s dies when remote host has A and AAAA records.
| Reported by: | smoku | Owned by: | smoku |
|---|---|---|---|
| Priority: | major | Component: | s2s |
| Version: | 2.1 | Keywords: | |
| Cc: | Tracforge_linkmap: | ||
| Blocking: | Blocked By: |
Description
On 2.0s9 and 2.0s10, the s2s component will die if asked to connect to a host that has both A and AAAA addresses. This does not happen if it is asked to connect to a host with only A or only AAAA records.
The host machine is OpenBSD 3.7 with IPv6 in the kernel, but no 'real' IPv6 address (only the fe80:: loopback). The problem has also been seen on FreeBSD 5.4 , also without a 'real' IPv6 connection.
tcpdump shows that no connection (IPv6 or IPv4) is attempted in this situation.
Last log message is line 266 of s2s/out.c, reading:
jabberd/s2s[19057]: [-1] [2001:610:1:80aa:192:87:102:36, port=5269] mio_connect error: No route to host (65) jabberd/router[9114]: [127.0.0.1, port=39526] disconnect jabberd/router[9114]: [s2s] default route offline jabberd/router[9114]: [s2s] offline
No useful messages come from the debug log, the last entry there being:
router.c:290 read action on fd 4
