1.7 2152 UPnP maps different Port than the one i set

[tomte]

Sorry got the Build wrong in topic title! Meant Build 2151 not 2152!

Since Update to Beta 2151 this happens:

UPnP: Discovered new device blabla...

UPnP: mapped port 55561 --> 192.168.2.103:55556

Well, i set uTorrent to only use 555556 and so far it had this Port mapped through.

Now, when i look at my connection Details from the outside (e.g some Tracker) i can see my connections happening on 55561, the Port uTorrent obviously chose.

The Connectivity is fine though.

would this be a bug? or could it also mean that my router is just not letting uTorrent use Port 55556 for some reason?

Change Port every time i connect is disabled.

oh yes- and before i forget this: i have no idea how to switch on logging before uTorrent starts the connection- it wouldn't remember that i set it to log to file when i restart it. so the first few lines of the log, the important ones, are just missing all the time. could someone be so kind to point out how i do this? Thank you.

[olmari]

Well... I don't know answer to why it does it that way, but incoming port in router doesn't have to be same as the incoming port of your computer the data is routed to... So it is totally 'legal' thing to forward router incoming port 55561 to you computer incoming for 55556...

[Firon]

As far as I know, that happens when the port is already mapped in the router.

[Switeck]

Even closing and reopening µTorrent quickly might cause that.

[tomte]

Checked my router's NAT Tables. The Virtual Server still had an old setting for my previously used WLAN connection on Port 55556. Since i'm not using that adapter anymore and therefore don't use that ip neither i forgot to check on that connection. Totally forgot that if the port is mapped its mapped, no matter wether its active or not. so it was absolutely my fault and the timely coincidence with the update led me on a wrong trail...

thank you for the hints and:

sorry for spamming the forum with this