Transmission always reports listening port closed?

And I have not any Transmission on the 1st router.
In general I have not the solution for the problem with Transmission running on LEDE routers. I am looking for it as many users do.

EDIT: Sorry for the disappointment, glad that I made you happy for some moments!

If you are certain that you have made the correct forward rule on the first LEDE device, and input rule on the second LEDE device, (from device 2) please provide an output of:

netstat -l -p -t

Show line(s) for the running Transmission client.

I still have the same problem. I do have a forwarding rule on the main router and an input rule on the second. The result of netstat is:

root@Home2:~# netstat -l -p -t
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 Home2.lan:9091 0.0.0.0:* LISTEN 1461/transmission-d
tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 1133/minidlna
tcp 0 0 localhost:netbios-ssn 0.0.0.0:* LISTEN 1253/smbd
tcp 0 0 Home2.lan:netbios-ssn 0.0.0.0:* LISTEN 1253/smbd
tcp 0 0 0.0.0.0:www 0.0.0.0:* LISTEN 1178/uhttpd
tcp 0 0 0.0.0.0:domain 0.0.0.0:* LISTEN 1248/dnsmasq
tcp 0 0 0.0.0.0:49912 0.0.0.0:* LISTEN 1461/transmission-d
tcp 0 0 0.0.0.0:5080 0.0.0.0:* LISTEN 910/dropbear
tcp 0 0 localhost:microsoft-ds 0.0.0.0:* LISTEN 1253/smbd
tcp 0 0 Home2.lan:microsoft-ds 0.0.0.0:* LISTEN 1253/smbd
tcp 0 0 localhost:netbios-ssn :::* LISTEN 1253/smbd
tcp 0 0 fd1c:b88:440::1:netbios-ssn :::* LISTEN 1253/smbd
tcp 0 0 fe80::4a1:51ff:fe8b:32e8:netbios-ssn :::* LISTEN 1253/smbd
tcp 0 0 :::www :::* LISTEN 1178/uhttpd
tcp 0 0 :::domain :::* LISTEN 1248/dnsmasq
tcp 0 0 :::49912 :::* LISTEN 1461/transmission-d
tcp 0 0 :::5080 :::* LISTEN 910/dropbear
tcp 0 0 localhost:microsoft-ds :::* LISTEN 1253/smbd
tcp 0 0 fd1c:b88:440::1:microsoft-ds :::* LISTEN 1253/smbd
tcp 0 0 fe80::4a1:51ff:fe8b:32e8:microsoft-ds :::* LISTEN 1253/smbd

People who have the upload port problem, which daemon have you installed, transmission-daemon-mbedtls or transmission-daemon-openssl?
I cannot answer my own question because now I have reinstalled LEDE for another reason and I don't remember which daemon I installed before.

I'm on transmission-daemon-mbedtls - 2.92+git-4

Before I had transmission-daemon-mbedtls and the upload port was closed, no upload speed appeared at Transmission remote GUI.
Then I tried transmission-daemon-openssl with the same result.
I removed Transmission.

Someone experiencing this issue should consider filing a bug report at: http://bugs.lede-project.org/

It's extremely odd the that the Transmission software doesn't work after opening the firewall input rule.

Here is the bug: https://github.com/openwrt/packages/issues/5459

1 Like

I have this same problem. I am running transmission-daemon-openssl on the router. I have no problems downloading but seeding and connecting to peers seems to struggle compared to my computer.

I tried following this guide but it got me nowhere:

https://forum.openwrt.org/viewtopic.php?id=62462

So from the github bug report, it is just transmission badly reporting the port is closed - underneath ,everything should work.

At the github bug-report link above neheb says that he has solved the Transmission port misfunction for OpenWRT!
https://github.com/openwrt/packages/issues/5459
If someone here can post the exact solution for LEDE following neheb's instructions it would be perfect, I want very much to install again Transmission in my LEDE router!

More discussion and perhaps help here:
https://github.com/transmission/transmission/pull/495

Vasilis, Transmission is fine even now, only the reporting whether the port is open is broken - receiveing and sending files is ok (you still have to open the port in the firewall and then check with some external tool if it is open) so you can install transmission even now.

@felagund I understand, but I thought I should mention the bug-work here, because I have not yet reinstalled Transmission and I don't remember if the Transmission remote GUI reports the upload rate of a torrent file/folder. In any case Transmission reporting the port open or closed is of some importance and it's also the title of this thread.

Sure, and it has some value (for determining if the port is open) and it is certailny confusing as is.

I'm having this problem with the latest OpenWRT. I run transmission-daemon-openssl direct from my router. Here are my port forwarding settings. What am I doing wrong?05%20AM

Edit - I changed from any host in wan to from any host in lan and it still doesn't work.

I also installed the unpnp service but no dice there also.

I noticed that even despite having upnp installed transmission is not passing the correct port forwarding information automatically:

Could using upnp possibly fix this for good?

[2018-08-07 18:34:45.827] Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 0 - No error information) (upnp.c:239)
[2018-08-07 18:34:45.827] Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled! (upnp.c:242)
[2018-08-07 18:34:45.827] Port Forwarding Starting (port-forwarding.c:92)

Upnp is broken by design, it doesn't fix anything.

Hmmm, thanks. I see that nehab fixed this but it is still not working for me. Any guide on this so I can set it up properly?

Are you running 18.06?

This should be an INPUT Traffic Rule, not a Port Forward.