From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Omar Armas <oarmas@mpsnet.net.mx>
Cc: bridge@osdl.org
Subject: Re: [Bridge] problem bridging
Date: Thu, 25 Jan 2007 11:09:18 -0800 [thread overview]
Message-ID: <20070125110918.6531e49e@freekitty> (raw)
In-Reply-To: <7350AD3A-96AF-46D6-AEFF-9B855A993974@mpsnet.net.mx>
On Thu, 25 Jan 2007 13:08:23 -0600
Omar Armas <oarmas@mpsnet.net.mx> wrote:
> >
> > iptables FORWARD rules apply to routing not bridging
> >
> > See:
> > http://ebtables.sourceforge.net/br_fw_ia/br_fw_ia.html#section6
>
>
> I recompiled with kernel 2.6.19, included ebtables modules and now it
> is working, I can filter with iptables and the FORWARD chain.
> I just want to confirm, was that the correct way to do it? Would have
> it worked if I had patched 2.4 with ebtables?
>
Yes. if you don't have ebtables then the bridge does no filtering
>
--
Stephen Hemminger <shemminger@linux-foundation.org>
prev parent reply other threads:[~2007-01-25 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 20:19 [Bridge] problem bridging Omar Armas
2007-01-25 18:46 ` Stephen Hemminger
2007-01-25 19:08 ` Omar Armas
2007-01-25 19:09 ` Stephen Hemminger [this message]
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=20070125110918.6531e49e@freekitty \
--to=shemminger@linux-foundation.org \
--cc=bridge@osdl.org \
--cc=oarmas@mpsnet.net.mx \
/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