From: Esteban Ribicic <eribicic@sinectis.com>
To: George Vieira <georgev@citadelcomputer.com.au>
Cc: epv_xemul@mail.ru, netfilter@lists.netfilter.org
Subject: Re: Traffic limitation with iptables
Date: Tue, 22 Jul 2003 19:16:25 -0300 [thread overview]
Message-ID: <20030722191625.480036d9.eribicic@sinectis.com> (raw)
In-Reply-To: <09B04A55822EFF4DA48D2E0BB2941D4A15BF6B@wardrive.citadelcomputer.com.au>
that would not be shapping...ass dropping/rejecting packets implicates
much more yhing under tcp/ip..
maybe lartc.org may help too..(this is not the mailing-list i think)
fix me if im wrong
Esteban
On Wed, 23 Jul 2003 08:07:40 +1000
"George Vieira" <georgev@citadelcomputer.com.au> wrote:
> Use the Quota patch and it'll limit the rule by itself..
>
> Thanks,
> ____________________________________________
> George Vieira
> Systems Manager
> georgev@citadelcomputer.com.au
>
> Citadel Computer Systems Pty Ltd
> http://www.citadelcomputer.com.au
>
>
>
> -----Original Message-----
> From: Xemul [mailto:epv_xemul@mail.ru]
> Sent: Wednesday, July 23, 2003 2:09 AM
> To: netfilter@lists.netfilter.org
> Subject: Traffic limitation with iptables
>
>
> Hi.
> I wanna solve such a problem:
> When I see that byte counter on some chain reaches or exceedes any fixed
> value - then IMMEDIATELY insert into that cahin new first rule (e.g. -j
> DROP) or delete some rules from any other chain. Or more abstract - how
> can can discover that byte counter is higher than smth without
> "polling" chains?
>
> Sorry for sending such a mail into announce, developers and user
> maillists but I need help as soon as possible. :)
>
>
next prev parent reply other threads:[~2003-07-22 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 22:07 Traffic limitation with iptables George Vieira
2003-07-22 22:16 ` Esteban Ribicic [this message]
2003-07-23 15:17 ` Xemul
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 23:17 George Vieira
2003-07-22 16:08 Xemul
2003-07-23 0:19 ` Arnt Karlsen
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=20030722191625.480036d9.eribicic@sinectis.com \
--to=eribicic@sinectis.com \
--cc=epv_xemul@mail.ru \
--cc=georgev@citadelcomputer.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox