Hi,
I can't seem to allocate the ports I want to in Ktorrent. It's more an issue of setting the ports I want to use for Ktorrent, as I know how to do this in Firestarter.

I open the 6881 and 4444 ports, but then Ktorrent starts grabbing at ports in the 10000+ range, at random. I want to specify these.

I'm aware in reading other posts that you can run in Permissive Mode, but for me this is unacceptable. As someone tends to close all my windows and re-route my adapter to a point that is non-existent.

In short: Is there a way to specify the ports other than the standard and UDP tracker ports?

Thanks.

Hello,

try TCP ports larger then 50000...

PEace

Thanks for the info, but exactly where is it I set this. I can't find any settings for ports except the common port and tracker ports.

I set these two in the general options setting panel, but I don't know where the others are.

Hello,

You only need to set TCP Incomming port in General panel and noware else. The traker port is optional.

Peace
PS: disable DHT

noaccess wrote:I open the 6881 and 4444 ports, but then Ktorrent starts grabbing at ports in the 10000+ range, at random. I want to specify these.

6881 and 4444 are for incoming things, when KT itself starts setting up connections to other peers, it will just pick random free ports (actually we let the OS do this). These ports are not configurable.

Yeah, outgoing ports are randomly chosen by the Linux kernel's TCP stack. It's the same way that you can't choose what port Firefox uses to communicate with web servers, except in that case you KNOW most webservers are on port 80 or 443. With KTorrent, you can't really write explicit outbound rules via Firestarter. It's only practical to use iptables application matching to allow /usr/bin/ktorrent all outbound access.

jdong wrote:Yeah, outgoing ports are randomly chosen by the Linux kernel's TCP stack. It's the same way that you can't choose what port Firefox uses to communicate with web servers, except in that case you KNOW most webservers are on port 80 or 443. With KTorrent, you can't really write explicit outbound rules via Firestarter. It's only practical to use iptables application matching to allow /usr/bin/ktorrent all outbound access.

Actually technically it is perfectly possible to do this (just a matter of calling bind on a socket, before calling connect). It's just that there aren't many reasons to do this. And I fail to see how such a feature would be usefull to anybody.