outgoing port range ignored

[Stedevil]

Hi

I run deluge on ubuntu 8.10 i386 and just updated to 1.1.0.

According to changelog you have

* Implement #79 ability to change outgoing port range

But when I try to set the sendports to eg 32881-32889 and specify tcp --sport 32881:32889 -j ACCEPT for iptables I get nothing but dropped packets, pretty much all of them from about sport 35000-60000

So it seems to me my outgoing portrange is simply ignored. I tried restarting Deluge a number of times, but the problem seems persistent. Am I the only one having these problems (or is just noone else filtering outgoing traffic?)

[gazpachoking]

I tried to set up some traffic shaping on the outgoing traffic based on the outgoing port with no luck. I also tried to do it with the tos bit and couldn't get that to work either. There is however a distinct possibility that I failed to set up my filters correctly. Anyone out there using this feature and got it working?

[Stedevil]

Yes, seems the UI in general dont affect the backend at all when it comes to outgoing stuff.

Putting --sport 30000:65535 for my firewall makes it stop blocking things, so it's not my firewall acting up either. So that verifies the portsvalues I set is just simply ignored.

[andar]

I've fixed the TOS byte in svn and I am currently working on fixing the outgoing ports bug.. Both of these fixes will be in 1.1.1.

[Stedevil]

Great

[gazpachoking]

Just upgraded to 1.1.1 and my traffic shaper can now filter my outgoing torrent traffic based on tos byte, nice! It was a bit confusing as (at least in my router, running vyatta) tos byte has been replaced with dscp, so I had to find a table to translate the tos value to dscp.
Thanks!