Deluge (libtorrent) leaves UPnP ports open

[req1348@…]

Hello,

I'm using Deluge 1.1.6 on Fedora 10 x86_64. I connect through a Linksys WAG54GP2 router with UPnP enabled. Deluge manages to forward ports just fine, problem is that it doesn't close the ports on exit. This, together with the use of random ports, on the long term leads to a lot of ports left open in my router. I'm quite sure this also has security implications.

Other p2p clients like amule or azureus manage to close the ports on exit, so I don't think it's a problem specific to my router. Thank you!

[anonymous]

Replying to req1348@…:

Hello, I'm using Deluge 1.1.6 on Fedora 10 x86_64. I connect through a Linksys WAG54GP2 router with UPnP enabled. Deluge manages to forward ports just fine, problem is that it doesn't close the ports on exit. This, together with the use of random ports, on the long term leads to a lot of ports left open in my router. I'm quite sure this also has security implications. Other p2p clients like amule or azureus manage to close the ports on exit, so I don't think it's a problem specific to my router. Thank you!

[anonymous]

Replying to anonymous:

Replying to req1348@…:

Hello, I'm using Deluge 1.1.6 on Fedora 10 x86_64. I connect through a Linksys WAG54GP2 router with UPnP enabled. Deluge manages to forward ports just fine, problem is that it doesn't close the ports on exit. This, together with the use of random ports, on the long term leads to a lot of ports left open in my router. I'm quite sure this also has security implications. Other p2p clients like amule or azureus manage to close the ports on exit, so I don't think it's a problem specific to my router. Thank you!

Whoops, sorry aboutt he blank comment, the site is bugging and is slow. Anyways, the problem still exists in 1.1.9. Its a pet peeve of mine and I recently came back to Deluge in hopes of this problem being fixed.

[andar]

Is this still a problem with the latest libtorrent (0.14.7)?

[trac-robot]

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

[kamu]

This still remains in 1.3.3. Deluge does not delete the uPnP port forwarding before it closes.

[Cas]

This is not a Deluge bug, please check/report on libtorrent bug tracker.

 http://code.google.com/p/libtorrent/issues/list

[bmnot]

This bug is still in libtorrent, and someone with some clout and an account at Google Code may want to give them a push:

 http://code.google.com/p/libtorrent/issues/detail?id=66

Basically, anything mapped via UPnP will remain mapped until the router is re-started. Not good.