Incoming ports are always out of range
Posted: Thu Oct 21, 2021 3:35 pm
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.
https://imgur.com/a/36USl7c
But the process seems to be reserving the proper ports:
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
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.
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)
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