From: Patrick Schaaf <bof@bof.de>
To: Joe Patterson <jpatterson@asgardgroup.com>
Cc: netfilter@lists.samba.org
Subject: Re: bridging with iptables (was no subject)
Date: Sun, 30 Jun 2002 09:13:42 +0200 [thread overview]
Message-ID: <20020630091342.U4136@oknodo.bof.de> (raw)
In-Reply-To: <NJEFLNJDIFFNMHDEBKMJGEJGDOAA.jpatterson@asgardgroup.com>; from jpatterson@asgardgroup.com on Sun, Jun 30, 2002 at 12:01:34AM -0400
Hi Joe,
> Does anyone know how netfilter deals with non-ip protocols?
Yes. It doesn't deal with them at all, as delivered "out of the box".
Here's a dump of what I know about the situation:
- netfilter is a set of hooks placed in stratetic places in the L3 networking
stack. Right now there are hooks for IPv4, IPv6, ARP, and I think there's
also something for DecNET, which I don't now nothing about.
- the hooks are all _inside_ the L3 stack.
- iptables is a user of the hooks put into the IPv4 stack.
- ip6tables is a user of the hooks put into the IPv6 stack.
- arptables is a user of the hooks put into the ARP stack.
- there is a patch to place netfilter hooks into the bridge code,
which _may_ be capable of filtering by ethernet protocol type.
I have not used it or looked closely. See http://bridge.sourceforge.net/
I don't think that there is any code right now which is able to filter
on IPX or AppleTalk header fields.
best regards
Patrick
next prev parent reply other threads:[~2002-06-30 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 22:39 bridging with iptables (was no subject) riffraff
2002-06-28 22:53 ` Antony Stone
2002-06-28 23:50 ` Martin Josefsson
2002-06-30 4:01 ` Joe Patterson
2002-06-30 7:13 ` Patrick Schaaf [this message]
2002-06-30 12:21 ` Martin Josefsson
[not found] <000901c1000a$8aaa63e0$4d2848c7@shaggy>
2002-06-28 19:48 ` (no subject) Antony Stone
2002-06-28 20:02 ` Patrick Schaaf
2002-06-28 20:00 ` Antony Stone
2002-06-28 22:22 ` bridging with iptables (was no subject) Jack Bowling
2002-06-28 22:29 ` Antony Stone
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=20020630091342.U4136@oknodo.bof.de \
--to=bof@bof.de \
--cc=jpatterson@asgardgroup.com \
--cc=netfilter@lists.samba.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