Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: David DeLauro <daved@saintjoe.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Dynamic Ratelimiting
Date: Mon, 29 Dec 2003 15:08:06 +0000	[thread overview]
Message-ID: <marc-lartc-107271140309119@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107219671428584@msgid-missing>

On Tue, 23 Dec 2003 At 21:28 +0100, gdamjan@mail.net.mk Articulated:

>
> Very interesting, I'll look more in depth to your scripts ... do you
> think it would be easy to change the decission of who to ratelimit, from
> the number of connections to the bandwidth they are using?
>
> Something like, if this user is using 512kb for 5 minutes ratelimit him?

Right now the scripts are just using a standard sniffer (tcpdump or
tethereal) to gather information about the connections.  For sure adding
the ability watch bandwidth as well would be something I'm looking into
adding... I haven't figured an efficient way to do it yet without parsing
datagrams myself for HLEN and TOTAL LENGTH.

>
>

-- 
David DeLauro

Do not handicap your children by making their lives easy. - Robert Heinlein

If the soul could know God without the world, the world would never have been created. - Meister Eckhart

Hata ukinichukia la kweli nitakwambia - Kanga Proverb

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-12-29 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 16:16 [LARTC] Dynamic Ratelimiting David DeLauro
2003-12-23 20:28 ` Damjan
2003-12-26 15:18 ` Anderson O Muniz
2003-12-27  1:43 ` arek
2003-12-29 14:42 ` Anderson O Muniz
2003-12-29 15:08 ` David DeLauro [this message]
2003-12-29 15:11 ` David DeLauro

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=marc-lartc-107271140309119@msgid-missing \
    --to=daved@saintjoe.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox