From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Ben Greear <greearb@candelatech.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@muc.de>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] arp_filter patch for 2.4.4 kernel.
Date: Sun, 6 May 2001 10:40:37 +0200 [thread overview]
Message-ID: <20010506104037.C29403@gruyere.muc.suse.de> (raw)
In-Reply-To: <3AF4720F.35574FDD@candelatech.com> <15092.32371.139915.110859@pizda.ninka.net> <3AF49617.1B3C48AF@candelatech.com> <15092.37426.648280.631914@pizda.ninka.net>
In-Reply-To: <15092.37426.648280.631914@pizda.ninka.net>; from davem@redhat.com on Sat, May 05, 2001 at 04:52:18PM -0700
On Sat, May 05, 2001 at 04:52:18PM -0700, David S. Miller wrote:
> > I have a setup that should be able to test some netfilter rules
> > if have some you want me to try....
>
> I'd be interested in seeing netfilter rules or a new netfilter
> kernel module which would do arpfilter as well.
I don't think it's a good idea. You either need a lot of hooks in the
arp input path for all the different cases or you would need to replicate
a lot of the arp.c logic into that netfilter module. Both not good.
IMHO it's better to just control replies via the routing table,
which already has all kinds of fancy mechanisms for it. In addition I haven't
seen a setup yet that couldn't be handled by arpfilter and the routing
table, it seems to be flexible enough for all practical purposes.
-Andi
next prev parent reply other threads:[~2001-05-06 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 0:08 Ben Greear
2001-05-05 21:35 ` Ben Greear
2001-05-05 22:28 ` David S. Miller
2001-05-05 22:53 ` dean gaudet
2001-05-05 22:57 ` dean gaudet
2001-05-06 8:34 ` Andi Kleen
2001-05-06 16:35 ` Mark Hahn
2001-05-05 23:27 ` David S. Miller
2001-05-05 23:52 ` David S. Miller
2001-05-06 7:20 ` Ben Greear
2001-05-06 8:40 ` Andi Kleen [this message]
2001-05-13 22:39 ` Harald Welte
2001-05-07 16:35 ` Matthew Kirkwood
2001-05-13 6:37 ` Ben Greear
2001-05-13 7:45 ` David S. Miller
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=20010506104037.C29403@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®