Jump to content

µTorrent UPnP-related issues


Phant0m``

Recommended Posts

Posted

Hi,

I've found several topics relating to µTorrent UPnP-related issues on this board, and some dates way back. And the thing is, it's obvious there's not much interest in investigating into them, and sometimes no participation at all from the µTorrent technical staff.

I really like the µTorrent software, and I know the development is still very, very active, and I can clearly see much participation by the team on the µTorrent forums.

I just want to know, is it a complete waste of my time reporting µTorrent UPnP-related issues? Or is there some interest from the technical and development staff?

One issue I have already reported about, UPnP: Could not map UPnP Port on this pass, retrying.> http://forum.utorrent.com/viewtopic.php?id=63165

And every-time manually de-checking and applying then re-checking 'Enable UPnP port mapping' and applying in Connection, under 'Listening Port', she'll work good for a little bit then I'll see the below µTorrent logging and shortly afterwards I observe often big decrease in transfer speed.

[2009-10-16 12:35:25] UPnP(XP): TCP port 6882 -> 192.168.1.10:6882 is already mapped. Not re-mapping.

[2009-10-16 12:35:25] UPnP(XP): UDP port 6882 -> 192.168.1.10:6882 is already mapped. Not re-mapping.

[2009-10-16 12:35:35] UPnP: Discovered host: http://192.168.1.1:5432/xml/igdIPDesc.xml

[2009-10-16 12:35:35] UPnP: Getting external IP

[2009-10-16 12:35:35] UPnP: Got external IP: 142.68.x.y

The green triangle still shows, the yellow triangle can take a bit for it to appear to indicate a problem. But while still on green triangle, I do the µTorrent Port test in µTorrent 'Speed Guide', and the test page will show there's a problem. Every-time manually de-checking and applying then re-checking 'Enable UPnP port mapping' and applying in Connection, under 'Listening Port', she'll work good for a little bit again.

Regards,

Phant0m``

Posted

I have no answer as to why it doesn't map the port from startup, but as for the "is already mapped. Not re-mapping." thing, that has nothing to do with anything. µTorrent always attempts to remap ports periodically to ensure that the router didn't drop the map (either because it is stupid, or because it restarted), and it doesn't (and couldn't logically) affect speed just to check if a port is open. Purely coincidence -- perhaps unless your router sucks.

Posted

Hi Ultima,

Thanks for responding.

I know just some short seconds after seeing the two entries '* port 6882 -> 192.168.1.10:6882 is already mapped. Not re-mapping.' appear, visiting uTorrent 'Speed Guide' and doing 'Test if port is forwarded properly', it reveals port error every-time "Port 6882 does not appear to be open.".

To address the problem I have to every-time manually de-checking and applying then re-checking 'Enable UPnP port mapping' and applying in Connection, under 'Listening Port', she'll work good for a little bit again.

Regarding 'UPnP: Unable to map port 192.168.1.10:6882 with UPnP.', isn't there something in uTorrent I can adjust to correct this or at least have it do some more retries? I find it somewhat annoying to have to every-time manually de-checking and applying then re-checking 'Enable UPnP port mapping' and applying in Connection, under 'Listening Port', .. to have it do what it suppose to.

Running Vista x64, and uTorrent 1.8.4 build 16688.

Regards,

Phant0m``

Posted

Hi Phant0m``,

UPnP problems are reported very often, because many routers have very broken UPnP implementations.

For problems like this, please send the following:

A wireshark log taken while the problem was happening (including the speedguide test).

The exact model number of your router.

Regards

Posted

Thanks Firon, an E-mail have been sent.

Edit: Hi,

I've did some more investigating, and here is what I came up with thus far.

My Router is already listed in Vista Network, but when I start the uTorrent application, the router entry quickly disappears and I'm seeing the below logging. So I guess uTorrent application forces an SSDP Discovery, but the problem is every-time ... uTorrent logs the 'UPnP: Unable to map port 192.168.1.10:6882 with UPnP.' message and JUST SHORTLY after that the Router entry re-appears in Vista Network. Is there a means through uTorrent to disable its SSDP Discovery attempt? Or have it 'retrying' just a tad bit longer? Or have it recycle through this startup phase after reaching the 'Unable to map port' message? I mean if we have uTorrent UPnP enabled, it shouldn't be so quick to call it quits.

[*] IPv6 is installed

[*] UPnP: Could not map UPnP Port on this pass, retrying.

[*] UPnP: Could not map UPnP Port on this pass, retrying.

[*] UPnP: Could not map UPnP Port on this pass, retrying.

[*] UPnP: Unable to map port 192.168.1.10:6882 with UPnP.

Bests Regards,

Phant0m``

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...