Deluge Announces Wrong Port to Tracker After Port is Changed

[Dagothur]

Hi,

Deluge 2.1.1
libtorrent 2.0.10.0

I believe Deluge is passing stale IP:Port info to libtorrent and/or the trackers.

Currently one of the trackers I use is reporting that it has the wrong port for me despite receiving announces since the port has been changed.

Incoming Port is set to 39619.
The tracker reports an old port of 55526.
Additionally, the "ltConfig" plugin shows that libtorrent has the wrong port (55526).


Restarting deluge, sending an announce and then checking the tracker then shows the correct port. It also then shows correct in ltConfig. So it seems like there is some sort of caching / failure to update.

Any guidance would be appreciated.

[shinger]

Hello Dagothur,

Did you change the port, but did not restart deluged? It is possible that ltconfig (being a plugin) somehow does not maybe have an update cycle or something. So that it only looks for which port is being used and thats it?

You could maybe post this issue directly in the plugin section, so that developer can give more context or maybe is indeed just a bug or something.

[ambipro]

Hi,

Deluge 2.1.1
libtorrent 2.0.10.0

I believe Deluge is passing stale IP:Port info to libtorrent and/or the trackers.

Currently one of the trackers I use is reporting that it has the wrong port for me despite receiving announces since the port has been changed.

Incoming Port is set to 39619.
The tracker reports an old port of 55526.
Additionally, the "ltConfig" plugin shows that libtorrent has the wrong port (55526).

Restarting deluge, sending an announce and then checking the tracker then shows the correct port. It also then shows correct in ltConfig. So it seems like there is some sort of caching / failure to update.

Any guidance would be appreciated.

Hello Dagothur,

Did you change the port, but did not restart deluged? It is possible that ltconfig (being a plugin) somehow does not maybe have an update cycle or something. So that it only looks for which port is being used and thats it?

You could maybe post this issue directly in the plugin section, so that developer can give more context or maybe is indeed just a bug or something.

Changes made to ltConfig do not necessarily need restart. I think that in this case, the interface change may require it, though. Changing the "Network" section will reinitalize the same as when it does with the Port and you Test Active Port, rather than changing it in ltConfig.

I believe the issue is simply the tracker, it takes time for peer list to update and reflect that. If the tracker also tests the port and IP it's reporting then you also may have to wait for that...without knowing the tracker's specific setup you won't know for sure, and the only way you will find out "for sure" is to use http (no s) for the tracker and sniff that, or use a proxy that you can watch the traffic on in Deluge.

You're also "hiding" the Actual Value in ltConfig with your window size, make it wider and you'll see the "Actual Value" - which unless it is checked won't necessarily be the same as "Setting"....