Opened 13 years ago
Closed 13 years ago
#3259 closed Bug (invalid)
Port closed as of 1.93, Mac OS X
Reported by: | David Munch | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | None Set |
Component: | Transmission | Version: | 1.93 |
Severity: | Normal | Keywords: | port closed mac os x |
Cc: |
Description (last modified by charles)
As of 1.93, the port is closed. Downgrading to 1.92 fixes the problem. Quoting Charles on the forum:
In 1.93 Transmission upgraded the port forwarding libraries it uses for port forwarding (miniupnpc and libnatpmp) ... if your ports started being closed when you upgraded to 1.93, maybe there's a bug in the new version of one of those libraries.
Mac OS X 10.6.3.
Change History (5)
comment:1 Changed 13 years ago by charles
- Description modified (diff)
comment:2 Changed 13 years ago by charles
comment:3 Changed 13 years ago by David Munch
I will try that, and return. :)
comment:4 Changed 13 years ago by David Munch
Seems that 1.92 is changing between open and closed, so I guess it is not something specific on 1.93. You may close this I guess. :)
comment:5 Changed 13 years ago by charles
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Because port forwarding is a very... tempermental feature on some routers, the ideal thing to test before reporting this upstream to the libnatpmp / upnpc authors would be to make certain that this is repeatable and not a fluke. For example, if you take turns running the 1.92 and 1.93 executables a couple of times each, does the port always forward with 1.92, and always not forward with 1.93?