UPnP does not work on my Linksys wrt54g router
UPnP does not work on my Linksys wrt54g router
I know there has been lots of UPnP fixes recently. It does not affect me too much because I already forward ports to fix this issue. However, UPnP still does not work on the WRT54G linksys router (it is a very popular router). I tested it by clicking on use random ports and then testing the new random port using the service that is provided with deluge. UPnP is enabled on my router and it has recent firmware.
Re: UPnP does not work on my Linksys wrt54g router
Are you using 1.0.5 and could you possibly build deluge with TORRENT_UPNP_LOGGING to get some upnp logs?DUser wrote:I know there has been lots of UPnP fixes recently. It does not affect me too much because I already forward ports to fix this issue. However, UPnP still does not work on the WRT54G linksys router (it is a very popular router). I tested it by clicking on use random ports and then testing the new random port using the service that is provided with deluge. UPnP is enabled on my router and it has recent firmware.
Re: UPnP does not work on my Linksys wrt54g router
In Deluge 1.0.5, UPnP works fine on my Linksys WRT54G2 router (which is the same as the WRT54G v5 upwards).
Re: UPnP does not work on my Linksys wrt54g router
It may help to pinpoint problems too if you said what firmware is in the router, there is also a lot of 3rd party firmwares for wrt54g's. Is it possible that a certain firmware version/type could cause such a problem?
Re: UPnP does not work on my Linksys wrt54g router
It is the standard linksys firmware. I think I got it compiled with the flag. Where is the log file located at? I am running ubuntu
Re: UPnP does not work on my Linksys wrt54g router
It the current working directly where you launch deluged.DUser wrote:It is the standard linksys firmware. I think I got it compiled with the flag. Where is the log file located at? I am running ubuntu
Re: UPnP does not work on my Linksys wrt54g router
Okay, here is my UPnP log. Btw, UPnP has been verified to work in uTorrent.
Code: Select all
Nov 14 03:16:16 ==> Broadcasting search for rootdevice
Nov 14 03:16:16 *** add mapping [ proto: tcp ext_port: 65138 local_port :65138 ]
Nov 14 03:16:16 *** add mapping [ proto: udp ext_port: 65138 local_port :65138 ]
Nov 14 03:16:17 <== (192.168.1.101:59831) Device with HTTP method: m-search. Ignoring device
Nov 14 03:16:18 ==> Broadcasting search for rootdevice
Nov 14 03:16:18 <== (192.168.1.101:59831) Device with HTTP method: m-search. Ignoring device
Nov 14 03:16:18 <== (192.168.1.1:1900) Found rootdevice: http://192.168.1.1:2869/IGatewayDeviceDescDoc total: 0
Nov 14 03:16:22 ==> Broadcasting search for rootdevice
Nov 14 03:16:22 <== (192.168.1.101:59831) Device with HTTP method: m-search. Ignoring device
Nov 14 03:16:28 ==> Broadcasting search for rootdevice
Nov 14 03:16:28 <== (192.168.1.101:59831) Device with HTTP method: m-search. Ignoring device
Nov 14 03:16:30 ==> connecting to http://192.168.1.1:2869/IGatewayDeviceDescDoc
Nov 14 03:16:31 <== (http://192.168.1.1:2869/IGatewayDeviceDescDoc) Rootdevice response, found control URL: http://192.168.1.1:2869/WANIPConnCtrlUrl urlbase: namespace: urn:schemas-upnp-org:service:WANIPConnection:1
Nov 14 03:16:31 ==> connecting to 192.168.1.1
Nov 14 03:16:31 ==> sending: POST /WANIPConnCtrlUrl HTTP/1.0
Host: 192.168.1.1:2869
Content-Type: text/xml; charset="utf-8"
Content-Length: 597
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"
<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:AddPortMapping xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>65138</NewExternalPort><NewProtocol>TCP</NewProtocol><NewInternalPort>65138</NewInternalPort><NewInternalClient>192.168.1.101</NewInternalClient><NewEnabled>1</NewEnabled><NewPortMappingDescription>Deluge 1.0.5</NewPortMappingDescription><NewLeaseDuration>3600</NewLeaseDuration></u:AddPortMapping></s:Body></s:Envelope>
Nov 14 03:16:31 <== got error message: 718
Nov 14 03:16:31 ==> connecting to 192.168.1.1
Nov 14 03:16:31 ==> sending: POST /WANIPConnCtrlUrl HTTP/1.0
Host: 192.168.1.1:2869
Content-Type: text/xml; charset="utf-8"
Content-Length: 593
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"
<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:AddPortMapping xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>0</NewExternalPort><NewProtocol>TCP</NewProtocol><NewInternalPort>65138</NewInternalPort><NewInternalClient>192.168.1.101</NewInternalClient><NewEnabled>1</NewEnabled><NewPortMappingDescription>Deluge 1.0.5</NewPortMappingDescription><NewLeaseDuration>3600</NewLeaseDuration></u:AddPortMapping></s:Body></s:Envelope>
Nov 14 03:16:31 <== got error message: 718
Nov 14 03:16:31 <== map response: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>718</errorCode><errorDescription>
ConflictInMappingEntry</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>
Nov 14 03:16:31 ==> connecting to 192.168.1.1
Nov 14 03:16:31 ==> sending: POST /WANIPConnCtrlUrl HTTP/1.0
Host: 192.168.1.1:2869
Content-Type: text/xml; charset="utf-8"
Content-Length: 597
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"
<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:AddPortMapping xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>65138</NewExternalPort><NewProtocol>UDP</NewProtocol><NewInternalPort>65138</NewInternalPort><NewInternalClient>192.168.1.101</NewInternalClient><NewEnabled>1</NewEnabled><NewPortMappingDescription>Deluge 1.0.5</NewPortMappingDescription><NewLeaseDuration>3600</NewLeaseDuration></u:AddPortMapping></s:Body></s:Envelope>
Nov 14 03:16:31 <== got error message: 718
Nov 14 03:16:31 ==> connecting to 192.168.1.1
Nov 14 03:16:31 ==> sending: POST /WANIPConnCtrlUrl HTTP/1.0
Host: 192.168.1.1:2869
Content-Type: text/xml; charset="utf-8"
Content-Length: 593
Soapaction: "urn:schemas-upnp-org:service:WANIPConnection:1#AddPortMapping"
<?xml version="1.0"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:AddPortMapping xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"><NewRemoteHost></NewRemoteHost><NewExternalPort>0</NewExternalPort><NewProtocol>UDP</NewProtocol><NewInternalPort>65138</NewInternalPort><NewInternalClient>192.168.1.101</NewInternalClient><NewEnabled>1</NewEnabled><NewPortMappingDescription>Deluge 1.0.5</NewPortMappingDescription><NewLeaseDuration>3600</NewLeaseDuration></u:AddPortMapping></s:Body></s:Envelope>
Nov 14 03:16:31 <== got error message: 718
Nov 14 03:16:31 <== map response: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>718</errorCode><errorDescription>
ConflictInMappingEntry</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>
Re: UPnP does not work on my Linksys wrt54g router
If you need anything else, let me know
Re: UPnP does not work on my Linksys wrt54g router
It works! 
WRT54GL, Ubuntu 8.10 32bit, Deluge 1.05
Read this:
http://forums.linksys.com/linksys/board ... d.id=71179
Hint: Factory defaults after firmware upgrade

WRT54GL, Ubuntu 8.10 32bit, Deluge 1.05
Read this:
http://forums.linksys.com/linksys/board ... d.id=71179
Hint: Factory defaults after firmware upgrade