Hi,

I am using rc1 of ktorrent3.2 (works on beta1 too).

When i try download a torrent from thepiratebay with this set of tracker :
http://tracker.thepiratebay.org/announce
udp://tracker.thepiratebay.org:80/announce

I get as result of announce :
« Réponse du traqueur non valable » in french
Invalid answer from tracker

It seems that on my box with ipv6 enable and working the domain name is resolved like this :
tracker.thepiratebay.org => 2a01:298:3:1::2

And ktorrent seems to not understand the aswer result...

The dns resolution for tracker.thepiratebay.org is this one :
tracker.thepiratebay.org has address 77.247.176.153
tracker.thepiratebay.org has address 77.247.176.132
tracker.thepiratebay.org has address 77.247.176.134
tracker.thepiratebay.org has address 77.247.176.135
tracker.thepiratebay.org has address 77.247.176.136
tracker.thepiratebay.org has address 77.247.176.137
tracker.thepiratebay.org has address 77.247.176.138
tracker.thepiratebay.org has address 77.247.176.139
tracker.thepiratebay.org has address 77.247.176.144
tracker.thepiratebay.org has address 77.247.176.145
tracker.thepiratebay.org has address 77.247.176.151
tracker.thepiratebay.org has IPv6 address 2a01:298:3:1::2

If i add one of the ipv4 ip and use it as a tracker url it works back...

May you fix ktorrent to handle ipv4 urls ?

There is an other bug too in the interface, it's impossible to add an url like this :
http://2a01:298:3:1::2/announce

My test by aliasing in /etc/hosts tracker2.thepiratebay.org to the ipv6 adresse got me the same invalid answer from tracker.

I use mandriva 2009.1 (cooker), ktorrent3.2rc1 (same issue on beta1), ipv4 and ipv6 stack.

The pirate bay is enabling ipv6, here is a discussion :
http://thepiratebay.org/blog/146

Seems azereus (vuze) is fixed to works on it.
Tickets are open for libtorrent :
http://libtorrent.rakshasa.no/ticket/1111
Transmission has implemented it :
« Transmission has implemented IPv6 in version 1.50 beta 2 » in http://thepiratebay.org/blog/146#dt-16621

On irc://irc.efnet.nl/thepiratebay channel i get some info about ipv6, upd and torrent protocol not realy fixed.

Japje- were saying that « udp for ipv6 is still bugged, i dont know the details of it, but brokep or TiAMO might »

berniv6 added some info about udp problem :
- I think the problem is not in the UDP protocol, but in compact peers
- compact v6 peers
- Azureus/Vuze had its share of problems with that as well

The UDP tracker protocol does not work with IPv6, it will work over IPv6, but the IP addresses in the responses are only IPv4 addresses, at this moment, there is no standard way to pass IPv6 addresses with the protocol.

Anyway, the original error message has to do with the HTTP tracker.

Can you make a wireshark trace ? So I can see what the tracker returns.

IPv6 should work, it has been included for some time now, and when I tested it, I had no problems with IPv6 trackers. Obviously this code hasn't seen much widespread usage, so there are probably some bugs in it.

This issue is still present today. It seems that thepiratebay tracker once contacted via IPv6 gives back bogus response:

Code: Select all

0030  00 00 00 00 00 01 00 50 be 23 ad b7 64 17 17 2b   .......P.#..d..+
0040  91 bf 50 18 00 0e 78 63 00 00 48 54 54 50 2f 31   ..P...xc..HTTP/1
0050  2e 30 20 32 30 30 20 4f 4b 0d 0a 43 6f 6e 74 65   .0 200 OK..Conte
0060  6e 74 2d 54 79 70 65 3a 20 74 65 78 74 2f 70 6c   nt-Type: text/pl
0070  61 69 6e 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e   ain..Content-Len
0080  67 74 68 3a 20 31 31 32 0d 0a 0d 0a 64 38 3a 63   gth: 112....d8:c
0090  6f 6d 70 6c 65 74 65 69 30 65 31 30 3a 64 6f 77   ompletei0e10:dow
00a0  6e 6c 6f 61 64 65 64 69 30 65 31 30 3a 69 6e 63   nloadedi0e10:inc
00b0  6f 6d 70 6c 65 74 65 69 31 65 38 3a 69 6e 74 65   ompletei1e8:inte
00c0  72 76 61 6c 69 31 37 32 32 65 31 32 3a 6d 69 6e   rvali1722e12:min
00d0  20 69 6e 74 65 72 76 61 6c 69 38 36 31 65 36 3a    intervali861e6:
00e0  70 65 65 72 73 36 31 38 3a 20 02 54 f0 16 83 00   peers618: .T....
00f0  00 00 00 00 00 00 00 00 01 dd 6c 65               ..........le   


And FYN/ACK follows after that. However, if I send the same request which ktorrent has just sent (via telnet) to the IPv4 address of the piratebay tracker, I get a proper full response.

I don't want to disable IPv6 on my machine. Would it be possible to disable it in ktorrent for tracker queries?

All the tracker stuff is done via KIO, as far as I know there is no way to do this.