Transmission

I can't get an open port even when I try to manually do it. I used the troubleshooting steps and here is my debug log:


2012-04-10 22:09:06 +0000 port-forwarding.c:181 [Info] Port Forwarding: Stopped
2012-04-10 22:09:07 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2012-04-10 22:09:07 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2012-04-10 22:09:07 +0000 upnp.c:104 [Debug] Port Forwarding (UPnP): upnpDiscover failed (errno 0 - Undefined error: 0)
2012-04-10 22:09:07 +0000 upnp.c:214 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Undefined error: 0)
2012-04-10 22:09:07 +0000 upnp.c:217 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2012-04-10 22:09:07 +0000 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2012-04-10 22:09:15 +0000 natpmp.c:77 [Debug] Port Forwarding (NAT-PMP): readnatpmpresponseorretry failed. Natpmp returned -7 (the gateway does not support nat-pmp); errno is 61 (Connection refused)
2012-04-10 22:09:15 +0000 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Starting" to "???"
2012-04-10 22:09:16 +0000 announcer.c:1255 [Info] Major League Baseball 2K12: Scrape error: Could not connect to tracker
2012-04-10 22:09:16 +0000 announcer.c:1264 [Info] Major League Baseball 2K12: Retrying scrape in 7241 seconds.
2012-04-10 22:09:41 +0000 announcer.c:1255 [Info] Major League Baseball 2K12: Scrape error: Could not connect to tracker
2012-04-10 22:09:41 +0000 announcer.c:1264 [Info] Major League Baseball 2K12: Retrying scrape in 7232 seconds.
2012-04-10 22:10:16 +0000 tr-dht.c:542 [Info] Major League Baseball 2K12: IPv4 DHT announce done

Greetings; very 1st post!

Are you talking about the built-in port test visible thru Transmission-gui? Are you using GNOME or Win? I'm starting to wonder if that ever worked, however I believe it does once it's a dedicated (modem > Transmission) connection. Even after I configured it with all my port forwarding scripts on all serially-connected nodes: nope.

And after I done this I noticed a significant 'drop' in speeds! Hm..
I believe Transmission's mission ultimately is to become "config-free" whereas NO port forwarding is necessary; just connect.

I personally run mines under lock and key; not even exposing random ports, thus allowing anyone to 'find' everyone and connect to all (that PGL don't block) successfully.
Gateway modem w/Firewall
Hardware Firewall Appliance
DMZ - Router - (Linux)>Transmission w/active blocklists and scripts.
It's better this way (trust me : P)


I've been around since Napster & WinMX

I had the same problem for a while. What I did was, I just assigned a static ip when port forwarding and it fixed the problem....make sure it's close to your router's ip. So if your router is 192.168.1.1.....assign something like: 192.168.1.50 then port forward to that address.

or try using "UPnP" if your on a home connection (make sure you turn off all port forwards when using UPnP or it won't work).

I tried alot of different technical stuff to fix mine.....but when it came down to it, it was simply "assigning a static address" that fixed the problem. Figure you can try this before getting too tech.