Deluge Forum

This is still a issue for me in Deluge 1.0.4 on Fedora 10.
Would it help if I send you a wireshark packet capture so you can see what's going on? My Router is a Siemens CL-110-I. aMule can set a UPnP Rule successfuly, Deluge not.

Felix

Unfortunately I can confirm this too.
Running Deloge 1.0.4 on intrepid ibex.
My router is a Linksys WAG200G
All other apps can UPNP just fine.

It would help if you could build deluge with TORRENT_UPNP_LOGGING on and send us the upnp.log that is generated.

Huh, I would, except I don't know how to compile turning on that setting you just said.
If you had a binary with the option turned on it'd be ideal. Or point me in the right direction on where I can find out how to properly compile.

priegog wrote:Huh, I would, except I don't know how to compile turning on that setting you just said.
If you had a binary with the option turned on it'd be ideal. Or point me in the right direction on where I can find out how to properly compile.

You basically just need to add "-DTORRENT_UPNP_LOGGING" to the _extra_compile_args list in setup.py and then rebuild. When you start the deluged, it will spit out a upnp.log in your current working directory.

Phew, that took a while (damn old athlon XP processor)
Here it is, then
It says something about not performing the routing because the device i snot on the same network.. which is bollocks, since the router is 192.168.1.1 and my computer is 192.168.1.102...
Hope the log helps.

Dammit, this forum won't let me attach the log under the thousand different extensions I could think of. So I'l just paste it here.

It seems to work now on my machine with the Speedtouch. Thank you, andar and others. I salute you And good luck getting it to work for more routers/machines/etc.

priegog wrote:Phew, that took a while (damn old athlon XP processor)
Here it is, then
It says something about not performing the routing because the device i snot on the same network.. which is bollocks, since the router is 192.168.1.1 and my computer is 192.168.1.102...
Hope the log helps.

Dammit, this forum won't let me attach the log under the thousand different extensions I could think of. So I'l just paste it here.

Code: Select all

Nov 01 19:35:03 ==> Broadcasting search for rootdevice
Nov 01 19:35:03 <== (192.168.1.102:56314) UPnP device ignored because it's not a router on our network (0.0.0.0, 0.0.0.0) (0.0.0.0, 0.0.0.0) (192.168.1.1, 0.0.0.0) 
Nov 01 19:35:03 *** add mapping [ proto: tcp ext_port: 52525 local_port :52525 ]
Nov 01 19:35:03 *** add mapping [ proto: udp ext_port: 52525 local_port :52525 ]
Nov 01 19:35:03 <== (192.168.1.1:2050) Found rootdevice: http://192.168.1.1:49152/gateway.xml total: 0
Nov 01 19:35:05 ==> Broadcasting search for rootdevice
Nov 01 19:35:05 <== (192.168.1.102:56314) UPnP device ignored because it's not a router on our network (0.0.0.0, 0.0.0.0) (0.0.0.0, 0.0.0.0) (192.168.1.1, 0.0.0.0) 
Nov 01 19:35:09 ==> Broadcasting search for rootdevice
Nov 01 19:35:09 <== (192.168.1.102:56314) UPnP device ignored because it's not a router on our network (0.0.0.0, 0.0.0.0) (0.0.0.0, 0.0.0.0) (192.168.1.1, 0.0.0.0) 

Could you paste the contents of: http://192.168.1.1:49152/gateway.xml

Here you go

priegog wrote:Here you go

Code: Select all

