#3570: UDP tracker announce failures
----------------------------+------------------------
Reporter: maran | Type: bug
Status: new | Priority: major
Milestone: needs verified | Component: libtorrent
Version: 2.1.0 | Keywords:
----------------------------+------------------------
It seems there is something weird going on with UDP announcements on
Deluge 2.X
It seems that it is trying to bind on local IPs.
{{{
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(http://tracker.trackerfix.com:80/announce)[172.17.0.1:61271] v1 skipping
tracker announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://9.rarbg.me:2930/announce)[172.17.0.1:61271] v1 sending announce
(started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(http://tracker.trackerfix.com:80/announce)[127.0.0.1:61271] v1 skipping
tracker announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://9.rarbg.me:2930/announce)[127.0.0.1:61271] v1 sending announce
(started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://9.rarbg.me:2930/announce)[127.0.0.1:61271] v1 skipping tracker
announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://9.rarbg.to:2870/announce)[127.0.0.1:61271] v1 sending announce
(started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://9.rarbg.me:2930/announce)[172.17.0.1:61271] v1 skipping tracker
announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://9.rarbg.to:2870/announce)[172.17.0.1:61271] v1 sending announce
(started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://9.rarbg.to:2870/announce)[172.17.0.1:61271] v1 skipping tracker
announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://tracker.thinelephant.org:12720/announce)[172.17.0.1:61271] v1
sending announce (started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://9.rarbg.to:2870/announce)[127.0.0.1:61271] v1 skipping tracker
announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://tracker.thinelephant.org:12720/announce)[127.0.0.1:61271] v1
sending announce (started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://tracker.thinelephant.org:12720/announce)[127.0.0.1:61271] v1
skipping tracker announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://tracker.slowcheetah.org:14730/announce)[127.0.0.1:61271] v1 sending
announce (started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://tracker.thinelephant.org:12720/announce)[172.17.0.1:61271] v1
skipping tracker announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_announce_alert: test-file.bin
(udp://tracker.slowcheetah.org:14730/announce)[172.17.0.1:61271] v1
sending announce (started)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_announce_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://tracker.slowcheetah.org:14730/announce)[172.17.0.1:61271] v1
skipping tracker announce (unreachable) "" (1)
09:13:22 [DEBUG ][deluge.core.alertmanager :125 ] Handling alert:
tracker_error_alert
09:13:22 [DEBUG ][deluge.core.alertmanager :120 ]
tracker_error_alert: test-file.bin
(udp://tracker.slowcheetah.org:14730/announce)[127.0.0.1:61271] v1
skipping tracker announce (unreachable) "" (1)
}}}
As you can see, it tries to use 127.0.0.1 and 172.17.0.1 which are both in
the private space, making the connections fails.Can we exclude private IPs
from the IP pool Deluge uses?
This was recorded on deluge 2.1.1 and libtorrent 2.0.5-5.
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3570>
Deluge <https://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to deluge-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/deluge-dev/044.ceff32b29ed82a3720bf6503b0971606%40deluge-torrent.org.
