Opened 7 years ago

Last modified 7 years ago

#5588 reopened Bug

udp trackers don't work, transmission just doesn't send request and output "cannot connect to tracker"

Reported by: cyberbat Owned by:
Priority: Normal Milestone: None Set
Component: libtransmission Version: 2.82
Severity: Normal Keywords:
Cc:

Description

I try this file https://trac.transmissionbt.com/attachment/ticket/117/Test-UDP.torrent

I use gentoo linux. If I start tcpdump -i eno1 host tracker.openbittorrent.com (eno1 is my internet interface) And then start Test-UDP torrent in transmission I see nothing in tcpdump output.

For example if I start rtorrent with same torrent file I see (I've masked my IP): 15:15:11.064990 IP (tos 0x0, ttl 64, id 31552, offset 0, flags [DF], proto UDP (17), length 44)

188.255.XX.YY.52701 > 31.172.63.253.80: UDP, length 16

15:15:11.114066 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], proto UDP (17), length 44)

31.172.63.253.80 > 188.255.XX.YY.52701: UDP, length 16

15:15:11.114156 IP (tos 0x0, ttl 64, id 31553, offset 0, flags [DF], proto UDP (17), length 126)

188.255.XX.YY.52701 > 31.172.63.253.80: UDP, length 98

15:15:11.163201 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], proto UDP (17), length 48)

31.172.63.253.80 > 188.255.XX.YY.52701: UDP, length 20

15:15:19.577761 IP (tos 0x0, ttl 64, id 31554, offset 0, flags [DF], proto UDP (17), length 44)

188.255.XX.YY.47233 > 31.172.63.253.80: UDP, length 16

15:15:19.626782 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], proto UDP (17), length 44)

31.172.63.253.80 > 188.255.XX.YY.47233: UDP, length 16

15:15:19.627005 IP (tos 0x0, ttl 64, id 31555, offset 0, flags [DF], proto UDP (17), length 126)

188.255.XX.YY.47233 > 31.172.63.253.80: UDP, length 98

15:15:19.676107 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], proto UDP (17), length 60)

31.172.63.253.80 > 188.255.XX.YY.47233: UDP, length 32

But tracker status is "Asking for more peers..."

I have have tried turn utp off and on. I have tried setting and not the encryption.

Change History (2)

comment:1 Changed 7 years ago by rb07

  • Component changed from Transmission to libtransmission
  • Resolution set to invalid
  • Status changed from new to closed

"Asking for more peers..." is not the same as "transmission says that they are working".

Eventually the asking will either succeed, fail with a connection error, or time out; then an error message appears.

comment:2 Changed 7 years ago by cyberbat

  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Summary changed from udp trackers don't work while transmission says that they are working to udp trackers don't work, transmission just doesn't send request and output "cannot connect to tracker"

After thinking for a while transmission says "cannot connect to tracker". There is nothing usefull in logs (I've cut one private torrentfile):

[22:17:01.455] Transmission 2.82 (14160) started (session.c:738) [22:17:01.455] Cache Maximum cache size set to 4.00 MiB (256 blocks) (cache.c:264) [22:17:01.455] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:828) [22:17:01.455] RPC Server Adding address to whitelist: 192.168.254.* (rpc-server.c:828) [22:17:01.455] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1035) [22:17:01.455] RPC Server Whitelist enabled (rpc-server.c:1039) [22:17:01.455] Bound socket 11 to port 52315 on 0.0.0.0 (net.c:379) [22:17:01.455] Bound socket 12 to port 52315 on :: (net.c:379) [22:17:01.455] Port Forwarding Stopped (port-forwarding.c:183) [22:17:01.455] DHT Initializing DHT (tr-dht.c:277) [22:17:01.455] DHT Reusing old id (tr-dht.c:306) [22:17:01.455] DHT DHT initialized (tr-dht.c:331) [22:17:01.455] LPD Initialising Local Peer Discovery (tr-lpd.c:284) [22:17:01.455] DHT Bootstrapping from 162 IPv4 nodes (tr-dht.c:154) [22:17:01.455] LPD Local Peer Discovery initialised (tr-lpd.c:355) [22:17:01.455] Using settings from "/var/lib/transmission/config" (daemon.c:526) [22:17:01.455] Saved "/var/lib/transmission/config/settings.json" (variant.c:1217) [22:17:01.455] Saved pidfile "/var/run/transmission/transmission.pid" (daemon.c:538) [22:17:01.455] Watching "/var/lib/transmission/watch" for new .torrent files (daemon.c:564) [22:17:01.455] Using inotify to watch directory "/var/lib/transmission/watch" (watch.c:74) [22:17:01.455] Test-UDP Read resume file "/var/lib/transmission/config/resume/Test-UDP.4ece5b02c0e950d0.resume" (resume.c:724) [22:17:01.455] Test-UDP Resume file found 2 files marked for download (resume.c:158) [22:17:01.455] Loaded 2 torrents (session.c:1994) [22:17:01.455] Test-UDP Announcing to tracker (announcer.c:1555) [22:17:01.455] Test-UDP Could not connect to tracker (announcer.c:999) [22:17:01.455] Test-UDP Retrying announce in 20 seconds. (announcer.c:1008) [22:17:21.465] Test-UDP Announcing to tracker (announcer.c:1555) [22:17:21.465] Test-UDP Could not connect to tracker (announcer.c:999) [22:17:21.465] Test-UDP Retrying announce in 324 seconds. (announcer.c:1008)

May be you need by configfile? Or I can recompile transmission with some more output enabled if you tell where I need to patch sources.

Note: See TracTickets for help on using tickets.