Opened 2 months ago

Last modified 2 months ago

#3570 new bug

UDP tracker announce failures

Reported by: maran Owned by:
Priority: major Milestone: needs verified
Component: libtorrent Version: 2.1.0
Keywords: Cc:

Description

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.

Change History (1)

comment:1 Changed 2 months ago by maran

Sadly having a public IP forced does not seem to solve the problem.

12:07:04 [DEBUG   ][deluge.core.alertmanager      :130 ] tracker_announce_alert: Testfile (udp://tracker.opentrackr.org:1337/announce)[185.162.184.11:62359] sending announce (started)
12:08:04 [DEBUG   ][deluge.core.alertmanager      :130 ] tracker_error_alert: Testfile (udp://tracker.opentrackr.org:1337/announce)[185.162.184.11:62359] timed out "" (1)

Having NC is reporting there is no issue connecting to the tracker.

nc -v -u tracker.opentrackr.org 1337
Connection to tracker.opentrackr.org (93.158.213.92) 1337 port [udp/*] succeeded!

Using Deluge 1.3 and Libtorrent 1.X everything works fine as well.

Note: See TracTickets for help on using tickets.