Page 1 of 1

Understanding deluge ports

Posted: Sat Jan 07, 2017 5:04 pm
by archimede
I would like to get a better understanding of deluge use of connection and ports

I configured the deluge server to use a specific network interface (10.33.239.246) and a specific port (56881) for incoming connections. Client requests are served on the default port 58846.
When I launch it, I see deluge listening on the following ports:

Code: Select all

tcp        0      0 10.33.239.246:4433      0.0.0.0:*               LISTEN      6463/python2
tcp        0      0 10.33.239.246:56881     0.0.0.0:*               LISTEN      6463/python2
tcp        0      0 127.0.0.1:58846         0.0.0.0:*               LISTEN      6463/python2
udp        0      0 10.33.239.246:56881     0.0.0.0:*                           6463/python2
udp        0      0 0.0.0.0:52790           0.0.0.0:*                           6463/python2


Out of these, there are two connections I do not understand.

What is port 4433 used for?

The last udp connnection, listening on 0.0.0.0 port 52790, uses a random port every time the program is launched. What is this connection for? Why does it listen on all interfaces?

Thanks

Re: Understanding deluge ports

Posted: Sat Jan 07, 2017 5:41 pm
by Cas
Port 4433 is for ssl torrents, this defaults to off in develop code but was not backported to 1.3 code. Although in libtorrent 1.1 this now defaults to off.

Not sure about the udp connection, it could be DHT, check debug logging. What version of libtorrent are you using?

Re: Understanding deluge ports

Posted: Sun Jan 08, 2017 2:22 am
by archimede
I use the Arch libtorrent-rasterbar package 1:1.0.9-1. I froze it to this version because there were problems upgrading (see ticket below). I am not sure if these have been resolved since.
http://dev.deluge-torrent.org/ticket/2856

Disabling DHT does not make any difference.

Where do I find the debug log? Does in need to be enabled?

Re: Understanding deluge ports

Posted: Sun Jan 08, 2017 12:47 pm
by Cas
With the release of 1.1.1 with backward compatibility fixed it is possible to use it with Deluge 1.3. I still recommend only using 1.0 though :)

The other alternative is that it is uTP, that can only be disabled using the lt config plugin.

See troubleshooting for logging.

Re: Understanding deluge ports

Posted: Sun Jan 15, 2017 8:50 pm
by archimede
In the debug log I cannot find any reference to that other port.

Re: Understanding deluge ports

Posted: Mon Jan 16, 2017 1:18 am
by Cas
Hang on that port is not listed as LISTEN. So in that case it will be your outgoing random port... Did you netstat with -l?

Re: Understanding deluge ports

Posted: Mon Apr 02, 2018 10:58 pm
by Kaliovic
Hello all, I understand that Deluge needs to listen to random (or defined) ports, but I have just realized that Deluge somehow set up permanent port forwarding for ports 4433 and 54441 on my home network router. Is this something I should worry about? I haven't set the port forwarding on the router by myself... Many thanks!

Re: Understanding deluge ports

Posted: Mon Apr 02, 2018 11:22 pm
by Shryp
Kaliovic wrote:Hello all, I understand that Deluge needs to listen to random (or defined) ports, but I have just realized that Deluge somehow set up permanent port forwarding for ports 4433 and 54441 on my home network router. Is this something I should worry about? I haven't set the port forwarding on the router by myself... Many thanks!


You probably have UPnP enabled. It is a bit of a security issue and should be disabled if possible, however it is probably working as expected. There are settings for it in routers and in applications.

Re: Understanding deluge ports

Posted: Wed Nov 18, 2020 10:15 pm
by QWIKAG
Can someone please advise the ports required for Deluge.

Re: Understanding deluge ports

Posted: Wed Nov 18, 2020 11:10 pm
by mhertz
If remember right, then deluged by default listens on port 58846 for client communication(not torrenting), and deluge-web on 8112, but both configurable. Then for torrenting, then outgoing ports by default are random, and incoming a random choosen port by default(on v2) and 6881-6889 I believe for v1.

Normally you only need define a port or port-range for incoming connections, choosen by yourself, and forward in your router and/or firewall - outgoing connections aren't blocked by router and usually of no concern. It's the same as other torrent clients in principle.