Jump to content

uTorrent & UPnP: opening/closing ports properly in router


niktarace

Recommended Posts

Posted

Hi.

It's surely more a clarification than a real issue.

I'm using a router Sagem (Livebox) where UPnP is enabled ; it's an easy feature to forward port without adding manually a rule in the router setup.

Anyway I think uT doesn't close a port previously used when it try to open a new one after switching from wireless to ethernet connection.

Example:

I started uT with wireless connection (local IP 192.168.1.11) & port 54321.

[2009-01-08 10:52:04] UPnP(XP): TCP port 54321 -> 192.168.1.11:54321 mapped successfully.

[2009-01-08 10:52:05] UPnP(XP): UDP port 54321 -> 192.168.1.11:54321 mapped successfully.

[2009-01-08 10:52:07] UPnP: Discovered host: http://192.168.1.1:2555/upnp/...

[2009-01-08 10:52:07] UPnP: Discovered new device: "Passerelle internet Sagem" http://192.168.1.1:2555/upnp...

[2009-01-08 10:52:07] UPnP: Getting external IP

[2009-01-08 10:52:07] UPnP: Got external IP: XXX

Rules about 192.168.1.11:54321 added in the router.

Green icon in uT.

I switched from wireless to ethernet (local IP 192.168.1.10) with same port set in uT.

Orange icon in uT.

[2009-01-08 11:12:07] UPnP(XP): TCP port 54322 -> 192.168.1.10:54321 mapped successfully. <-- uT tries port 54322

[2009-01-08 11:12:09] UPnP(XP): UDP port 54322 -> 192.168.1.10:54321 mapped successfully. <-- uT tries port 54322

[2009-01-08 11:12:12] UPnP: Could not detect external IP on this pass, retrying.

[2009-01-08 11:12:17] UPnP: Could not detect external IP on this pass, retrying.

[2009-01-08 11:12:22] UPnP: Could not detect external IP on this pass, retrying.

[2009-01-08 11:12:27] UPnP: Unable to get external IP with UPnP.

Rules about 192.168.1.10:54322 added in the router.

Rules about 192.168.1.11:54321 stayed in the router.

Green icon in uT.

uT removed previous rules about 192.168.1.11:54321 and added new 192.168.1.10:54321.

[2009-01-08 11:32:29] UPnP: Discovered host: http://192.168.1.1:2555/upnp/...

[2009-01-08 11:32:29] UPnP: ERROR mapping TCP port 54321 -> 192.168.1.10:54321. Deleting mapping and trying again: (718) The port mapping entry specified conflicts with a mapping assigned previously to another client

[2009-01-08 11:32:30] UPnP: Removed TCP port 54321

[2009-01-08 11:32:31] UPnP: Mapped TCP port 54321 -> 192.168.1.10:54321

[2009-01-08 11:32:31] UPnP: TCP port 54321 -> 192.168.1.10:54321 mapped successfully.

[2009-01-08 11:32:31] UPnP: ERROR mapping UDP port 54321 -> 192.168.1.10:54321. Deleting mapping and trying again: (718) The port mapping entry specified conflicts with a mapping assigned previously to another client

[2009-01-08 11:32:32] UPnP: Removed UDP port 54321

[2009-01-08 11:32:33] UPnP: Mapped UDP port 54321 -> 192.168.1.10:54321

[2009-01-08 11:32:33] UPnP: UDP port 54321 -> 192.168.1.10:54321 mapped successfully.

[2009-01-08 11:32:33] UPnP: Getting external IP

[2009-01-08 11:32:33] UPnP: Got external IP: XXX

Rules about 192.168.1.10:54322 stayed in the router.

Green icon in uT.

The conclusion is uT has incremented port 54321 to 54322 when I switched to ethernet but didn't close 54322 after having used it and reforwared port 54321...

Is there any way to prevent that ?

Thank you.

  • 1 month later...
Posted

I have had similar messages with d-link di-704up without wireless issue. Baffled I fiddled. I invoked my uT 1.8.1 preferences > Connection and unchecked the enable UPnP check box - applied - same same no effect - got fresh log error messages - again I invoked my uT preferences > Connection and this time CHECKED the enable UPnP check box - applied - and magic happing - box going so fast I will finish and make the pub on time - reasons why part 2 - no idea at all - just loved the result - best of luck niktarace

Archived

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

×
×
  • Create New...