libtorrent sends port=0 via IPv6 announce instead of the correct port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libtorrent-rasterbar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This bug has also been reported to debian [1].
1) lsb_release -rd
Description: Ubuntu 18.10
Release: 18.10
2) dpkg -l | grep libtorrent
ii libtorrent-
ii python-libtorrent 1.1.9-1 amd64 Python bindings for libtorrent-
* What led up to the situation?
My system has both IPv4 and IPv6 connections and I used deluged with libtorrent to get the debian-
* What exactly did you do (or not do) that was effective (or ineffective)?
When I did an update tracker, I saw that 2 announce messages are sent.
One to the tracker's IPv4 address and one to the tracker's IPv6 address, but the last one sent port=0 instead of the correct portnumber.
The order might change (first IPv6 and then IPv4).
* What was the outcome of this action?
I did a tcpdump of the connection to the debian tracker and saw the following data:
To 130.239.18.159 on port 6969:
..`.NGD.GET /announce?
Host: bttracker.
User-Agent: Deluge 1.3.15
Accept-Encoding: gzip
Connection: close
and to 2001:6b0:
..5ENGD.GET /announce?
Host: bttracker.
User-Agent: Deluge 1.3.15
Accept-Encoding: gzip
Connection: close
Here you can see the port=0 part of the announce message, which will make the tracker think the client is listening on port 0, but it is not.
* What outcome did you expect instead?
I would expect that both the IPv4 and IPv6 announce messages would send the correct port
* Additional information
This issue has also been reported to upstream as #3306 [2] and has been fixed with PR #3385 [3]. And it will be available in the next 1.1.X release.
I've added the patch that can be applied to fix the issue.
[1] https:/
[2] https:/
[3] https:/
The attachment "fix the port=0 issue" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]