Page 1 of 1
Trnamission always claims port is closed despite being open
Posted:
Mon Jan 24, 2022 5:07 amby Cubytus
Hi there,
a recurring issue I had with Transmission installed on fvdwsl-base: it always claims the port is closed, despite me opening it in the router. The router runs OpenWRT, but since the result was the same with Gargoyle (a dd-wrt derivative) on another router, I tend to think the issue is rather with fvdwsl-base or Transmission itself.
Any insight?
Re: Trnamission always claims port is closed despite being o
Posted:
Mon Jan 24, 2022 9:10 amby Jocko
Hi
Transmission opens itself the port if a upnp service is enabled on the router.
So if you created a nat rule for it, you have to remove it and let transmission to do it after enabling upnp on your router
Re: Trnamission always claims port is closed despite being o
Posted:
Mon Jan 24, 2022 2:46 pmby Cubytus
I never enabled UPnP on any of my routers out of security concerns. In fact, both Gargoyle and OpenWRT (and perhaps dd-wrt) turn off UPnP by default, and on OpenWRT, it isn't even installed.
Why can't Transmssion just use the manually opened port?
Re: Trnamission always claims port is closed despite being o
Posted:
Mon Jan 24, 2022 3:49 pmby Jocko
I do not know as we are not the developers...
What I can say it works when I let transmission to forward the port :
- Code: Select all
[2022-01-24 16:41:33.765] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:73)
[2022-01-24 16:41:33.765] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:73)
[2022-01-24 16:41:35.748] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.1.1:60000/7024abc4/upnp/control/WANIPConn1" (upnp.c:200)
[2022-01-24 16:41:35.749] Port Forwarding (UPnP) Local Address is "192.168.1.99" (upnp.c:201)
[2022-01-24 16:41:36.818] Port Forwarding (UPnP) Port forwarding through "http://192.168.1.1:60000/7024abc4/upnp/control/WANIPConn1", service "urn:schemas-upnp-org:service:WANPPPConnection:1". (local address: 192.168.1.99:59135) (upnp.c:276)
[2022-01-24 16:41:36.819] Port Forwarding (UPnP) Port forwarding successful! (upnp.c:280)
[2022-01-24 16:41:36.819] Port Forwarding Forwarded (port-forwarding.c:107)
But anyhow if you set manually the port (TCP and UDP rules), it is also ok according this page
https://transmissionbt.com/help/gtk/1.6x/html/troubleshoot.html
Re: Trnamission always claims port is closed despite being o
Posted:
Tue Jan 25, 2022 3:14 amby Cubytus
Supposed to be OK, but still doesn't work :( I don't have a "double NAT" as described, just a regular cable modem + router. Can't post on their forum either as the register page appears to be cycling through the same fields without acknowledging entries.
On the desktop version of Transmission, I got these parts of the log when switching the port from a forwarded one to a non-forwarded one:
- Code: Select all
2022-01-24 18:18:09 +0000 net.c:462 [Debug] Transmission: Bound socket 11 to port 51415 on 0.0.0.0
2022-01-24 18:18:09 +0000 net.c:462 [Debug] Transmission: Bound socket 12 to port 51415 on ::
2022-01-24 18:18:23 +0000 net.c:462 [Debug] Transmission: Bound socket 11 to port 51414 on 0.0.0.0
2022-01-24 18:18:23 +0000 net.c:462 [Debug] Transmission: Bound socket 12 to port 51414 on ::
Re: Trnamission always claims port is closed despite being o
Posted:
Tue Jan 25, 2022 9:51 amby Jocko
To check on the nas, you can do that
- Code: Select all
netstat -apn|grep transmission
and you should get at least these lines
- Code: Select all
tcp 0 0 0.0.0.0:55185 0.0.0.0:* LISTEN 8826/transmission-d
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 8826/transmission-d
tcp 0 0 :::55185 :::* LISTEN 8826/transmission-d
udp 0 0 0.0.0.0:55185 0.0.0.0:* 8826/transmission-d
55185 is my forwarded port.
And to enable the debug log mode, do if you did not change the location where the downloaded files are stored
- Code: Select all
killall transmission-daemon
transmission-daemon -g /direct-usb/tr-daemon -w /direct-usb/tr-downloads --log-debug --logfile /var/log/transmission.log
(be careful transmission.log will be verbose)
Re: Trnamission always claims port is closed despite being o
Posted:
Tue Jan 25, 2022 11:03 pmby Cubytus
After the first command:
- Code: Select all
# netstat -apn|grep transmission
tcp 0 0 0.0.0.0:9091 0.0.0.0:* LISTEN 4155/transmission-d
tcp 0 0 0.0.0.0:9093 0.0.0.0:* LISTEN 4155/transmission-d
tcp 0 0 0.0.0.0:51413 0.0.0.0:* LISTEN 4171/transmission-d
tcp 0 6771 192.168.1.10:9093 201.160.220.246:14109 ESTABLISHED 4155/transmission-d
tcp 0 1 192.168.1.10:34795 103.244.242.56:30027 SYN_SENT 4155/transmission-d
tcp 0 0 192.168.1.10:49311 86.204.71.225:6881 ESTABLISHED 4155/transmission-d
tcp 32 0 192.168.1.10:46284 172.67.73.71:443 CLOSE_WAIT 4155/transmission-d
tcp 0 243360 192.168.1.10:9093 46.0.56.58:30783 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:33089 200.8.97.124:6881 ESTABLISHED 4155/transmission-d
tcp 0 425 192.168.1.10:56683 196.206.198.118:6881 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 188.251.120.65:55088 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:44120 172.67.73.71:443 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 99.233.198.37:29168 ESTABLISHED 4155/transmission-d
tcp 0 509 192.168.1.10:60683 197.210.64.127:3204 ESTABLISHED 4155/transmission-d
tcp 1 0 192.168.1.10:46324 195.82.146.120:80 CLOSE_WAIT 4155/transmission-d
tcp 0 56937 192.168.1.10:9093 41.103.19.24:11335 ESTABLISHED 4155/transmission-d
tcp 32 0 192.168.1.10:46766 172.67.74.208:443 CLOSE_WAIT 4155/transmission-d
tcp 0 281 192.168.1.10:9093 105.68.155.198:49828 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 37.228.200.125:22852 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 151.246.208.131:58004 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 154.122.56.157:64603 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 157.48.76.118:48155 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 41.82.182.239:62850 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:46171 90.17.249.103:16881 ESTABLISHED 4155/transmission-d
tcp 0 39032 192.168.1.10:9093 187.32.237.15:1796 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 213.47.23.51:55381 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:9093 177.132.53.91:50533 ESTABLISHED 4155/transmission-d
tcp 0 1 192.168.1.10:51351 117.155.170.212:23087 SYN_SENT 4155/transmission-d
tcp 0 1 192.168.1.10:54153 37.172.86.209:35035 SYN_SENT 4155/transmission-d
tcp 0 0 192.168.1.10:9093 51.39.2.16:1225 ESTABLISHED 4155/transmission-d
tcp 0 0 192.168.1.10:36058 172.67.70.124:443 ESTABLISHED 4155/transmission-d
tcp 0 0 :::9093 :::* LISTEN 4155/transmission-d
tcp 0 0 :::51413 :::* LISTEN 4171/transmission-d
udp 0 0 0.0.0.0:60975 0.0.0.0:* 4155/transmission-d
udp 0 0 239.192.152.143:6771 0.0.0.0:* 4155/transmission-d
udp 0 0 192.168.1.10:48259 192.168.1.1:5351 ESTABLISHED 4171/transmission-d
udp 62464 0 0.0.0.0:9093 0.0.0.0:* 4155/transmission-d
udp 0 0 0.0.0.0:43218 0.0.0.0:* 4155/transmission-d
udp 0 0 0.0.0.0:51413 0.0.0.0:* 4171/transmission-d
udp 0 0 192.168.1.10:59402 192.168.1.1:5351 ESTABLISHED 4155/transmission-d
udp 0 0 0.0.0.0:57619 0.0.0.0:* 4155/transmission-d
unix 3 [ ] STREAM CONNECTED 18745154 4171/transmission-d
unix 3 [ ] STREAM CONNECTED 18743761 4155/transmission-d
unix 3 [ ] STREAM CONNECTED 18745155 4171/transmission-d
unix 3 [ ] STREAM CONNECTED 18743758 4155/transmission-d
unix 3 [ ] STREAM CONNECTED 18743760 4155/transmission-d
unix 3 [ ] STREAM CONNECTED 18745152 4171/transmission-d
unix 3 [ ] STREAM CONNECTED 18743757 4155/transmission-d
unix 3 [ ] STREAM CONNECTED 18745151 4171/transmission-d
After killing and restarting in verbose mode:
- Code: Select all
# transmission-daemon --log-debug --logfile /share/1000/tr-downloads/transmission_verbose.log
How do I filter out files?
Re: Trnamission always claims port is closed despite being o
Posted:
Wed Jan 26, 2022 8:26 amby Jocko
You can remove all line containing the string resume.c or torrent.c or announcer.c or tr-dht.c.
According with your netstat -apn command, the port is open on your nas. So with a nat rule on your router there is no issue but check also its firewall settings (some router do not create a firewall rule at the same time you set a nat rule)