This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Problem with UPnP plugin

Page 1 of 2 (18 posts)

1, 2 • Next

Tags: None
(comma "," separated)
rikd
Registered Member
Posts
13
Karma
0

Problem with UPnP plugin

Tue Mar 07, 2006 7:34 pm
Hi,

I've just come across ktorrent and am trying to get it functional before I make the full switch.. Just one problem..

I can't seem to get the UPNP plugin working...

I've enabled it and it then searches for the my router and all I get back is "invalid URL"

Log is:
Code: Select all
Bound to port 6881
Loading plugin logviewerplugin
Loading plugin upnpplugin
Trying to find UPnP devices on the local network
Showing KT
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
Invalid URL
USE THE FORCE KTORRENTVIEW !!!!
IP 0.0.0.0 banned.


only files in the dir are:
    log plugins routers search_engines


Searched the boards - and some mentions of similar problems - but no mention of solutions..

I'm using a DLink DSL-G604T wireless ADSL router if that helps..

Would appreciate any thoughts, or help in getting this working..

TIA,
RikD
stoeptegel
Registered Member
Posts
1075
Karma
0

Tue Mar 07, 2006 10:08 pm
Maybe stupid question, but are you sure UPnP is enabled in your router and that no firewall is obstructing the passthrough?

Speaking for myself: UPnP does work on my zyxel 2602, but sometimes i do get firewalled on some torrents. For this reason and because i know UPnP was dangerous under windows(which may be a very unvalid reason when using linux), i am using NAT instead.

PS.The firmware of my modem is modded by my ISP demon.nl and is unstable, so don't take my information for granted.
rikd
Registered Member
Posts
13
Karma
0

Wed Mar 08, 2006 5:08 pm
UPnP is enabled on the router - Azureus and others have no problem accessing it.

Again - since Azureus has no issues with firewall blocking it, am assumming that ktorrent shouldn't have a problem either.

I dont' want to rely on port forwarding because
a) I upgrade FW reguarly on the box, and having to set it up all the time is a pain.
b) I don't always run torrent clients from the same PC - so each PC needs to be able to punch a hole through to the router if possible.

RikD.
George
Moderator
Posts
5421
Karma
1

Thu Mar 09, 2006 5:23 pm
The problems with this kind of stuff is that I do not have your router. So it is pretty difficult to debug this.

I need to write a small UPnP test tool which produces some usefull debugging output.

Btw, does the routers file contain anything ?
rikd
Registered Member
Posts
13
Karma
0

Thu Mar 09, 2006 6:53 pm
routers file is empty..

let me know what I can do to help out.

- if I get time this weekend, I might download the SVN version and see what I can dig out. Would be nice to have more verbose output on what is going..

RikD.
stoeptegel
Registered Member
Posts
1075
Karma
0

Thu Mar 09, 2006 9:13 pm
Poke me if you happen to need my router file (zyxel prestige 2602R-61)
rudwardt
Registered Member
Posts
1
Karma
0

Mon Mar 13, 2006 1:34 am
I've got the same problem. UPnP does not work. With Azureus it works fine but I want to get rid of that java monster.

My log file:
Code: Select all
Bound to port 6881
Loading /home/rudi/.kde3.5/share/apps/ktorrent/tor0/
Encoding : UTF-8
Multi file torrent
Loading plugin upnpplugin
Trying to find UPnP devices on the local network
Loading plugin searchplugin
Loading plugin infowidgetplugin
Showing KT
Trying to find UPnP devices on the local network
Trying to find UPnP devices on the local network
SynchronousWait
USE THE FORCE KTORRENTVIEW !!!!
IP 0.0.0.0 banned.


