Fedora 10's iptables firewall blocks UPnP

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
tolland
Posts: 7
Joined: Mon Jan 12, 2009 12:40 am

Fedora 10's iptables firewall blocks UPnP

Post by tolland »

Hi,

I have uPNP enabled on my router, and its working for other applications such as eMule and games, however transmission is not setting up the port forwarding correctly - the debug log gives;

Mon Jan 12 00:27:49 2009 debug Starting libevent thread
Mon Jan 12 00:27:49 2009 debug setrlimit( RLIMIT_NOFILE, 712 )
Mon Jan 12 00:27:49 2009 debug 200 usable file descriptors
Mon Jan 12 00:27:49 2009 Transmission 1.40 (7096) started

Mon Jan 12 00:27:50 2009 Port Forwarding (NAT-PMP) initnatpmp succeeded (0)
Mon Jan 12 00:27:50 2009 Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2)
Mon Jan 12 00:27:58 2009 debug Port Forwarding (UPnP) upnpDiscover failed (errno 2 - No such file or directory)
Mon Jan 12 00:27:58 2009 debug Port Forwarding (UPnP) UPNP_GetValidIGD failed (errno 0 - Success)
Mon Jan 12 00:27:58 2009 debug Port Forwarding (UPnP) If your router supports UPnP, please make sure UPnP is enabled!
Mon Jan 12 00:27:58 2009 Port Forwarding State changed from "Not forwarded" to "Starting"
Mon Jan 12 00:27:58 2009 debug Bound socket 15 to port 51413
Mon Jan 12 00:27:58 2009 Port Forwarding Opened port 51413 to listen for incoming peer connections
Mon Jan 12 00:27:58 2009 debug Port Forwarding (NAT-PMP) readnatpmpresponseorretry failed. natpmp returned -7 (the gateway does not support nat-pmp); errno is 111 (Connection refused)
Mon Jan 12 00:27:58 2009 Port Forwarding State changed from "Starting" to "???"

The router is a netgear WGT624v3, and there don't seem to be any options other than on/off for uPNP.

I can attach a wireshark dump of the traffic if that would be of any help?

Thanks,

T
tolland
Posts: 7
Joined: Mon Jan 12, 2009 12:40 am

Re: uPNP not working for 1.40 on fedora 10

Post by tolland »

Hi,

In the end it was the default IPTABLES firewall was blocking the uPNP on the router forwarding to the tranmission port. (I thought that uPNP would set the port up regardless of whether it was actually accessible on the client, but alas no)

"service iptables stop" is a workaround, I am having a think on how to have transmission notify iptables of what port it is using

Cheers,

T
Post Reply