transmission-daemon doesn't open port using UPnP

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
marcelpaulo
Posts: 3
Joined: Sun Oct 24, 2010 6:19 pm

transmission-daemon doesn't open port using UPnP

Post by marcelpaulo »

Even though UPnP is enabled in transmission-daemon as well as the router, transmission-daemon is not opening the port on the router.

I have seen these two topics in this forum, but they don't seem to address the problem I'm facing:

viewtopic.php?f=2&t=15840&hilit=upnp
viewtopic.php?f=2&t=16405&hilit=upnp

Steps to investigate the problem, with screenshots and links to relevant files:

1. Configured my router (D-Link DSL-2730E) for UPnP and no DMZ:
Roteador ADSL - Google Chrome_006.jpg
Roteador ADSL - Google Chrome_006.jpg (12.43 KiB) Viewed 10875 times
Roteador ADSL - Google Chrome_005.jpg
Roteador ADSL - Google Chrome_005.jpg (11.5 KiB) Viewed 10875 times
2. Configured transmission-daemon to forward ports. Here's the relevant entry in my settings.json:

Code: Select all

"port-forwarding-enabled": true, 
3. Start a wireshark capture with filter udp port 1900. Here's the resulting pcap file:
https://docs.google.com/file/d/0B6eQjhX ... p=drivesdk

4. Started transmission-daemon. Here are the entries from /var/log/upstart/transmission-daemon.log related to UPnP:

Code: Select all

[2015-04-15 16:41:26.165 BRT] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
[2015-04-15 16:41:26.165 BRT] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
[2015-04-15 16:41:34.169 BRT] Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:92)
[2015-04-15 16:41:34.169 BRT] Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:92)
5. Tested if the port (51413) was opened, both with transmission-qt and http://www.canyouseeme.org/:
Transmission Preferences_004.jpg
Transmission Preferences_004.jpg (47.7 KiB) Viewed 10875 times
Open Port Check Tool - Google Chrome_003.jpg
Open Port Check Tool - Google Chrome_003.jpg (17.1 KiB) Viewed 10875 times
Analyzing the wireshark pcap file, I could see that:

1. transmission sent the SDDP search broadcasts
2.The router replied 13s later with the required notify's
3. transmission didn't send a request to open the port

I get the impression that transmission didn't wait long enough for the router SDDP replies. Comparing the timestampts from transmission-daemon.log and the pcap file will confirm my hypothesis.

I'm running transmission-daemon 2.84-0ubuntu0.14.10.1 installed from PPA ppa:transmissionbt/ppa, on Xubuntu 14.10.

Please let me know how I can assist debugging this further.

EDIT:Almost forgot to mention, port 51413 is opened on my firewall:

Code: Select all

paulo@monk:~/tmp$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
51413                      ALLOW       Anywhere
5179/tcp                   ALLOW       Anywhere
5183/udp                   ALLOW       Anywhere
22000/tcp                  ALLOW       Anywhere
21026/udp                  ALLOW       Anywhere
21025/udp                  ALLOW       Anywhere
Anywhere                   DENY        192.168.25.1
51413 (v6)                 ALLOW       Anywhere (v6)
5179/tcp (v6)              ALLOW       Anywhere (v6)
5183/udp (v6)              ALLOW       Anywhere (v6)
22000/tcp (v6)             ALLOW       Anywhere (v6)
21026/udp (v6)             ALLOW       Anywhere (v6)
21025/udp (v6)             ALLOW       Anywhere (v6)
Post Reply