advanced setting "net.outgoing_port" incorrectly implemented

[maxe]

hello ludde,

long time ago we (me and some other users) requested the feature for µtorrent to be able to set the outgoing ports. i see with beta 453 you included such a feature but unforntunately you didn't implement it correctly. also we didn't request to be able to set *one* single port for the outgoing connections BUT we requested to be able to set an outgoing port *range*.

with your current implementation setting up the single outgoing port produces an error from all connected trackers and timeouts/breaks the connections to them.

also in this case the torrents are going very slow as every outgoing connection breaks each other. a connection tracking tool also proves that.

the error message generated from the trackers is that only one single source port can be used for every connection, obviously.

one very easy way for you to correct this now would be to let µtorrent simply additionally use the higher ports than the one set up as the outgoing port.

so you can leave this advanced setting like it is now, the user only sets the *first* outgoing port and µtorrent adjusts the outgoing port range by itself.

so when a user sets up "12345" as the outgoing port then µtorrent should use the range 12345-12999 or even 12345-14000 if it needs more ports/connections.

µtorrent should dynamically adjust the last outgoing port by its needed number of outgoing connections. when µtorrent opens a second outgoing connection then it should adjust the port range to 12345-12346. when the last used port is being closed then the range should be adjusted to 12345-(lastport-1). when a random port inside the range is being closed then the range should not be changed but the next outgoing connection has to use that free source port.

moderators, please hand this important information over to ludde and/or others involved in the development process.