My upnp_failure file:
Code: Select all
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
   <specVersion>
      <major>1</major>
      <minor>0</minor>
   </specVersion>
   <URLBase>http://192.168.0.1:5678</URLBase>
   <device>
      <deviceType>urn:schemas-upnp-org:device:InternetGatewayDevice:1</deviceType>
      <presentationURL>http://192.168.0.1:80</presentationURL>
      <friendlyName>D-Link Router</friendlyName>
      <manufacturer>D-Link</manufacturer>
      <manufacturerURL>http://www.dlink.com</manufacturerURL>
      <modelDescription>Internet Access Router</modelDescription>
      <modelName>D-Link Router</modelName>
        <UDN>uuid:upnp-InternetGatewayDevice-1_0-12345678900001</UDN>
        <UPC>123456789001</UPC>
      <serviceList>
         <service>
            <serviceType>urn:schemas-upnp-org:service:Layer3Forwarding:1</serviceType>
            <serviceId>urn:upnp-org:serviceId:L3Forwarding1</serviceId>
            <controlURL>/Layer3Forwarding</controlURL>
            <eventSubURL>/Layer3Forwarding</eventSubURL>
            <SCPDURL>/Layer3Forwarding.xml</SCPDURL>
         </service>
      </serviceList>
      <deviceList>
         <device>
            <deviceType>urn:schemas-upnp-org:device:WANDevice:1</deviceType>
            <friendlyName>WANDevice</friendlyName>
            <manufacturer>D-Link</manufacturer>
            <manufacturerURL>http://www.dlink.com</manufacturerURL>
            <modelDescription>Internet Access Router</modelDescription>
            <modelName>D-Link Router</modelName>
            <modelNumber>1</modelNumber>
            <modelURL>http://support.dlink.com</modelURL>
                <serialNumber>12345678900001</serialNumber>
                <UDN>uuid:upnp-WANDevice-1_0-12345678900001</UDN>
                <UPC>123456789001</UPC>
            <serviceList>
               <service>
                  <serviceType>urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1</serviceType>
                  <serviceId>urn:upnp-org:serviceId:WANCommonInterfaceConfig</serviceId>
                  <controlURL>/WANCommonInterfaceConfig</controlURL>
                  <eventSubURL>/WANCommonInterfaceConfig</eventSubURL>
                  <SCPDURL>/WANCommonInterfaceConfig.xml</SCPDURL>
               </service>
            </serviceList>
            <deviceList>
               <device>
                  <deviceType>urn:schemas-upnp-org:device:WANConnectionDevice:1</deviceType>
                  <friendlyName>WAN Connection Device</friendlyName>
                  <manufacturer>D-Link</manufacturer>
                  <manufacturerURL>http://www.dlink.com</manufacturerURL>
                  <modelDescription>Internet Access Router</modelDescription>
                  <modelName>D-Link Router</modelName>
                  <modelNumber>1</modelNumber>
                  <modelURL>http://support.dlink.com</modelURL>
                        <serialNumber>12345678900001</serialNumber>
                        <UDN>uuid:upnp-WANConnectionDevice-1_0-12345678900001</UDN>
                        <UPC>123456789001</UPC>
                  <serviceList>
                     <service>
                        <serviceType>urn:schemas-upnp-org:service:WANIPConnection:1</serviceType>
                        <serviceId>urn:upnp-org:serviceId:WANIPConnection</serviceId>
                        <controlURL>/WANIPConnection</controlURL>
                        <eventSubURL>/WANIPConnection</eventSubURL>
                        <SCPDURL>/WANIPConnection.xml</SCPDURL>
                     </service>
                  </serviceList>
               </device>
            </deviceList>
         </device>
      </deviceList>
   </device>
</root>


The routers file is empty. Ktorrent is v1.2.
__
Rud
George
Moderator
Posts
5421
Karma
1

Mon Mar 13, 2006 6:41 pm
Something I can debug on, that's a good thing.
George
Moderator
Posts
5421
Karma
1

Mon Mar 13, 2006 7:17 pm
Rudwardt wrote:I've got the same problem. UPnP does not work. With Azureus it works fine but I want to get rid of that java monster.

My log file:
Code: Select all
Bound to port 6881
Loading /home/rudi/.kde3.5/share/apps/ktorrent/tor0/
Encoding : UTF-8
Multi file torrent
Loading plugin upnpplugin
Trying to find UPnP devices on the local network
Loading plugin searchplugin
Loading plugin infowidgetplugin
Showing KT
Trying to find UPnP devices on the local network
Trying to find UPnP devices on the local network
SynchronousWait
USE THE FORCE KTORRENTVIEW !!!!
IP 0.0.0.0 banned.


My upnp_failure file:
....
The routers file is empty. Ktorrent is v1.2.
__
Rud


Well the XML seems to parse fine, can you try it with the latest SVN code ?
That way we can see if this is not a bug which is allready fixed.
rikd
Registered Member
Posts
13
Karma
0

Mon Mar 13, 2006 8:03 pm
ok,

I downloaded latest SVN code, modified UPnPMCastSocket to print a little more info than it currently does..

