Rtorrent: Full IPv6 Support

[ghost]

This ticket has been open for 4 years (!) now, with no progress in the main rtorrent branch: http://libtorrent.rakshasa.no/ticket/1111

IPv6 is very real, and very much in production. Comcast, KDDI, Time Warner Cable, Free Telecom, etc... are all deploying IPv6 for their customers starting now: http://www.worldipv6launch.org/

If rtorrent does not support IPv6, there is a good chance that in the near future peers/seeds from major ISP's will be unreachable due to Carrier Grade NAT: http://iepg.org/2012-03-ietf83/IPv6%20Critical%20Mass%20and%20Avoiding%20CGN.pdf

IPv6 support is now an IETF BCP: http://tools.ietf.org/html/rfc6540

All major server providers support IPv6: OVH, LeaseWeb, SoftLayer, FDCServers, NForce, Swiftway, etc...
All other major torrent clients support IPv6: uTorrent, Deluge, QBittorrent, and Transmission.

[ghost]

Eyeball subscriber wise for the ISP's that are enabling IPv6:
Comcast: 18,200,000
AT&T: 16,500,000
Time Warner: 10,000,000
FREE: 5,000,000
XS4ALL: 500,000

Within 44 days, at least 2,500,000 home users across the world will have IPv6 turned on.

Server provider wise:
OVH: 120,000
SoftLayer: 100,000
LeaseWeb: 40,000
FDC Servers: 5,000
And over 275,000 servers are IPv6 enabled. (publicly rent-able, that is.)

[rakshasa]

IPv6 will be done when I get around to it, which might take some time depending on other stuff I'll need to prioritize.

[RCM7]

What about now? :)

[delin]

And…?(

[Issard]

use these 2 patches if you are desperate as i am... (although i've been experiencing memory leaks (11 out of 16GB after running for 2 months with 1400 torrents ~)

https://gist.github.com/yysfire/4538684
https://gist.github.com/yysfire/4538720

patches are for 0.9.2/0.13.2

[inste]

I've found memleak introduced by these patches:
https://github.com/inste/libtorrent/commit/bdf086234cc6ea07364c6ef20e08c5fc504b70db

Have been testing my trunk for two days with about 200 torrents seeding: see no memleaks in pmap and vagrind.

[Xeneox]

Any updates? Is there a chance to have IPv6 support in the next official release?

[rakshasa]

Not likely, I have a todo list of critical issues that needs to be fixed first and need to get back into the habit of working on rtorrent again.

[Wireheadbe]

Thanks for the memleak fix inste! Official IPv6 would be nice I guess.. :+1:

[Issard]

any updates ? its 2014 and official ipv6 support would be nice. all other major torrent clients are already ipv6 compatible :/

[jessetane]

+1 for ipv6!

[hv15]

+1

[salorium]

+1

[delin]

+1

[inste]

There were feature requests for ipv6 for last (almost) ten years firstly on trac, then here. But till today official upstream didn't make a single step, so now we must handle it ourselves

[Tatsh]

You know what would be nice? A fully working and tested (by multiple people including all of you) pull request instead of bugging the author.

[soyuka]

+1 @Tatsh

[webknjaz]

+1 @Tatsh && @inste && @Issard

[soyuka]

https://github.com/inste/libtorrent/commits/master looks good for a PR, I'll try tomorrow (:

[inste]

My interest in rtorrent is (and always was) exclusively consumptional, I have no resources to properly develop and PR to upstream, so these patches were applied and tested only cause of big need in IPv6.
These patches mostly was based on
https://gist.github.com/yysfire/4538684
https://gist.github.com/yysfire/4538720
applied to trunk.
But on the other hand, I can say that they are long-tested (since Oct '13) in 24/7 use with several hundred of torrents in multiple installations (each on CentOS 6 x86_64) and reveal no issues, so I believe these will be a good start for initial PR.

[colinhd8]

+1 @inste

[rakshasa]

Currently being worked on, basing it on the patches however they are not appropriate for inclusion as-is.

[colinhd8]

@rakshasa good news.

[hv15]

@rakshasa awesome!

[rakshasa]

The ipv6 branch on both repositories now seem to work, however there's still a lot of cleanup and refactoring to do before merging.

[salorium]

Good, thank you for work :+1:

[RCM7]

Nice! Thanks for the effort! :+1:

[hv15]

Brilliant! Thank you @rakshasa!

[colinhd8]

Thank you for great work :+1:

[inste]

Good news, @rakshasa :+1:
And BTW plz don't forget about memleak https://github.com/inste/libtorrent/commit/bdf086234cc6ea07364c6ef20e08c5fc504b70db and wrong subnet definitions https://github.com/inste/libtorrent/commit/ca363ee3d1f81f3f1c00bc4c53f52d0b604aceea ;)

[rvalles]

IPv6 with IPv4 NAT in the ISP is very real and crippling.

How's IPv6 support coming along?

[rakshasa]

Merged.

[bernhardschmidt]

@rakshasa Any chance to make a release with this patch soon? Freeze for Debian Stretch is approaching, a release in early December (or earlier) would help to get it in.

[colinhd8]

good news. thanks.:+1:

[chros73]

There are some bugs: https://github.com/rakshasa/libtorrent/issues/114
Please try it out as many as we can, so they can be fixed before a new release.

[telmich]

Hello,

I would love to test/use rtorrent with IPv6, as our networks are IPv6 only now - is there any progress on this?

[rakshasa]

I have various corner cases to deal with before it is done. I hope to have it done over the next couple months.