Graham Leggett wrote:
Hi all,
I have been trying to investigate traffic shaping in an effort to solve
the "unfriendly network apps" problem on a test network.
I have a basis by which I'd like to shape traffic, but studying the
howto doesn't uncover and existing qdisc that seems to fit what I would
like to do.
The problem I would like to address is to prevent an IP address opening
10 simultaneous streams from drowning out another IP address that opened
1 stream.
I would like to penalise IP addresses where two or more simultaneous
sessions are in effect, by adding a delay to the streams such that the
total bandwidth used by the IP address is capped at a declining curve.
In other words, assuming that the data you are sending is constrained
behind you by a 1mbps bottleneck.
When an IP has one session detected, their traffic is passed through,
and normal rules apply.
When an IP has two sessions detected, their combined sent traffic
towards the IP is delayed and shaped down to say 800kbps.
When an IP has three sessions detected, their combined sent traffic
towards the IP is delayed and shaped down to say 600kbps.
The starting point of how many sessions can be open before penalising
takes effect, the starting point of the curve and the gradient of the
curve would obviously be subject to lots of experimentation and would be
set by the admin.
The nett effect I am looking for, is that a user who chooses to open
multiple simultaneous streams, should see a noticable decrease in
maximum throughput, in an effort to discourage them from swamping the
network with sessions.
My question is, does a qdisc exist that implements something like this?
Is this a reasonable thing to do, or will a strategy like this not work,
and if not, why not? (for the purposes of me better understanding the
issues).
Regards,
Graham
I've my misgivings with this scheme.
What you are doing makes sense only if the number of connections is a
constrained resource. If bandwidth is the constraint, then shaping by
source IP irrespective of number of connections will do the job. As far
as I've seen, routers can support 200k connections and this is
sufficient for many large LANs - say 500 node LAN with 400 connections
per node.
In many cases, the user may not know how many connections he is opening
or which app is consuming connections. Thus, the user may not be in a
position to take remedial action and hence will be at a disadvantage.
I'm questioning the need for such a scheme really.
Mohan
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
