rbalik Posted October 17, 2007 Report Posted October 17, 2007 I reported this bug a while ago and it is still not fixed. uTorrent is attempting to forward the port on the wrong device.There are a few UPnP devices on my network and instead of attempting to forward a port on the address of the gateway at 192.168.1.1 uTorrent seems to be trying to forward the port on other devices at 192.168.1.111 and 192.168.1.118 which of course, doesn't work.Is there any way to force it to use the gateway address?Edit: This is with 1.7.5, by the way
Switeck Posted October 17, 2007 Report Posted October 17, 2007 I think there's a couple settings in µTorrent's advanced section that might help.net.outgoing_ipandnet.bind_ip
rbalik Posted October 17, 2007 Author Report Posted October 17, 2007 I get a "UDP port bind() failed" message when I try to set net.bind_ip to 192.168.1.1the outgoing_ip doesn't seem to change anything
DreadWingKnight Posted October 17, 2007 Report Posted October 17, 2007 You can't bind to an IP address that isn't on your system.You have devices advertising gateway capabilities that shouldn't be. Wireshark and check the ssdp/udp packets.
rbalik Posted October 17, 2007 Author Report Posted October 17, 2007 Those IP addresses are actually PCs. I think they're running the Windows Vista media sharing service.\E%ZomlHTTP/1.1 200 OKST:upnp:rootdeviceUSN:uuid:28627880-c17a-4f20-8f26-1b326c2a1a76::upnp:rootdeviceLocation:http://192.168.1.111:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76OPT:"http://schemas.upnp.org/upnp/1/0/"; ns=0101-NLS:f9c17033a413fb28b2c614e1dbf6cb4cCache-Control:max-age=900Server:Microsoft-Windows-NT/5.1 UPnP/1.0 UPnP-Device-Host/1.0Ext:Edit: From UPnP Tester--Description: DeviceType: urn:schemas-upnp-org:device:MediaServer:1FriendlyName: [edited out]Manufacturer: MicrosoftManufacturerUrl: http://www.microsoft.com/ModelName: Windows Media Player SharingModelNumber: 4.0ModelURL: http://www.microsoft.com/PresentationUrl: SerialNumber: [edited out]UDN: [edited out]UPC:Another Edit: UPnP tester can tell the difference between the gateway and these computers. If I set it to only show gateways it shows the single correct thing.
Greg Hazel Posted October 17, 2007 Report Posted October 17, 2007 I reported this bug a while ago and it is still not fixed. uTorrent is attempting to forward the port on the wrong device.There are a few UPnP devices on my network and instead of attempting to forward a port on the address of the gateway at 192.168.1.1 uTorrent seems to be trying to forward the port on other devices at 192.168.1.111 and 192.168.1.118 which of course, doesn't work.Is there any way to force it to use the gateway address?Edit: This is with 1.7.5, by the wayCan you turn on verbose logging, and paste all the upnp related lines here?
rbalik Posted October 18, 2007 Author Report Posted October 18, 2007 Here ya go:[21:14:22] UPnP: Discovered host: http://192.168.1.111:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:14:22] UPnP: Received invalid query from UPnP device[21:14:22] UPnP: Discovered host: http://192.168.1.113:8008/RootDevice.xml[21:14:22] UPnP: Discovered host: http://192.168.1.195:8008/RootDevice.xml[21:14:23] UPnP: Discovered host: http://192.168.1.118:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:14:23] UPnP: Received invalid query from UPnP device[21:14:42] UPnP: Received timeout while communicating with UPnP device[21:14:42] UPnP: Received timeout while communicating with UPnP device[21:14:45] UPnP: Could not map UPnP Port on this pass, retrying.[21:14:47] UPnP: Discovered host: http://192.168.1.113:8008/RootDevice.xml[21:14:48] UPnP: Discovered host: http://192.168.1.111:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:14:48] UPnP: Received invalid query from UPnP device[21:14:49] UPnP: Discovered host: http://192.168.1.118:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:14:49] UPnP: Received invalid query from UPnP device[21:14:49] UPnP: Discovered host: http://192.168.1.195:8008/RootDevice.xml[21:15:07] UPnP: Received timeout while communicating with UPnP device[21:15:09] UPnP: Received timeout while communicating with UPnP device[21:15:12] UPnP: Could not map UPnP Port on this pass, retrying.[21:15:14] UPnP: Discovered host: http://192.168.1.195:8008/RootDevice.xml[21:15:14] UPnP: Discovered host: http://192.168.1.118:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:15:14] UPnP: Discovered host: http://192.168.1.113:8008/RootDevice.xml[21:15:14] UPnP: Received invalid query from UPnP device[21:15:16] UPnP: Discovered host: http://192.168.1.111:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:15:16] UPnP: Received invalid query from UPnP device[21:15:34] UPnP: Received timeout while communicating with UPnP device[21:15:34] UPnP: Received timeout while communicating with UPnP device[21:15:37] UPnP: Could not map UPnP Port on this pass, retrying.[21:15:39] UPnP: Discovered host: http://192.168.1.118:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:15:39] UPnP: Received invalid query from UPnP device[21:15:39] UPnP: Discovered host: http://192.168.1.113:8008/RootDevice.xml[21:15:40] UPnP: Discovered host: http://192.168.1.195:8008/RootDevice.xml[21:15:40] UPnP: Discovered host: http://192.168.1.111:2869/upnphost/udhisapi.dll?content=uuid:28627880-c17a-4f20-8f26-1b326c2a1a76[21:15:40] UPnP: Received invalid query from UPnP device[21:15:59] UPnP: Received timeout while communicating with UPnP device[21:16:00] UPnP: Received timeout while communicating with UPnP device[21:16:03] UPnP: Unable to map port 192.168.1.109:35100 with UPnP.I'm running Smoothwall on the router, by the way. I looked at the UPnP config files on the router and it's set to notify every 240 seconds. Is this too long? Maybe uTorrent just isn't seeing it. Although it really shouldn't be trying to forward a port on a device that isn't a gateway anyways.Edit: I am running Vista, but this problem is also happening with computers on my network running XP.
Greg Hazel Posted October 18, 2007 Report Posted October 18, 2007 I don't see 192.168.1.1 in the list of devices that responded. Also, it doesn't seem to be trying to map those other devices - it just processes all the responses from a search. It would try to map, but I'm not sure they're gateway devices.
rbalik Posted October 18, 2007 Author Report Posted October 18, 2007 Yeah, those aren't gateway devices, they're all PCs.I was under the impression that UPnP programs compiled a list of devices by just waiting for those devices to broadcast themselves at regular intervals. I didn't know that there was a query feature. UPnPtest and Windows both see the Smoothwall so why wouldn't uTorrent?
Greg Hazel Posted October 18, 2007 Report Posted October 18, 2007 uTorrent relies on the query to discovery devices, since many applications listen on port 1900 - including the Windows discovery service. When we bound to port 1900, sometimes queries would fail as well as the regular interval broadcasts going to the other listener.I suppose we could try both simultaniously, and see if that helps. Mind if I send you a build to test that theory?
rbalik Posted October 18, 2007 Author Report Posted October 18, 2007 Sure, you can email to the address in my profile.
Firon Posted October 18, 2007 Report Posted October 18, 2007 If you'd like to talk to him faster, join the IRC channel.
cogboy Posted October 31, 2007 Report Posted October 31, 2007 Any word on whether this fix worked? I'm having a vaguely similar issue where UPnPTester can successfully find the gateway but uTorrent can't. I'm not sure if it's a problem with uTorrent or a problem with the router I'm using.Port binding does work initially, but after 45 minutes or so (of first booting up the router) I get the 'Unable to map port [address of Vista PC with Media Server service] with UPnP' error.It seems that after a certain amount of time uTorrent can't see -- or just isn't using-- the gateway, and is trying to map the port through a Vista machine's UPnP Media Server service.I'm willing to beta test any possible fixes too; feel free to emal me.
Greg Hazel Posted October 31, 2007 Report Posted October 31, 2007 After quite a bit of debugging, we found that the router was never replying to M-SEARCH requests, but only sending NOTIFY packets. What that means is anyone not listening on the 1900 multicast port can not discover the router. Since the OS binds to this port, we would have to use the XP UPnP interface to map a port.We're looking in to using the XP system as a fallback.
rbalik Posted November 1, 2007 Author Report Posted November 1, 2007 I'm still working on getting them to add SSDP search to Smoothwall, which would fix this problem, but there seems to be some reluctance on the part of the developers.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.