Deluge Forum

I would like to have some explanation, because it doesn't seem to be a real problem.
I'm working with ubuntu 7.10 amd64 version and deluge 0.5.7.95. I'm behind a firewall (software..firestarter) and a nat (hardware..a router), so i set a range of 9 ports of my choice in the preferences, allow them for outgoing and ingoing connections in firestarter and finally set port forwarding for them in my router.
Everything is working fine, i passed the connection test, can download pretty fast and upload too.
The thing i don't understand is why there are many and many tcp outgoing connection attempts blocked by my firewall, with very random port numbers and standard torrent port numbers too. This happens only when Deluge is running.
If i decide to use some ports, why the program tries to use other ones? I tried to shut down the firewall to allow all those connections, and i didn't see any improvement in bandwith, so i really don't understand if this is a problem or not.

Thank you in advance, and sorry if my english is not good.

dottoreDIvino wrote:I would like to have some explanation, because it doesn't seem to be a real problem.
I'm working with ubuntu 7.10 amd64 version and deluge 0.5.7.95. I'm behind a firewall (software..firestarter) and a nat (hardware..a router), so i set a range of 9 ports of my choice in the preferences, allow them for outgoing and ingoing connections in firestarter and finally set port forwarding for them in my router.
Everything is working fine, i passed the connection test, can download pretty fast and upload too.
The thing i don't understand is why there are many and many tcp outgoing connection attempts blocked by my firewall, with very random port numbers and standard torrent port numbers too. This happens only when Deluge is running.
If i decide to use some ports, why the program tries to use other ones? I tried to shut down the firewall to allow all those connections, and i didn't see any improvement in bandwith, so i really don't understand if this is a problem or not.

Thank you in advance, and sorry if my english is not good.

the single port, aka active port, is the incoming port. however, when making outgoing connections, programs use a random port number. you can test this while surfing the net, even. yes, the browser is going to port 80 on the server, but on the localhost it opens up another port to talk to it.

markybob wrote:the single port, aka active port, is the incoming port. however, when making outgoing connections, programs use a random port number. you can test this while surfing the net, even. yes, the browser is going to port 80 on the server, but on the localhost it opens up another port to talk to it.

First of all thank you for your christmas answer
Ok i focused the problem..when i surf the net i have only to set an outgoing rule for my firewall, because it remembers the random port from which i generated the request..because of the freedom of choosing the incoming port for deluge, i should set as outgoing rules all the ports choosed by other peers i connect to, and that's obviously impossible. Am i right? Is there a way to bind a rule to a program, like windows firewalls do? And why it seems there are no drawbacks on bandwith?