[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 267551] New: ktorrent contacts dual stack tracker exclusively
From: Benedikt Gollatz <benedikt () gollatz ! net>
Date: 2011-03-03 13:21:35
Message-ID: bug-267551-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=267551
Summary: ktorrent contacts dual stack tracker exclusively via
IPv6 on dual-stacked machine
Product: ktorrent
Version: unspecified
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: joris.guisson@gmail.com
ReportedBy: benedikt@gollatz.net
Version: unspecified (using KDE 4.5.5)
OS: Linux
When operating a dual-stack IPv6/IPv4 setup and announcing a torrent on a
tracker that is both reachable via IPv6 and IPv4, ktorrent connects to the
tracker only via IPv6, announces only its IPv6 address and only receives IPv6
peers from the tracker, which keeps separate IPv6 and IPv4 client pools. As a
consequence, dual-stack hosts cannot see IPv4-only peers and vice versa.
Reproducible: Always
Steps to Reproduce:
1. Set up working IPv6 and IPv4 on host1.
2. Create torrent, announce on IPv6- and IPv4-enabled tracker like
<http://tracker.ccc.de/announce>.
3. Open torrent on exclusively IPv4-connected host2.
Actual Results:
host1 and host2 get a distinct set of peers (IPv6 pool and IPv4 pool), even
though they are theoretically interconnectible. Due to the current lack of
popularity of IPv6, host1 may not see any peers at all.
Expected Results:
host1 contacts tracker both via IPv4 and IPv6, thus acquiring both IPv6 and
IPv4 peer addresses and announcing both its IPv4 and IPv6 address to the
tracker.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic