Understanding deluge ports

General support for problems installing or using Deluge
archimede
New User
New User
Posts: 6
Joined: Thu Jun 02, 2016 3:38 pm
OS or Distro: Arch Linux

Understanding deluge ports

Postby archimede » Sat Jan 07, 2017 5:04 pm

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

Cas
Top Bloke
Top Bloke
Posts: 3510
Joined: Mon Dec 07, 2009 6:04 am
OS or Distro: Ubuntu 16.04
Location: Scotland

Re: Understanding deluge ports

Postby Cas » Sat Jan 07, 2017 5:41 pm

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?

archimede
New User
New User
Posts: 6
Joined: Thu Jun 02, 2016 3:38 pm
OS or Distro: Arch Linux

Re: Understanding deluge ports

Postby archimede » Sun Jan 08, 2017 2:22 am

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?
Last edited by archimede on Wed Jan 11, 2017 12:09 am, edited 1 time in total.

Cas
Top Bloke
Top Bloke
Posts: 3510
Joined: Mon Dec 07, 2009 6:04 am
OS or Distro: Ubuntu 16.04
Location: Scotland

Re: Understanding deluge ports

Postby Cas » Sun Jan 08, 2017 12:47 pm

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.

archimede
New User
New User
Posts: 6
Joined: Thu Jun 02, 2016 3:38 pm
OS or Distro: Arch Linux

Re: Understanding deluge ports

Postby archimede » Sun Jan 15, 2017 8:50 pm

In the debug log I cannot find any reference to that other port.

Cas
Top Bloke
Top Bloke
Posts: 3510
Joined: Mon Dec 07, 2009 6:04 am
OS or Distro: Ubuntu 16.04
Location: Scotland

Re: Understanding deluge ports

Postby Cas » Mon Jan 16, 2017 1:18 am

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?

Kaliovic
New User
New User
Posts: 1
Joined: Mon Apr 02, 2018 10:51 pm
OS or Distro: Windows 10

Re: Understanding deluge ports

Postby Kaliovic » Mon Apr 02, 2018 10:58 pm

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!

Shryp
Super Seeder
Super Seeder
Posts: 459
Joined: Mon Apr 20, 2015 10:20 pm
OS or Distro: Manjaro Linux

Re: Understanding deluge ports

Postby Shryp » Mon Apr 02, 2018 11:22 pm

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.


Return to “Support”

Who is online

Users browsing this forum: No registered users and 6 guests