Deluge
Cas wrote:It only uses one port at a time but if you restart Deluge and your pc/router is still holding that port connection open it cannot use it until its freed. The libtorrent api does mention this point:Lazybones wrote: More than a single inbound port seems odd for a torrent client, also if I read the libtorrent API correctly it only binds to one inbound port out of the range anyway. I might open it up to two ports to reduce the chance of binding failure.listen-port wrote:If all ports in the specified range fails to be opened for listening, libtorrent will try to use port 0 (which tells the operating system to pick a port that's free).
The listening port should not care what the router is up to unless it is using dynamic port mapping UPNP or NAT transverse... I am using a FIXED port forwarding configuration and have those options unchecked... After a reboot there should be NOTHING on that listening port that Deluge is using, nor should the local machine care about the router status since I have set both manually.