1

Quite new to ubuntu so still learning.

I'm trying to get transmission working but it shows that 51413 is closed. I'm just looking at the settings in Transmission and under Network > Peer listening port it says Port is closed.

Looked into port forwarding from router but the setting doesn't exist. It has IPv6 enabled so apparently no need for port forwarding. So how do I open the port?

I've not got the ufw enabled but I probably should as a security measure. Any help or links to guides would be much appreciated.

Thanks

MontyBlack
  • 11
  • How, exactly, are you determining that port 51413 is closed? Please be detailed: Complete input and output helps much more helpful than summaries. You can edit your question to add as much detail as you need. – user535733 Feb 25 '20 at 21:38
  • Please see https://askubuntu.com/questions/195758/how-do-i-open-port-51413-for-transmission and https://askubuntu.com/questions/460673/firewall-rules-for-transmission – K7AAY Feb 25 '20 at 21:44
  • 1
    This is a known bug in transmission. It may show a properly opened port as closed. – Pilot6 Feb 25 '20 at 21:47
  • Bug reports for port 51413 are listed https://launchpad.net/+search?field.text=port+51413 – K7AAY Feb 26 '20 at 00:08
  • Thanks for the help but nothing has actually worked. I've disabled the firewall to rule that out. Transmission is still not connecting to any peers and the port shows 'closed' in preferences.

    My hunch is that it's something related to the config.json file but I'm not sure what it could be that I need to change.

    Can anyone help me out?

     – MontyBlack Feb 27 '20 at 19:20
  • I fixed it. After I looked at the message log and it told me there was a UDP error and I needed to add a log to /etc/sysctl.conf. Now I've added those lines it's working.

    Testing the port through the Transmission UI still show 'Port closed'. My guess is that because I'm using UPnP it doesn't require port forwarding.

     – MontyBlack Feb 27 '20 at 19:51
  • which lines you added after that it's work – lakshman Feb 28 '20 at 18:43
  • I had to add "net.core.wmem_max=" – MontyBlack Mar 02 '20 at 18:27

0 Answers0