Transmission

Brilliant, thanks, I'll give it a go. Had a quick look for the ticket and couldn't find it, but I can certainly see the logic behind only trying to map ports on a connected gateway (I'm thinking networks with multiple possible gateways, etc). You'd think this was a fairly obvious thing to miss on ...

You can also make sure this is the problem by using miniupnp's tool, similar to the one you mentioned (UPnP PortMapper) this one is called upnpc , you can find it in the downloads of miniupnp's page, and if you can open (and close) the port then there is a workaround changing Transmission's code ...

https://forum.transmissionbt.com/viewtopic.php?f=2&t=13405#p60246

Search portforward.com for your router.

Thanks. I know I can manually forward ports; I was just wondering if anyone has any insight into why Transmission specifically seems to have issues with UPnP on this router. That, and this ...

I recently got a new router (Belkin N600 DB), and Transmission doesn't seem to be able to see its UPnP interface to open ports. Here's the relevant section of the log:


2012-05-12 12:55:15 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2012-05-12 12:55:15 +0000 natpmp ...