From: Herman <Herman@AerospaceSoftware.com>
To: Jeremy Jones <jeremy@samnjack.com>, netfilter@lists.netfilter.org
Subject: Re: Bridge question
Date: Fri, 17 Oct 2003 07:52:17 -0600 [thread overview]
Message-ID: <200310170752.17546.Herman@AerospaceSoftware.com> (raw)
In-Reply-To: <1066397839.29597.6.camel@jccn-crux-linux.djc.state.id.us>
Aaaaaaaaah... Thanks Jeremy!
I think ebtables is exactly what the doctor ordered.
I'll try my bridge+iptables kludge - explained in another post - as well and
see which one we get to work properly first - we are running short on time
with this project.
Cheers,
Herman
On Friday 17 October 2003 7:37 am, Jeremy Jones wrote:
Herman,
in addition to the bridge.sourceforge.net pages, have a look at
ebtables.sourceforge.net. the howto documentation you'll find at, say,
tldp.org is a little out of date, but at ebtables, you may find more
helpful info. i've been using the bridging code & netfilter-bridge
kernel patch with 2.4.x for a while now, along with ebtables (analagous
to iptables, but filters at layer 2), and it's doing wonders for me.
good luck,
Jeremy
On Thu, 2003-10-16 at 21:15, Herman wrote:
> Hi everybody,
>
> This question is not about iptables, but it is closely related, so
somebody
> might know the answer:
> I am trying to construct a bridge, to filter 802.1q tags and protect a
legacy
> version 2.2 kernel server, while preserving port to port security on
the LAN,
> using the VLAN module.
>
> Can anybody refer me to some documentation on filtering on a bridge
for the
> 2.4 kernel?
>
> Regards,
next prev parent reply other threads:[~2003-10-17 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 22:02 Isolate a legacy machine Ringer, Torleiv
2003-10-17 3:15 ` Bridge question Herman
2003-10-17 3:46 ` Mark E. Donaldson
2003-10-17 8:39 ` tsh
2003-10-17 13:49 ` Herman
2003-10-17 13:37 ` Jeremy Jones
2003-10-17 13:52 ` Herman [this message]
2003-10-17 3:52 ` Isolate a legacy machine Bill Chappell
2003-10-17 4:37 ` Joel Newkirk
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=200310170752.17546.Herman@AerospaceSoftware.com \
--to=herman@aerospacesoftware.com \
--cc=jeremy@samnjack.com \
--cc=netfilter@lists.netfilter.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 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.