All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: uniplex <uniplex@maximum-linux.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: -m recent
Date: Thu, 23 Jan 2003 14:15:05 -0500	[thread overview]
Message-ID: <20030123191505.GL484@ns.snowman.net> (raw)
In-Reply-To: <3E2FEA1C.9030305@maximum-linux.net>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

* uniplex (uniplex@maximum-linux.net) wrote:
> Has anyone here had any luck with this?

It works for me and I use it, though, well, I wrote it too, so.. :)

> It's logging the ip and ttl etc etc in the file it's supposed to, but 
> the --update -j DROP rule I'm using doesn't seem to have any effect.
> 
> Here's a snip of rules from my script that I've been using to test with. 
> I've put them in the same order as they appear in the script. It's not 
> the entire script(of coarse) and I'm matching to icmp packets just to 
> test with.
> 
> iptables -A INPUT -i eth0 -p all -m recent --name icmps --update -j DROP
> 
> iptables -N icmps
> iptables -A INPUT -i eth0 -p icmp -j icmps
> iptables -A icmps -m recent --name icmps --set -j DROP
> iptables -A icmps -j DROP

This looks good to me..  Can you tell me what version of ipt_recent
you're using?  An old version had a bug where the --name only worked
when it was the last option, that may be the problem.

	Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-23 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 13:11 -m recent uniplex
2003-01-23 19:15 ` Stephen Frost [this message]
2003-01-23 15:59   ` uniplex
2003-01-23 22:40     ` Stephen Frost
2003-01-24  2:03       ` uniplex
2003-01-24  8:15         ` Fabrice MARIE
2003-01-25  1:29         ` Stephen Frost
2003-01-30 19:50           ` uniplex
2003-02-24 13:59             ` Stephen Frost

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=20030123191505.GL484@ns.snowman.net \
    --to=sfrost@snowman.net \
    --cc=netfilter@lists.netfilter.org \
    --cc=uniplex@maximum-linux.net \
    /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.