Incoming ports are always out of range

General support for problems installing or using Deluge
Post Reply
ragnartarod
New User
New User
Posts: 1
Joined: Thu Oct 21, 2021 3:20 pm

Incoming ports are always out of range

Post by ragnartarod »

Hi all,
I have deluge 1.3.15 in a Buster Raspbian.

I have used it without problems for some time.

I have put all my wired network behind a Google Wifi point. So my network now is:
Internet - ISP modem - Google Wifi - Headless switch - raspberry with deluge.

I have setup the port forwarding in the isp modem to point to Google Wifi IP and setup the port forwarding in Google wifi to point to raspberry.

Also raspberry has a fixed ip in Google wifi through google wifi dhcp setup.

Problem now when deluge starts the incoming port is always outside the range I setup. First I just have one port setup but searching in google I found out you better setup a range in case the modem is keeping used the port. So I put a range of two hundred ports both in the isp modem and google wifi, but deluge always gets a port outside of that range.

Image
https://imgur.com/a/36USl7c


But the process seems to be reserving the proper ports:

Code: Select all

tcp        0      0 0.0.0.0:8112            0.0.0.0:*               LISTEN      19008/python         off (0.00/0/0)
tcp        0      0 0.0.0.0:62100           0.0.0.0:*               LISTEN      19008/python         off (0.00/0/0)
tcp        0      0 0.0.0.0:58846           0.0.0.0:*               LISTEN      19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:52871     77.211.36.158:16881     ESTABLISHED 19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:60615     37.187.111.119:51413    ESTABLISHED 19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:52901     86.127.245.174:42000    ESTABLISHED 19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:57065     80.174.115.24:51422     ESTABLISHED 19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:34969     81.36.182.58:16004      ESTABLISHED 19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:57597     185.228.155.162:63005   ESTABLISHED 19008/python         off (0.00/0/0)
tcp        0      0 192.168.86.46:48371     37.187.111.119:51413    ESTABLISHED 19008/python         off (0.00/0/0)
tcp6       0      0 :::62100                :::*                    LISTEN      19008/python         off (0.00/0/0)
udp        0      0 127.0.0.1:45664         0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 192.168.86.46:6771      0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 127.0.0.1:6771          0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 0.0.0.0:6771            0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 192.168.86.46:58508     0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 0.0.0.0:62100           0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 192.168.86.46:38660     0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 127.0.0.1:34107         0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 0.0.0.0:53056           0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 192.168.86.46:1900      0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 127.0.0.1:1900          0.0.0.0:*                           19008/python         off (0.00/0/0)
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           19008/python         off (0.00/0/0)
udp6       0      0 fe80::4b50:7108:30:6771 :::*                                19008/python         off (0.00/0/0)
udp6       0      0 ::1:6771                :::*                                19008/python         off (0.00/0/0)
udp6       0      0 :::62100                :::*                                19008/python         off (0.00/0/0)
udp6       0      0 fe80::4b50:7108:3:45781 :::*                                19008/python         off (0.00/0/0)
udp6       0      0 ::1:57049               :::*                                19008/python         off (0.00/0/0)
Check the LISTEN ports: 62100 the first available in the range setup.

How can it be using port 62301 and it doesn't show as listening in netstat??????

Is the udp6 and tcp5 normal? I am not sure it was there before Google wifi being the dhcp server and i am not sure if that may be a problem.

What is blocking 200 ports?

Any clue what's going on?

BTW: I cannot upgrade to deluge 2.0 because my favourite tracker doesn't allow it
shamael
Compulsive Poster
Compulsive Poster
Posts: 667
Joined: Sat Oct 08, 2016 9:28 am

Re: Incoming ports are always out of range

Post by shamael »

Your setup seems fine for me, you can even reduce the ports range. Deluge will always use only one port, the range is useful if any other process is already using it. Then Deluge will simply try the next one.
About the IPv6 yes it's normal, you can get rid of it by disabling the IPv6 on the RPI. If you don't redirect the IPv6 there is no point using it on the RPI.

That said you problem is closer to a bug in the interface. Using the same version of Deluge I often take a 10 port range, may you try just for the sake of test to take for example 52100-52110 to see the behaviour? Pinpoint when the problem appears may help.
ignitionnight
New User
New User
Posts: 1
Joined: Mon Oct 25, 2021 8:04 am

Re: Incoming ports are always out of range

Post by ignitionnight »

I've got this same problem, realized this after I had a bunch of random downloads hit my deluge client (suspect weak webui port and password which I've since remedied) so I went into my settings and realized I was no longer using the port I have forwarded to my machine.

Image

I've tried toggling the random port setting on and off, quitting and restarting the app with the setting on and off. Seems like the app is no longer respecting if the use random port setting is off because the port changes every time I reset the app regardless if the setting is enabled or not.
Post Reply