From: Harald Welte <laforge@gnumonks.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Ben Greear <greearb@candelatech.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@muc.de>
Subject: Re: [PATCH] arp_filter patch for 2.4.4 kernel.
Date: Sun, 13 May 2001 19:39:56 -0300 [thread overview]
Message-ID: <20010513193956.P26722@corellia.laforge.distro.conectiva> (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 Miller wrote:
> > No idea, haven't tried to use netfilter. With this patch, though,
> > it's as easy as:
>
> I know, the problem is if some existing facility can be made
> to do it, I'd rather it be done that way.
of course.
> I'd be interested in seeing netfilter rules or a new netfilter
> kernel module which would do arpfilter as well.
the problem is, that netfilter hooks are currently only in the IPv4
and IPv6 packet paths. as ARP is not an IPv4 protocol, but another
protocol residing at layer 3, the arp code bypasses all netfilter hooks,
and is - as a result - not handled by any IP tables.
If you would want to do it using netfilter (the hooks only) and a hook-
attaching module, you need to add ARP netfilter hooks first.
If you want to filter arp packets, you need the netfilter hooks in the ARP
code, as well as a new 'arptables' module and a userspace tool allowing
modification of those arp tables.
So I see no clean solution for using netfilter in this case. It's one
of the scenario where netfilter/iptables layer-three-protocol boundness
hurts.
> David S. Miller
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
next prev parent reply other threads:[~2001-05-15 20:49 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
2001-05-13 22:39 ` Harald Welte [this message]
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=20010513193956.P26722@corellia.laforge.distro.conectiva \
--to=laforge@gnumonks.org \
--cc=ak@muc.de \
--cc=davem@redhat.com \
--cc=greearb@candelatech.com \
--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
all inboxes | Powered by JetHome®