First the response from my router :
Code: Select all
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
ST:urn:schemas-upnp-org:device:InternetGatewayDevice:1
MAN:"ssdp:discover"
MX:3
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=1800
DATE: Mon, 13 Mar 2006 19:55:10 GMT
EXT:
LOCATION: http://192.168.1.1:52869/gatedesc.xml
SERVER: Linux/2.4.17_mvl21-malta-mips_fp_le, UPnP/1.0, Intel SDK for UPnP devices /1.2
ST: urn:schemas-upnp-org:device:InternetGatewayDevice:1
USN: uuid:75802409-bccb-40e7-8e6c-fa095ecce13e::urn:schemas-upnp-org:device:InternetGatewayDevice:1


And then the code breaks in UPnPMCastSocket::parseResponse() when it checks if the KURL location.isValid()

Code: Select all
Invalid URL in:  http://192.168.1.1:52869/gatedesc.xml at line: LOCATION: http://192.168.1.1:52869/gatedesc.xml


seems like it's got a valid URL to the xml file - next step is check why KURL is reporting it as not valid..

RikD[/code]
rikd
Registered Member
Posts
13
Karma
0

Mon Mar 13, 2006 8:49 pm
Ureka!

Got it to detect my router..

2 problems.
1. I'm running twonkyserver and for some reason that is causing problems despite a valid server. (info attached below)
2. if you look at my previous post. my router would report it's location as
Code: Select all
LOCATION: http://192.168.1.1:52869/gatedesc.xml

But when creating the KURL the space after the first : is left and KURl reports the URL as malformed. removing that space resolves the problem

If I turn off twonkyserver and then run ktorrent with my quick fix at line 131 of upnpmcastsocket.cpp to
Code: Select all
location = line.mid(line.find(':') + 2);
it works perfectly.

A bit rough and ready I know - but just didn't have the time to work out a more elegant solution.

Now to the other problem...
If I'm running twonky, I get many problems - here's the log

Code: Select all
Trying to find UPnP devices on the local network
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://127.0.0.1:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.1.8:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Location : http://192.168.0.20:9000/DeviceDescription.xml
Server : Linux/2.x.x, UPnP/1.0, TwonkyVision UPnP SDK/1.0
Error parsing router description !
Error parsing router description !
Error parsing router description !
Error parsing router description !
Error parsing router description !
Error parsing router description !
Error parsing router description !


Just not sure why it detects the twonky server running so much - I would have expected 3 - but not this...
RikD
George
Moderator
Posts
5421
Karma
1

Tue Mar 14, 2006 5:45 pm
Indeed you are right I forgot to strip the whitespace on the location variable (for some reason I did do the server variable, my brain must have been not functioning 100 %).

Now the twonky thing, lets ignore the many replies and deal with the parsing first, can you get me the XML files from those routers. Just do wget on the location, that gives you the xml description and then post it here.
rikd
Registered Member
Posts
13
Karma
0

Tue Mar 14, 2006 11:26 pm
Twonky isn't a router it's a media server. XML file attached

Code: Select all
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
 <specVersion>
  <major>1</major>
  <minor>0</minor>
 </specVersion>
 <URLBase>http://192.168.1.8:9000/</URLBase>
 <device>
  <dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMS-1.50</dlna:X_DLNADOC>
  <dlna:X_DLNACAP xmlns:dlna="urn:schema-dlna-org:device-1-0">av-upload,image-upload,audio-upload</dlna:X_DLNACAP>
  <deviceType>urn:schemas-upnp-org:device:MediaServer:1</deviceType>
  <UDN>uuid:89665984-7466-0030-1bb1-49ed3885739</UDN>
  <friendlyName>INX-MS1</friendlyName>
  <manufacturer>TwonkyVision GmbH</manufacturer>
  <manufacturerURL>http://www.twonkyvision.de?redsonic.com</manufacturerURL>
  <modelName>TwonkyVision Media Server</modelName>
  <modelNumber>103</modelNumber>
  <modelURL>http://www.twonkyvision.de/UPnP</modelURL>
  <modelDescription>TwonkyVision Media Server</modelDescription>
  <serialNumber></serialNumber>
  <UPC></UPC>
  <presentationURL>configpage/index.htm</presentationURL>
  <serviceList>
   <service>
    <serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType>
    <serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId>
    <SCPDURL>ConnectionManager.xml</SCPDURL>
    <eventSubURL>ConnectionManager/Event</eventSubURL>
    <controlURL>ConnectionManager/Control</controlURL>
   </service>
   <service>
    <serviceType>urn:schemas-upnp-org:service:ContentDirectory:1</serviceType>
    <serviceId>urn:upnp-org:serviceId:ContentDirectory</serviceId>
    <SCPDURL>ContentDirectory.xml</SCPDURL>
    <eventSubURL>ContentDirectory/Event</eventSubURL>
    <controlURL>ContentDirectory/Control</controlURL>
   </service>
  </serviceList>
 </device>
