All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Graham - Reg.CA" <graham@reg.ca>
To: "Cedric Blancher" <blancher@cartel-securite.fr>,
	"Jerome de Vivie" <jerome.de-vivie@wanadoo.fr>
Cc: <netfilter-devel@lists.netfilter.org>
Subject: Re: match limit with inverse [!]
Date: Fri, 29 Nov 2002 02:11:15 -0800	[thread overview]
Message-ID: <009d01c2978f$a7b6fca0$2a00a8c0@zorro> (raw)
In-Reply-To: 1038074008.8074.23.camel@elendil.intranet.cartel-securite.net

Thanks!  The new workaround is hardly as convenient, but we managed to work
out a workable set of rules in the end.  It would have saved us a lot of
confusion if the documentation (man iptables) of  didn't imply that the "!"
rule worked.

Still it would be nice to see the proper inverse work for a later release -
the "inverse" rule is hardly intuitive.

----- Original Message -----
From: "Cedric Blancher" <blancher@cartel-securite.fr>
To: "Jerome de Vivie" <jerome.de-vivie@wanadoo.fr>
Cc: "Graham- Reg.CA" <graham@reg.ca>; <netfilter-devel@lists.netfilter.org>
Sent: Saturday, November 23, 2002 9:53 AM
Subject: Re: match limit with inverse [!]


> Le sam 23/11/2002 à 19:24, Jerome de Vivie a écrit :
> > Your out of luck. The patch hasn't been applied because it a kernel
> > header and could disturb older versions of netfilter. The patch is under
> > http://perso.wanadoo.fr/jerome.de-vivie/ipt/
>
> However, we can emulate limit inverse with a user chain. Suppose you
> want to log and drop ICMPs that are over the 1/S limit :
>
> iptables -N inv_limit
> iptables -A FORWARD -p icmp -j inv_limit
> iptables -A inv_limit -m limit --limit 1/s -j RETURN \
> --log-prefix "Over limit ICMP "
> iptables -A inv_limit -j LOG
> iptables -A inv_limit -j DROP
> [...]
>
> That's only a workaround...
>
> --
> Cédric Blancher  <blancher@cartel-securite.fr>
> IT systems and networks security expert  - Cartel Sécurité
> Phone : +33 (0)1 44 06 97 87 - Fax: +33 (0)1 44 06 97 99
> PGP KeyID:157E98EE  FingerPrint:FA62226DA9E72FA8AECAA240008B480E157E98EE

      reply	other threads:[~2002-11-29 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00ae01c292ed$2c125aa0$2a00a8c0@zorro>
2002-11-23 18:24 ` match limit with inverse [!] Jerome de Vivie
2002-11-23 17:53   ` Cedric Blancher
2002-11-29 10:11     ` Graham - Reg.CA [this message]

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='009d01c2978f$a7b6fca0$2a00a8c0@zorro' \
    --to=graham@reg.ca \
    --cc=blancher@cartel-securite.fr \
    --cc=jerome.de-vivie@wanadoo.fr \
    --cc=netfilter-devel@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.