eddie4 Posted August 6, 2013 Report Share Posted August 6, 2013 Hi all,Aim an Bittorrent Tracker operator and am a bit confused by the way utorrent is currently handling trackers that both support IPv4 and IPv6.The current setup is as fallowingTracker:IPv4_IP 37.251.*.*IPv6_IP 2001:*:1f15:105a:4000::102Now because one tracker can't use both ipv4&6 there are 2 instances running. Lets say v4 has 100 peers and v6 has 20.So time for DNS recordsv4.domain.org (HAS ipv4)v5.domain.org (HAS ipv4 & ipv6)v6.domain.org (HAS ipv6)So far as i can tel with my tests is that utorrent will connect as fallowing:v4.domain.org (Connected to ipv4)v5.domain.org (Connected to ipv6)v6.domain.org (Connected to ipv6)The problem is with the way it connects to v5. Lets say an computer has both ipv4&6 connection it will now connect only to the IPv6 tracker and not to the IPv4 tracker. This is an issue because currently the ipv6 swarm will be pretty much empty. As ipv6 processes it will be the other way around and people with ipv4 won't be able to connect to people with ipv4&6. Why doesn't utorrent connect to both ip4&6 Ip's if both dns records are available? Or did I mess up somewhere else and it does? Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 6, 2013 Report Share Posted August 6, 2013 uTorrent follows the operating system preference order, which you happen to have set to ipv6 preference.It's not supposed to connect to both types at once. Link to comment Share on other sites More sharing options...
eddie4 Posted August 6, 2013 Author Report Share Posted August 6, 2013 It's not supposed to connect to both types at once.Why not??As I layout in the start topic that brings up many problems. If i were to change production to add IPv6 support. I would split the swarm in 2, which would be BAD. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 6, 2013 Report Share Posted August 6, 2013 Did you check to see if the tracker was receiving the ipv4 and/or ipv6 address in the tracker request query string?How are these three trackers separated? Link to comment Share on other sites More sharing options...
eddie4 Posted August 6, 2013 Author Report Share Posted August 6, 2013 Did you check to see if the tracker was receiving the ipv4 and/or ipv6 address in the tracker request query string?How are these three trackers separated?Well they are 3 different DNS records for 2 trackers IPv4 and ipv6.Ill have to check the request string Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 6, 2013 Report Share Posted August 6, 2013 And are they all one tracker package on one instance of the tracker software? Link to comment Share on other sites More sharing options...
eddie4 Posted August 6, 2013 Author Report Share Posted August 6, 2013 And are they all one tracker package on one instance of the tracker software?No they are two tracker instances as opentracker will not and cannot run IPv4 and IPv6 at the same time. This is per design and as all bigger none-private trackers run it something we will need to workaroundAm close to getting the peerid's just need to get them out of wireshark Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 6, 2013 Report Share Posted August 6, 2013 the peer IDs aren't relevant here. The rest of the query string is. Link to comment Share on other sites More sharing options...
eddie4 Posted August 6, 2013 Author Report Share Posted August 6, 2013 As expected:ipv4 = ipv4ipv5 = ipv6 (Has both dns records for ipv4 and ipv6)ipv6 = ipv6This fallows the rule that IPv6 has priority when available. To keep ipv6 implementation backwards compatible we need ipv6 connections to connect to both ipv4 and ipv6 when ipv4 is available. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 6, 2013 Report Share Posted August 6, 2013 To keep ipv6 implementation backwards compatible we need ipv6 connections to connect to both ipv4 and ipv6 when ipv4 is available.Incorrect. We need trackers to respect that dual-stack clients will send the other IP address (the one they didn't connect from) in the query string. Link to comment Share on other sites More sharing options...
eddie4 Posted August 6, 2013 Author Report Share Posted August 6, 2013 To keep ipv6 implementation backwards compatible we need ipv6 connections to connect to both ipv4 and ipv6 when ipv4 is available.Incorrect. We need trackers to respect that dual-stack clients will send the other IP address (the one they didn't connect from) in the query string.This is the problem with opensource protocols because UDP ipv6 also isn't working because of problems between implementations. Well i guess the utorrent dev's need to talk to Opentracker devs because this needs to get fixed before IPv6 becoms widely implementenopentrackers view on UDPv6 and Trackerv6http://opentracker.blog.h3q.com/2007/12/28/the-ipv6-situation/Utorrent and opentracker need to talk this over because you are the 2 big players. and can't live without each other.EditFunny thing is Vuze works perfectly with UDPv6 and IPv5 connects to ipv4. Problem is that it does not connect to IPv6 at all. Seems Vuze prioritizes IPv4 over ipv6. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.