equitable traffic diversion (bittorrent vs. http)?

Hi,

I have 5 places connected using different access points around the town
using wifi (every place has one IP), and all share granted 512k full duplex
line shaped on the gateway of that ISP. It works as expected, but when on
one place runs bittorrent, it will eat all the bandwidth and for the
remaining 4 IPs the line becomes very slow. The winner of the battle is
that place which has more threads open.

Is there a way to rightly divide the load, no matter how many parallel
threads are open? If 3 places want to download, everyone should get 3/5 of
512k, but when others are idle, one should get full 512k. The goal is that
one place running 100 threads using bittorrent and the other place using
one thread only gets the same piece of cake

My ISP told me this ain't possible. I doubt about it, so i'm asking yet
here Is this possible? And if it is, then how - using a shaper, qos,...
whatever?

Thanks for any ideas,

Y.

Yandos wrote:
> Hi,
>
> I have 5 places connected using different access points around the town
> using wifi (every place has one IP), and all share granted 512k full duplex
> line shaped on the gateway of that ISP. It works as expected, but when on
> one place runs bittorrent, it will eat all the bandwidth and for the
> remaining 4 IPs the line becomes very slow. The winner of the battle is
> that place which has more threads open.
>
> Is there a way to rightly divide the load, no matter how many parallel
> threads are open? If 3 places want to download, everyone should get 3/5 of
> 512k, but when others are idle, one should get full 512k. The goal is that
> one place running 100 threads using bittorrent and the other place using
> one thread only gets the same piece of cake
>
> My ISP told me this ain't possible. I doubt about it, so i'm asking yet
> here Is this possible? And if it is, then how - using a shaper, qos,...
> whatever?
>
> Thanks for any ideas,
>
> Y.


Yandos,

Yes this is possible. You can use HTB to put them into classes and then
limit the classes to certain bandwidth requirements.

Bittorrent makes this a little less effective since it has so many
connections. We suggest you put generic high port traffic into a queue
with a lower bandwidth ceiling. Even lower for TCP 6881.

You can also branch out to subclasses. Such as:

Location 1 100 min 500 max
IP1 10/50
IP2 10/50
....

Location 2 200 min 1000 max
network 1 100/1000
IP1 10/50
IP2 10/50

This is to avoid "location 1" using all the bandwidth. It also limits
users at "location 1" from using all of "location 1"'s bandwidth.


Here is an overview:

http://www.paisleysystems.com/produc...ntdoor/traffic


There are links on the right side under "See Also" which will help
explain HTB further.


Scott R. Haven
Sr. Systems Engineer
Paisley Systems Inc.
managed services, consulting, and support
www.paisleysystems.com