Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Router ports not removed after QBT upgrade. #5695

Closed
Snake883 opened this issue Sep 2, 2016 · 2 comments
Closed

Router ports not removed after QBT upgrade. #5695

Snake883 opened this issue Sep 2, 2016 · 2 comments

Comments

@Snake883
Copy link

Snake883 commented Sep 2, 2016

Problem:
Old UPnP forwarded ports are not removed from router when QBT is upgraded to a new version.

Situation:
The UPnP port fowarding features creates router ports with a port name that includes the QBT version number.

When QBT is upgraded to a new version, QBT creates new forwarded ports on the router. These new ports contain the new QBT version in the port name.

When the new ports are created with the new QBT version in the port name, QBT doesn't remove the old port numbers with the old QBT version in the port name.

Proposal:
Forwarded ports on the router should be named without the QBT version number. QBT should remove any old ports that are no longer in use.

@Seeker2
Copy link

Seeker2 commented Jul 2, 2017

This is a VERY old bug in libtorrent:
http://code.google.com/p/libtorrent/issues/detail?id=66 reproduced here: xlgjjff/libtorrent#66 libtorrent does not delete UPnP on session deletion
Deluge (libtorrent) leaves UPnP ports open as well: http://dev.deluge-torrent.org/ticket/884

vaguely similar problem... Someone was claiming UPnP doesn't work with UDP:
#6950 UPnP option doesn't open UDP port

other similar issue?:
#6702 UPnP doesn't use configured Optional IP Address

@sledgehammer999
Copy link
Member

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@qbittorrent qbittorrent locked and limited conversation to collaborators Oct 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants