UPNP not working? Other ways to set advertised server address?
Posted: Mon Jun 18, 2018 3:31 am
I have deluge 1.3.15 running on FreeBSD host behind a NAT router I run myself. I have miniupnpd running, and configured to allow my deluge host to request ports in the same range configured in deluge (lets say 45600 - 45700). Assuming I did that right. (in Network preferences, for both Incoming and Outgoing Ports, I have "From: 45600" and "To: 45700", with "Use Random Ports" _not_ checked.). I also have UPnP checked at the bottom, and none of the other "Network Extras."
On at least one tracker I use, if I ask it about my connect ability, it reports that my client is not able to accept incoming connections, and it shows by IP address as my _internal_ IP address behind my NAT/router, and shows a port number _not_ in the range above...
And, if I look at the packet filter rules put in place on my router by miniupnpd, I see no rules for my deluge server.
Am I not telling deluge correctly to use UPnP to find an outside routable address? Or is there some other reason it is advertising it's internal IP address to outside trackers I'm connected to?
Thanks. Ask any questions if I didn't provide enough information, but I'm a little out of ideas.
On at least one tracker I use, if I ask it about my connect ability, it reports that my client is not able to accept incoming connections, and it shows by IP address as my _internal_ IP address behind my NAT/router, and shows a port number _not_ in the range above...
And, if I look at the packet filter rules put in place on my router by miniupnpd, I see no rules for my deluge server.
Am I not telling deluge correctly to use UPnP to find an outside routable address? Or is there some other reason it is advertising it's internal IP address to outside trackers I'm connected to?
Thanks. Ask any questions if I didn't provide enough information, but I'm a little out of ideas.