Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#383 closed Enhancement (wontfix)

Don't enable UPnp/Nat-PMP when port has been manually opened

Reported by: tiennou Owned by: tiennou
Priority: Normal Milestone: None Set
Component: libtransmission Version: 0.82+
Severity: Normal Keywords:


I'm registering this more to tackle the fact that there are numerous "My port is green, but there was an error mapping port. What does this mean ?". I guess this could be handled in the preferences window, or better into libT port-forwarding stuff.

Change History (6)

comment:1 Changed 14 years ago by charles

the upnp / nat-pmp code's author hasn't been around in a couple of months. If this is something requiring change sin libtransmission's upnp / nat-pmp code, would you like to take a shot at it?

comment:2 Changed 14 years ago by tiennou

  • Component changed from Transmission to libtransmission
  • Milestone changed from None Set to 0.91
  • Owner changed from somebody to tiennou

No problem, I'll take a look a it then...

comment:3 Changed 14 years ago by charles

  • Milestone changed from 0.91 to 0.9x

comment:4 Changed 14 years ago by charles

tiennou: ping

comment:5 Changed 14 years ago by tiennou

  • Resolution set to wontfix
  • Status changed from new to closed

After (re-)taking a look at this and taking a quick dive into the UPnP specification (*shrug*), there is no specific return code when tryin to auto-map a port already manually opened, so I guess this takes this down. (quick look at NAT-PMP spec) NAT-PMP doesn't allow this neither. And IIRC livings tackled the issue by removing the Port-mapping led altogether.

comment:6 Changed 14 years ago by charles

  • Milestone changed from 0.9x to None Set
Note: See TracTickets for help on using tickets.