net.ougoing_port and net.outgoing_max_port not working correctly? 2.1

[Napsterbater]

I don't think its working correctly at least it dosn't make sense, but could a developer confirm?

UT 2.1 b19623 on Windows 2003 R2 sp2

My understanding is net.ougoing_port is the only/lowest port used and net.outgoing_max_port is the highest port used for outgoing communication, now I have 40000 and 40500 set respectively for QOS reasons (any packet originating on those ports are lowest priority) but it appears that utorrent on only using port 40000 as a source port, every connection has that as a source port except for respones to request on the incoming port (10000 in this case), now normally utorrent uses a different Ephemeral port for each connection am i right? so shouldn't the defined range be used like Ephemeral ports instead of just using the first available post in the range for all outgoing connections?

Also I would assume this explains the "Only one usage of each socket address (protocol/network address/port) is normally permitted."

It just doesn't really make sense for it to behave the way it is, unless there is a technical reason.

[oyabun]

Trying to do the exact same thing on Windows 7 x64, using client version 2.2b 22538. No matter what port I set in "net.outgoing_max_port" and "net.outgoing_port", uTorrent just keeps on using random ephemeral ports for seeding.

I want to throttle μTorrent via my router's traffic shaping features in order to minimize upload bandwidth usage whenever my mail client, VNC or VPN needs it, but this stops me from accomplishing this.

Why are those options not working?

Thank you for your work.

[oyabun]

I had tried the following values that hadn't worked (each time restarting the client)

port - max

50000 - 50100

18365 - 18365 (18365 is my incoming port)

18365 - 18366

The above values didn't work. Then, after I posted this, I tried the 40000 - 40010 range, like Napsterbater was trying to use and it worked!

Can anyone explain this? Must ports specified lie outside the ephemeral port range and outside the incoming port range? (I know that you are using the specified incoming port for UDP outgoing traffic).

[GTHK]

Looking at source or destination port?

[oyabun]

Looking at source or destination port?

Always at source port, destination depends on the remote client.

[Switeck]

In my own tests, I couldn't use the same outgoing port as incoming port...not without extreme problems anyway.

When you define a range, only the first port is used UNLESS there's a conflict with already connected ips...then only the first port after that is used. Generally, there is not...so only the first outgoing port is used with the second port used only intermittently.

[oyabun]

What about the ephemeral port range? Are we allowed to specify a port from that range or is it a no-no, like I observed with port 50000?

[Switeck]

As far as I know, You can use a listening port in the ephemeral range.