From: Peteris Krumins <newsgroups@lf.lv>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] per-session QoS
Date: Wed, 04 Feb 2004 23:44:04 +0000 [thread overview]
Message-ID: <81108570265.20040205014404@lf.lv> (raw)
Wednesday, February 4, 2004, 11:15:17 PM, you wrote:
B> That's the closest thing I've seen to what I want, but it's not quite
B> there. From what I understand, this lets me identify all sessions that
B> have sent more than x bytes.
Right.
B> I want something that says "for every session going to port x, limit
B> incoming throughput to no more than 50KB/5s" - or some other throughput
B> definition that allows bursting.
Well, that is easy.
Create as many classes needed, add filters based on MARK value to put
the traffic in the correspoing classes, then simply put the connbytes
rules (-m connbytes max_bw:) together with a jump to MARK target
(-j MARK) in the mangle table.
As soon as max_bw will be reached, the packet will get marked and the
filter will put the traffic in the appropriate class.
P.Krumins
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-02-04 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 23:44 Peteris Krumins [this message]
2004-02-05 0:48 ` Re[2]: [LARTC] per-session QoS Ben
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81108570265.20040205014404@lf.lv \
--to=newsgroups@lf.lv \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.