Tor daemon replies to a SOCKS5 connect command with an IPv4 payload when using IPv6 thus making the client trying to receive too much bytes and failing to use IPv6 with a SOCKS5 connection.
I'll be submitting a patch for this soon. Just need to get this bug number and make the changes file.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
This looks right. I've tweaked the whitespace a little and made a "bug10987_024" branch in case we want to backport. I've merged to 0.2.5, and I'm marking this one for possible 0.2.4 backport.
How much does ipv6 work in 0.2.4 otherwise? If there are other fixes in 0.2.5 that will make you want to use that one instead, then no backport. If this really is the only thing standing between you and happy ipv6 usage, I could maybe be talked into it? That said, 0.2.5 will be out real soon, and sooner if we don't muck with 0.2.4.
I think that IPv6 sorta works in 0.2.4, and this fixes the case where you want to specify an IPv6 address via SOCKS. OTOH, the best reason to do that is AutomapHostsOnResolve, and see also legacy/trac#10468 (moved).