From: Nuutti Kotivuori <naked@iki.fi>
To: netfilter@lists.netfilter.org
Subject: Per connection transfer rate matching
Date: Thu, 05 Feb 2004 00:31:30 +0200 [thread overview]
Message-ID: <877jz2iiil.fsf@iki.fi> (raw)
I have recently trying to find a solution to a QoS problem of sorts.
What I would wish to be able to do, is to mark a connection based on
the data transfer rate in that connection. That is, to have some sort
of a token bucket filter or rate estimator attached to a certain
connection tracking connection - and to be able to use that in
netfilter rules.
An example problem case is trivial. Let's assume we have an
interactive transfer class, which has several interactive sessions
where latency is tried to be kept to a minimum. Occasionally some
interactive session might start transferring a lot of data - in which
case it should be scheduled into the maximum throughput class,
forgetting latency, until it doesn't transfer that much and it should
be returned to the interactive class again.
The 'connbytes' match in the patch-o-matic matches on cumulative
transfer amounts on a per connection basis. The 'limit' match matches
packets on a simple token bucket implementation. Combining these two
to something which matches bytes on a simple token bucket per
connection would create the desired result.
So, does such a thing exist already? If not, do other people see this
as useful as I do? Or have I missed something crucial?
And finally, if it doesn't exist already, making such a module
shouldn't be too hard - would anyone be willing to undertake such an
ordeal?
-- Naked
next reply other threads:[~2004-02-04 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 22:31 Nuutti Kotivuori [this message]
2004-02-05 7:28 ` Per connection transfer rate matching Ray Leach
2004-02-10 18:02 ` Nuutti Kotivuori
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=877jz2iiil.fsf@iki.fi \
--to=naked@iki.fi \
--cc=netfilter@lists.netfilter.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.