Opened 6 years ago

#5738 new Bug

HTTP tracker announcements fail if IPv6 global connectivity is not available

Reported by: MoSal Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.84
Severity: Normal Keywords:
Cc:

Description

HTTP trackers' announcements never worked for me. And I found out why.

Conditions: 1] "bind-address-ipv6": "::1" 2] An IPv4 DNS server that returns both IPv4 & IPv6 addresses. 3] No global IPv6 connectivity.

In this case, transmission prefers IPv6 and fail.

Here is some out put after setting TR_CURL_VERBOSE=1

* Hostname was NOT found in DNS cache
*   Trying <IPv4 addr>...
* Hostname was NOT found in DNS cache
* Name '::1' family 2 resolved to '::1' family 10
* bind failed with errno 22: Invalid argument
*   Trying <IPv6 addr>...
* Hostname was found in DNS cache
* Name '::1' family 10 resolved to '::1' family 10
* Local port: 0
* Immediate connect fail for <IPv6 addr>: Network is unreachable
* Closing connection 0

Fails even if the tracker does not resolve to an IPv6 address

* Hostname was NOT found in DNS cache
* Hostname was NOT found in DNS cache
*   Trying <another IPv4 addr>...
* Hostname was found in DNS cache
* Hostname in DNS cache was stale, zapped
* Name '::1' family 2 resolved to '::1' family 10
* bind failed with errno 22: Invalid argument
* Closing connection 4
* Could not resolve host: <hostname>
* Closing connection 5

Announcements work correctly after unsetting bind-address-ipv6

Change History (0)

Note: See TracTickets for help on using tickets.