Pirate Bay v6 breaks stuff?

[Ryan Rawdon]

I also tested out some stuff on TPB last night and had no issues with 
the IPv6-enabled setup (from a machine with v4 and v6 connectivity)

Jeroen Massar wrote:
> Iljitsch van Beijnum wrote:
>   
>> Hi,
>>
>> The Pirate Bay is rolling out IPv6:
>>
>> http://thepiratebay.org/blog/146
>>
>> They now have an IPv6 tracker. I tried this with two clients (purely for
>> research purposes, of course): Azureus 3.0.3.4 and the (original?)
>> BitTorrent 4.1.7 python client. Neither of them could do anything useful
>> when connected to the tracker over IPv6, and neither of them would fall
>> back to IPv4 as far as I can tell.
>>     
>
> The trick is that in the generic tracker protocol (the HTTP based one)
> one don't use the "peers" notation which is IPv4 only (just 32-bits
> repeated).
>
>   
>> Anyone else seeing the same issues?
>>     
>
> Works for me(tm) and apparently a number of clients are able to use it
> IPv6: http://www.sixxs.net/tools/tracker/clients/ for a list.
>
> Note also that http://piratebay.org lists:
> 8<-------------------------------------------------------------------------
> IPv4 23.013.843 peers (10.345.077 seeders + 12.668.766 leechers) in
> 1.593.127 torrents on tracker.
> IPv6 17.142 peers (7.566 seeders + 9.576 leechers) in 15.523 torrents on
> tracker.
> RSS
> ------------------------------------------------------------------------->8
> Thus, yes, there is content out there ;)
>
>   
>> As far as I know, the original BitTorrent specification allows for IPv6
>> but later updates optimized away the possibility of communicating IPv6
>> addresses or host names and only work with IPv4 addresses, but I have no
>> idea about the capabilities of various software.
>>     
>
> They support it, as they don't use the peers notation for IPv6. See above.
>
>   
>> Tip: if you're having this type of trouble on FreeBSD, this will make
>> the client connect to the tracker over IPv6. Creating a Windows version
>> of this command is left as an exercise for the reader.
>>     
>
> Your Prefix Policy should already prefer native IPv6 over native IPv4;
> 6to4 and Teredo is behind native IPv4 though.
>
> Greets,
>  Jeroen
>
>