</root>


As mentioned - would expect 3 replies, 1 for each of the interfaces (127.0.0.1, 192.168.0.20 and 192.168.1.8 ).

The XML File from the DLink is
Code: Select all
root>
−
   <specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.1:52869</URLBase>
−
   <device>
−
   <deviceType>
urn:schemas-upnp-org:device:InternetGatewayDevice:1
</deviceType>
<friendlyName>DLINK Internet Gateway Device</friendlyName>
<manufacturer>DLINK</manufacturer>
<manufacturerURL>http://www.dlink.com</manufacturerURL>
<modelName>DLINK IGD</modelName>
<UDN>uuid:75802409-bccb-40e7-8e6c-fa095ecce13e</UDN>
−
   <iconList>
−
   <icon>
<mimetype>image/gif</mimetype>
<width>118</width>
<height>119</height>
<depth>8</depth>
<url>/ligd.gif</url>
</icon>
</iconList>
−
   <serviceList>
−
   <service>
<serviceType>urn:schemas-microsoft-com:service:OSInfo:1</serviceType>
<serviceId>urn:microsoft-com:serviceId:OSInfo1</serviceId>
<controlURL>/upnp/control/OSInfo1</controlURL>
<eventSubURL>/upnp/event/OSInfo1</eventSubURL>
<SCPDURL>/gateinfoSCPD.xml</SCPDURL>
</service>
</serviceList>
−
   <deviceList>
−
   <device>
<deviceType>urn:schemas-upnp-org:device:WANDevice:1</deviceType>
<friendlyName>WANDevice</friendlyName>
<manufacturer>DLINK</manufacturer>
<manufacturerURL>http://www.dlink.com</manufacturerURL>
<modelDescription>WAN Device on DLINK IGD</modelDescription>
<modelName>DLINK IGD</modelName>
<modelNumber>0.92</modelNumber>
<modelURL>http://www.dlink.com</modelURL>
<serialNumber>0.92</serialNumber>
<UDN>uuid:75802409-bccb-40e7-8e6c-fa095ecce13e</UDN>
<UPC>DLINK IGD</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/control/WANCommonIFC1</eventSubURL>
<SCPDURL>/gateicfgSCPD.xml</SCPDURL>
</service>
</serviceList>
−
   <deviceList>
−
   <device>
<deviceType>urn:schemas-upnp-org:device:WANConnectionDevice:1</deviceType>
<friendlyName>WANConnectionDevice</friendlyName>
<manufacturer>DLINK</manufacturer>
<manufacturerURL>http://www.dlink.com</manufacturerURL>
<modelDescription>WanConnectionDevice on DLINK IGD</modelDescription>
<modelName>DLINK IGD</modelName>
<modelNumber>0.92</modelNumber>
<modelURL>http://www.dlink.com</modelURL>
<serialNumber>0.92</serialNumber>
<UDN>uuid:75802409-bccb-40e7-8e6c-fa095ecce13e</UDN>
<UPC>DLINK IGD</UPC>
−
   <serviceList>
−
   <service>
<serviceType>urn:schemas-upnp-org:service:WANIPConnection:1</serviceType>
<serviceId>urn:upnp-org:serviceId:WANIPConn1</serviceId>
<controlURL>/upnp/control/WANIPConn1</controlURL>
<eventSubURL>/upnp/control/WANIPConn1</eventSubURL>
<SCPDURL>/gateconnSCPD.xml</SCPDURL>
</service>
</serviceList>
</device>
</deviceList>
</device>
</deviceList>
<presentationURL>http://192.168.1.1/</presentationURL>
</device>
</root>


Rik.
George
Moderator
Posts
5421
Karma
1

Wed Mar 15, 2006 5:26 pm
The twonky thing is pretty obvious, it's a mediaserver. We only use UPnP to forward ports, I don't think a mediaserver does that.

