Opened 16 years ago

Last modified 12 years ago

#884 reopened bug

Deluge (libtorrent) leaves UPnP ports open

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

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)

in reply to:  description ; comment:1 by anonymous, 16 years ago

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!

in reply to:  1 comment:2 by anonymous, 16 years ago

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 by andar, 15 years ago

Status: newpending

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

comment:4 by trac-robot, 15 years ago

Status: pendingclosed

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 by kamu, 13 years ago

Cc: mr.kamu@gmail.com added
Keywords: upnp added
Milestone: Future
Priority: criticalminor
Status: closedreopened
Version: 1.1.61.3.3

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

comment:6 by Calum, 13 years ago

Component: corelibtorrent
Milestone: Future
Version: 1.3.3

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

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

comment:7 by BugMeNot, 13 years ago

Summary: Deluge leaves UPnP ports openDeluge (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 by Calum, 12 years ago

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