public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Buhr <buhr@telus.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stateless dropping of packets
Date: 01 Apr 2003 14:50:39 -0800	[thread overview]
Message-ID: <87d6k5ltmo.fsf@saurus.asaurus.invalid> (raw)
In-Reply-To: <87he9ilz05.fsf@deneb.enyo.de>

Florian Weimer <fw@deneb.enyo.de> writes:
>
> Is it possible to drop packets, preferably using 2.4 iptables, before
> the packet triggers updates of some caches (e.g. the route cache)?

If you DROP the packet in a PREROUTING chain, that should work.  Since
the "filter" table doesn't have a PREROUTING chain, you need to use a
table that does, like the "mangle" table.  For example:

        iptables -t mangle -A PREROUTING -s 10.0.0.0/8 -j DROP

should drop everything with a source in 10.0.0.0/8 without touching
the routing cache.

-- 
Kevin <buhr@telus.net>

  reply	other threads:[~2003-04-01 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 20:54 Stateless dropping of packets Florian Weimer
2003-04-01 22:50 ` Kevin Buhr [this message]
2003-04-02 15:02   ` Florian Weimer
2003-04-02 17:00     ` Kevin Buhr

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=87d6k5ltmo.fsf@saurus.asaurus.invalid \
    --to=buhr@telus.net \
    --cc=fw@deneb.enyo.de \
    --cc=linux-kernel@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