View previous topic :: View next topic |
Author |
Message |
a_big_friend
Joined: 22 Jul 2011 Posts: 3
|
Posted: Fri Jul 22, 2011 8:51 am Post subject: Backward compatibility miniupnp with IGD:2 and clients |
|
|
I'm currently testing a version of IGD firmware (wive-ng-rtnl) that is implementing miniupnp 1.5 with IGD type 2 enabled, see below the UPNP schemas that I've captured with wireshark.
To me it looks that there's a poor (or none) compatibility between miniupnp demon with this IGD type 2 mode and most of the current UPNP clients (Including PS3 and XBOX 360).
Can you please confirm any backward compatibility issue of IGD:2 demon with clients that expect to talk with and IGD:1?
<?xml version="1.0" ?>
- <root xmlns="urn:schemas-upnp-org:device-1-0">
- <specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
- <device>
<deviceType>urn:schemas-upnp-org:device:InternetGatewayDevice:2</deviceType>
<friendlyName>Wifi-Router router</friendlyName>
<manufacturer>Wifi-Router</manufacturer>
<manufacturerURL>http://sadnet.ru</manufacturerURL>
<modelDescription>Wifi-Router router</modelDescription>
<modelName>Wifi-Router router</modelName>
<modelNumber>1</modelNumber>
<modelURL>http://sadnet.ru</modelURL>
<serialNumber>0</serialNumber>
<UDN>uuid:55372061-62fb5aa7f-57eb-a09c7d67307c</UDN>
- <serviceList>
- <service>
<serviceType>urn:schemas-upnp-org:service:Layer3Forwarding:1</serviceType>
<serviceId>urn:upnp-org:serviceId:Layer3Forwarding1</serviceId>
<controlURL>/ctl/L3F</controlURL>
<eventSubURL>/evt/L3F</eventSubURL>
<SCPDURL>/L3F.xml</SCPDURL>
</service>
- <service>
<serviceType>urn:schemas-upnp-org:service:DeviceProtection:1</serviceType>
<serviceId>urn:upnp-org:serviceId:DeviceProtection1</serviceId>
<controlURL>/ctl/DP</controlURL>
<eventSubURL>/evt/DP</eventSubURL>
<SCPDURL>/DP.xml</SCPDURL>
</service>
</serviceList>
- <deviceList>
- <device>
<deviceType>urn:schemas-upnp-org:device:WANDevice:2</deviceType>
<friendlyName>WANDevice</friendlyName>
<manufacturer>MiniUPnP</manufacturer>
<manufacturerURL>http://miniupnp.free.fr/</manufacturerURL>
<modelDescription>WAN Device</modelDescription>
<modelName>WAN Device</modelName>
<modelNumber>20100125</modelNumber>
<modelURL>http://miniupnp.free.fr/</modelURL>
<serialNumber>0</serialNumber>
<UDN>uuid:55372061-62fb5aa7f-57eb-a09c7d67307c</UDN>
<UPC>MINIUPNPD</UPC>
- <serviceList>
- <service>
<serviceType>urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1</serviceType>
<serviceId>urn:upnp-org:serviceId:WANCommonIFC1</serviceId>
<controlURL>/ctl/CmnIfCfg</controlURL>
<eventSubURL>/evt/CmnIfCfg</eventSubURL>
<SCPDURL>/WANCfg.xml</SCPDURL>
</service>
</serviceList>
- <deviceList>
- <device>
<deviceType>urn:schemas-upnp-org:device:WANConnectionDevice:2</deviceType>
<friendlyName>WANConnectionDevice</friendlyName>
<manufacturer>MiniUPnP</manufacturer>
<manufacturerURL>http://miniupnp.free.fr/</manufacturerURL>
<modelDescription>MiniUPnP daemon</modelDescription>
<modelName>MiniUPnPd</modelName>
<modelNumber>20100125</modelNumber>
<modelURL>http://miniupnp.free.fr/</modelURL>
<serialNumber>0</serialNumber>
<UDN>uuid:55372061-62fb5aa7f-57eb-a09c7d67307c</UDN>
<UPC>MINIUPNPD</UPC>
- <serviceList>
- <service>
<serviceType>urn:schemas-upnp-org:service:WANIPConnection:2</serviceType>
<serviceId>urn:upnp-org:serviceId:WANIPConn1</serviceId>
<controlURL>/ctl/IPConn</controlURL>
<eventSubURL>/evt/IPConn</eventSubURL>
<SCPDURL>/WANIPCn.xml</SCPDURL>
</service>
</serviceList>
</device>
</deviceList>
</device>
</deviceList>
<presentationURL>http://192.168.1.1/</presentationURL>
</device>
</root> |
|
Back to top |
|
|
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1589
|
Posted: Fri Jul 22, 2011 12:26 pm Post subject: |
|
|
IGDv2 in miniupnpd is in development.
There certainly are compatibility issues between miniupnpd with IGDv2 enabled and current IGDv1 control points (= clients).
Issues can come from bugs in MiniUPnPd but also from the control points which are very unlikely to have been tested against any IGDv2 implementation.
I have neither a PS3 nor a 360... so if someone can test his setup with theses consoles, I'm interested in any bug report.
I see several likely causes of problems :
1- SSDP discovery process :
miniupnpd should answer to M-SEARCH for both
urn:schemas-upnp-org:device:InternetGatewayDevice:2
and
urn:schemas-upnp-org:device:InternetGatewayDevice:1
but I'm not sure if a v1 control point will accept a urn:schemas-upnp-org:device:InternetGatewayDevice:2 response.
2- Description parsing
by parsing the rootdescription, a v1 control point could reject it.
Note : IGDv2 is designed to be compatible with IGDv1 !
I'm interesting in knowing how other IGDv2 implementation achieve compatibilty with IGDv1 control points. _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
|
|