uPNP and Port Forwarding

[russiandivxclub]

Hello I have a question. I am using transmission-daemon 2.82 and I am having problem with opening a single port. Let me explain. I am using uTorrent with uPNP and any port I selected I see being activated in router within a second or so. But I don't see it with transmission-daemon. I tried everything. I tried turning uPNP off and on with transmission-remote -M then back -m and tried changing port itself with -p command. Nothing. Port stay closed. Then I decided to turn off port mapping and do manual port forwarding. Right now I have uTorrent with 60190 that's mapped with uPNP and Transmission that have port 60180. And in router I have setup port forwarding to to my internal IP of router 192.168.1.1 (I am using transmission-daemon on DDWRT) and nothing. I even tried to do DMZ both on 192.168.1.1 (my router) or my PC that is on 192.168.1.200 same thing port remain closed when I do test. I am not too sure what is going on. In theory -m command should activate uPNP and as long uPNP enabled in router it should be it. I do know it's activated and works because when I activate uPNP in uTorrent I see right away it showing up in uPNP page on router. Can anyone give me a hint on what else I can try or may be manual settings for DDWRT I am doing all wrong ?

P.S.

If transmission is running on router,does it mean IP of it is routers IP (aka 192.168.1.1) ? Because clearly when let's say I want to forward something from desktop I use desktop IP 192.168.1.200

Thank you guys !

[rb07]

If transmission is running on router

Then you don't need port forwarding (as long as the daemon binds to all interfaces, or at least to the WAN interface).

Port forwarding in Transmission is very strict, the router has to reply with the correct response, otherwise Transmission will not try to open the port. Some routers don't do this, and the reason is their fault, errors in firmware are common, also common is that the error is corrected in new firmware...

I don't know what is the case of DDWRT, which also has many different versions. But you can test it manually using upnpc, which is MiniUPnP's own tool (Transmission uses their library -- and old version, unless its installed system wide), and see if the response from the router to a discovery query is definitive or not. If Transmission is not opening the port, then the response is not definitive... but this was not a waste of time, you can use upnpc to open the port manually, and ask DDWRT to fix their code.

Here's an example with a router that does work:

Code: Select all

$ upnpc -a 192.168.10.5 12345 12345 tcp
upnpc : miniupnpc library test client. (c) 2005-2013 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
 desc: http://192.168.10.1:1780/InternetGatewayDevice.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.10.1:1780/control?WANIPConnection
Local LAN ip address : 192.168.10.5
ExternalIPAddress = <WAN address>
InternalIP:Port = 192.168.10.5:12345
external <WAN address>:12345 TCP is redirected to internal 192.168.10.5:12345 (duration=0)

$ upnpc -d 12345 tcp
upnpc : miniupnpc library test client. (c) 2005-2013 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
 desc: http://192.168.10.1:1780/InternetGatewayDevice.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.10.1:1780/control?WANIPConnection
Local LAN ip address : 192.168.10.5
UPNP_DeletePortMapping() returned : 0