I'll try out the DLink one. Btw is that the exact output ? That doesn't exactly look like good XML.
rikd
Registered Member
Posts
13
Karma
0

Wed Mar 15, 2006 6:52 pm
no it's not the actual file - was looking at it through firefox. here's the actual file

Code: Select all
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
        <specVersion>
                <major>1</major>
                <minor>0</minor>
        </specVersion>
        <URLBase>http://192.168.1.1:52869</URLBase>
        <device>
                <deviceType>urn:schemas-upnp-org:device:InternetGatewayDevice:1</deviceType>
                <friendlyName>DLINK Internet Gateway Device</friendlyName>
                <manufacturer>DLINK</manufacturer>
                <manufacturerURL>http://www.dlink.com</manufacturerURL>
                <modelName>DLINK IGD</modelName>
                <UDN>uuid:75802409-bccb-40e7-8e6c-fa095ecce13e</UDN>
                <iconList>
                        <icon>
                                <mimetype>image/gif</mimetype>
                                <width>118</width>
                                <height>119</height>
                                <depth>8</depth>
                                <url>/ligd.gif</url>
                        </icon>
                </iconList>
                <serviceList>
                        <service>
                                <serviceType>urn:schemas-microsoft-com:service:OSInfo:1</serviceType>
                                <serviceId>urn:microsoft-com:serviceId:OSInfo1</serviceId>
                                <controlURL>/upnp/control/OSInfo1</controlURL>
                                <eventSubURL>/upnp/event/OSInfo1</eventSubURL>
                                <SCPDURL>/gateinfoSCPD.xml</SCPDURL>
                        </service>
                </serviceList>
                <deviceList>
                        <device>
                                <deviceType>urn:schemas-upnp-org:device:WANDevice:1</deviceType>
                                <friendlyName>WANDevice</friendlyName>
                                <manufacturer>DLINK</manufacturer>
                                <manufacturerURL>http://www.dlink.com</manufacturerURL>
                                <modelDescription>WAN Device on DLINK IGD</modelDescription>
                                <modelName>DLINK IGD</modelName>
                                <modelNumber>0.92</modelNumber>
                                <modelURL>http://www.dlink.com</modelURL>
                                <serialNumber>0.92</serialNumber>
                                <UDN>uuid:75802409-bccb-40e7-8e6c-fa095ecce13e</UDN>
                                <UPC>DLINK IGD</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/control/WANCommonIFC1</eventSubURL>
                                                <SCPDURL>/gateicfgSCPD.xml</SCPDURL>
                                        </service>
                                </serviceList>
                                <deviceList>
                                        <device>
                                                <deviceType>urn:schemas-upnp-org:device:WANConnectionDevice:1</deviceType>
                                                <friendlyName>WANConnectionDevice</friendlyName>
                                                <manufacturer>DLINK</manufacturer>
                                                <manufacturerURL>http://www.dlink.com</manufacturerURL>
                                                <modelDescription>WanConnectionDevice on DLINK IGD</modelDescription>
                                                <modelName>DLINK IGD</modelName>
                                                <modelNumber>0.92</modelNumber>
                                                <modelURL>http://www.dlink.com</modelURL>
                                                <serialNumber>0.92</serialNumber>
                                                <UDN>uuid:75802409-bccb-40e7-8e6c-fa095ecce13e</UDN>
                                                <UPC>DLINK IGD</UPC>
                                                <serviceList>
                                                        <service>
                                                                <serviceType>urn:schemas-upnp-org:service:WANIPConnection:1</serviceType>
                                                                <serviceId>urn:upnp-org:serviceId:WANIPConn1</serviceId>
                                                                <controlURL>/upnp/control/WANIPConn1</controlURL>
                                                                <eventSubURL>/upnp/control/WANIPConn1</eventSubURL>
                                                                <SCPDURL>/gateconnSCPD.xml</SCPDURL>
                                                        </service>
                                                </serviceList>
                                        </device>
                                </deviceList>
                        </device>
                </deviceList>
        <presentationURL>http://192.168.1.1/</presentationURL>
        </device>
</root>


As for twonky - I realise that it;'s a media server and the UPnp supported isn't for AV servers - but the question is why does the plugin attempt to add it to the routers description and is there some means for us to ignore it?

Rik.

Page 1 of 2 (18 posts)

1, 2 • Next

Bookmarks


Who is online

Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]