−
<root>
−
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.1:49152</URLBase>
−
<device>
−
<deviceType>
urn:schemas-upnp-org:device:InternetGatewayDevice:1
</deviceType>
<friendlyName>LINKSYS WAG200G Gateway</friendlyName>
<manufacturer>LINKSYS</manufacturer>
<manufacturerURL>http://www.linksys.com</manufacturerURL>
<modelDescription>LINKSYS WAG200G Gateway</modelDescription>
<modelName>Wireless-G ADSL Home Gateway</modelName>
<modelNumber>WAG200G</modelNumber>
<modelURL>http://www.linksys.com</modelURL>
<serialNumber>123456789</serialNumber>
<UDN>uuid:8d401597-1dd2-11b2-a7d4-001ee5947cac</UDN>
<UPC>WAG200G</UPC>
−
<serviceList>
−
<service>
<serviceType>urn:schemas-upnp-org:service:Layer3Forwarding:1</serviceType>
<serviceId>urn:upnp-org:serviceId:L3Forwarding1</serviceId>
<controlURL>/upnp/control/L3Forwarding1</controlURL>
<eventSubURL>/upnp/event/L3Forwarding1</eventSubURL>
<SCPDURL>/l3frwd.xml</SCPDURL>
</service>
</serviceList>
−
<deviceList>
−
<device>
<deviceType>urn:schemas-upnp-org:device:WANDevice:1</deviceType>
<friendlyName>WANDevice</friendlyName>
<manufacturer>LINKSYS</manufacturer>
<manufacturerURL>http://www.linksys.com/</manufacturerURL>
<modelDescription>Residential Gateway</modelDescription>
<modelName>Internet Connection Sharing</modelName>
<modelNumber>1</modelNumber>
<modelURL>http://www.linksys.com/</modelURL>
<serialNumber>0000001</serialNumber>
<UDN>uuid:8d401596-1dd2-11b2-a7d4-001ee5947cac</UDN>
<UPC>WAG200G</UPC>
−
<serviceList>
−
<service>
−
<serviceType>
urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
</serviceType>
<serviceId>urn:upnp-org:serviceId:WANCommonIFC1</serviceId>
<controlURL>/upnp/control/WANCommonIFC1</controlURL>
<eventSubURL>/upnp/event/WANCommonIFC1</eventSubURL>
<SCPDURL>/cmnicfg.xml</SCPDURL>
</service>
</serviceList>
−
<deviceList>
−
<device>
<deviceType>urn:schemas-upnp-org:device:WANConnectionDevice:1</deviceType>
<friendlyName>WANConnectionDevice</friendlyName>
<manufacturer>LINKSYS</manufacturer>
<manufacturerURL>http://www.linksys.com/</manufacturerURL>
<modelDescription>Residential Gateway</modelDescription>
<modelName>Internet Connection Sharing</modelName>
<modelNumber>1</modelNumber>
<modelURL>http://www.linksys.com/</modelURL>
<serialNumber>0000001</serialNumber>
<UDN>uuid:8d401597-1dd2-11b2-a7d3-001ee5947cac</UDN>
<UPC>WAG200G</UPC>
−
<serviceList>
−
<service>
−
<serviceType>
urn:schemas-upnp-org:service:WANEthernetLinkConfig:1
</serviceType>
<serviceId>urn:upnp-org:serviceId:WANEthLinkC1</serviceId>
<controlURL>/upnp/control/WANEthLinkC1</controlURL>
<eventSubURL>/upnp/event/WANEthLinkC1</eventSubURL>
<SCPDURL>/wanelcfg.xml</SCPDURL>
</service>
−
<service>
<serviceType>urn:schemas-upnp-org:service:WANPPPConnection:1</serviceType>
<serviceId>urn:upnp-org:serviceId:WANPPPConn1</serviceId>
<controlURL>/upnp/control/WANPPPConn1</controlURL>
<eventSubURL>/upnp/event/WANPPPConn1</eventSubURL>
<SCPDURL>/pppcfg.xml</SCPDURL>
</service>
</serviceList>
</device>
</deviceList>
</device>
−
<device>
<deviceType>urn:schemas-upnp-org:device:LANDevice:1</deviceType>
<friendlyName>LANDevice</friendlyName>
<manufacturer>LINKSYS</manufacturer>
<manufacturerURL>http://www.linksys.com/</manufacturerURL>
<modelDescription>Residential Gateway</modelDescription>
<modelName>Residential Gateway</modelName>
<modelNumber>1</modelNumber>
<modelURL>http://www.linksys.com/</modelURL>
<serialNumber>0000001</serialNumber>
<UDN>uuid:8d401596-1dd2-11b2-a7d3-001ee5947cac</UDN>
<UPC>WAG200G</UPC>
−
<serviceList>
−
<service>
−
<serviceType>
urn:schemas-upnp-org:service:LANHostConfigManagement:1
</serviceType>
<serviceId>urn:upnp-org:serviceId:LANHostCfg1</serviceId>
<controlURL>/upnp/control/LANHostCfg1</controlURL>
<eventSubURL>/upnp/event/LANHostCfg1</eventSubURL>
<SCPDURL>/lanhostc.xml</SCPDURL>
</service>
</serviceList>
</device>
</deviceList>
<presentationURL>http://192.168.1.1/index.htm</presentationURL>
</device>
</root>

This should be fixed in the 1.0.0_RC branch if you feel like testing it out.. it would be appreciated.