Opened 10 years ago

Last modified 7 years ago

#884 reopened bug

Deluge (libtorrent) leaves UPnP ports open

Reported by: req1348@… Owned by: andar
Priority: minor Milestone: not applicable
Component: libtorrent Version:
Keywords: upnp Cc: mr.kamu@…

Description

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!

Change History (8)

comment:1 in reply to: ↑ description ; follow-up: Changed 10 years ago by 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!

comment:2 in reply to: ↑ 1 Changed 10 years ago by 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.

comment:3 Changed 10 years ago by andar

  • Status changed from new to pending

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

comment:4 Changed 10 years ago by trac-robot

  • Status changed from pending to closed

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

comment:5 Changed 8 years ago by kamu

  • Cc mr.kamu@… added
  • Keywords upnp added
  • Milestone set to Future
  • Priority changed from critical to minor
  • Status changed from closed to reopened
  • Version changed from 1.1.6 to 1.3.3

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

comment:6 Changed 8 years ago by Cas

  • Component changed from core to libtorrent
  • Milestone Future deleted
  • Version 1.3.3 deleted

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

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

comment:7 Changed 7 years ago by bmnot

  • Summary changed from Deluge leaves UPnP ports open to Deluge (libtorrent) leaves UPnP ports open

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.

comment:8 Changed 7 years ago by Cas

  • Milestone set to not applicable
Note: See TracTickets for help on using tickets.