tantra Posted June 26, 2013 Report Share Posted June 26, 2013 HelloI have some trouble with upnp.On my gateway work miniupnpd. When uTorrent send SSDP discovery request miniupnp respond to it with follow (i see this throw wareshark):HTTP/1.1 200 OKCACHE-CONTROL: max-age=120ST: upnp:rootdeviceUSN: uuid:75802409-bccb-40e7-8e6c-60a44c67052b::upnp:rootdeviceEXT:SERVER: RT-N56U/3.0.3.5 UPnP/1.1 MiniUPnPd/1.8LOCATION: http://192.168.1.1:8268/rootDesc.xmlOPT: "http://schemas.upnp.org/upnp/1/0/"; ns=0101-NLS: 1BOOTID.UPNP.ORG: 1CONFIGID.UPNP.ORG: 1337but after that uTorrent can't discover host with folow messages on uTorrent upnp log:27.06.2013 3:00:28: DEBUG: UPnP: Got a reply/notify event27.06.2013 3:00:28: UPnP: Found location from upnp notify: http://192.168.1.1:8268/rootDesc.xml27.06.2013 3:00:28: UPnP: Discovered host: http://192.168.1.1:8268/rootDesc.xml27.06.2013 3:00:28: recvfrom ERROR: 1003527.06.2013 3:00:31: UPnP: Unable to map port 192.168.1.118:42553 with UPnP.27.06.2013 3:00:46: recvfrom ERROR: 1003527.06.2013 3:00:46: recvfrom ERROR: 1003527.06.2013 3:00:49: recvfrom ERROR: 1003527.06.2013 3:00:49: recvfrom ERROR: 1003527.06.2013 3:00:49: recvfrom ERROR: 1003527.06.2013 3:00:49: recvfrom ERROR: 1003527.06.2013 3:00:54: recvfrom ERROR: 1003527.06.2013 3:00:54: recvfrom ERROR: 10035If i go to http://192.168.1.1:8268/rootDesc.xml from browser (Firefox in my case) i see normal xml :<?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:1</deviceType><friendlyName>ASUS RT-N56U Wireless Router</friendlyName><manufacturer>ASUSTek Computer Inc.</manufacturer><manufacturerURL>http://www.asus.com/</manufacturerURL><modelDescription>RT-N56U Router</modelDescription><modelName>Wireless Router</modelName><modelNumber>1</modelNumber><modelURL>http://code.google.com/p/rt-n56u/</modelURL><serialNumber>12345678</serialNumber><UDN>uuid:75802409-bccb-40e7-8e6c-60a44c67052b</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></serviceList><deviceList><device><deviceType>urn:schemas-upnp-org:device:WANDevice:1</deviceType><friendlyName>WANDevice</friendlyName><manufacturer>MiniUPnP</manufacturer><manufacturerURL>http://miniupnp.free.fr/</manufacturerURL><modelDescription>WAN Device</modelDescription><modelName>WAN Device</modelName><modelNumber>20130504</modelNumber><modelURL>http://miniupnp.free.fr/</modelURL><serialNumber>12345678</serialNumber><UDN>uuid:75802409-bccb-40e7-8e6c-60a44c67052b</UDN><UPC>000000000000</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:1</deviceType><friendlyName>WANConnectionDevice</friendlyName><manufacturer>MiniUPnP</manufacturer><manufacturerURL>http://miniupnp.free.fr/</manufacturerURL><modelDescription>MiniUPnP daemon</modelDescription><modelName>MiniUPnPd</modelName><modelNumber>20130504</modelNumber><modelURL>http://miniupnp.free.fr/</modelURL><serialNumber>12345678</serialNumber><UDN>uuid:75802409-bccb-40e7-8e6c-60a44c67052b</UDN><UPC>000000000000</UPC><serviceList><service><serviceType>urn:schemas-upnp-org:service:WANIPConnection:1</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>Also very strange than in wareshark i doesn't see any traffic flow for tcp peer 192.168.1.1:8268 that must be generated by uTorrent. I saw it only when make request by myself throw browserPS: My network topology looks like this:uTorrent ------- router ----- (gateway with nat)uTorrent, router exist in subnet 192.168.1.64/26router and gateway with nat exists in other subnet: 192.168.1.0/26router exist in both subnets, and also on router run igmpproxy to properly route multicastcast traffic (SSDP requests) Link to comment Share on other sites More sharing options...
ciaobaby Posted June 27, 2013 Report Share Posted June 27, 2013 Set the port manually and turn UPnP off then. Link to comment Share on other sites More sharing options...
tantra Posted June 27, 2013 Author Report Share Posted June 27, 2013 it seems i found reason. minuupnpd append additional info in SSDP requestOPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01which other upnp server doesn't do. So a patch miniupnpd (remove code that produce that aditional output) and uTorrent can setup port forwarding begin work Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.