All of lore.kernel.org
 help / color / mirror / Atom feed
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ?OT? Linux 2.6: bridge + routing firewall
Date: Fri, 16 Feb 2007 13:37:10 +0000	[thread overview]
Message-ID: <1171633030.4769.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20070215154459.GC6325@softaplic.com.br>

I have some experience.

It seems that you should explicitely allow bridging in iptables as well
as in ebtables.

So, in addition to my bridge roules in ebtables I also have this rule in
iptables:

iptables -A FORWARD -i br0 -o br0 -j ACCEPT

Otherwise, it could block bridging by later rules or the policy.

В Чтв, 15/02/2007 в 13:44 -0200, Edesio Costa e Silva пишет:
> Hi All!
> 
> I need to deploy a bridge firewall using linux kernel 2.6. I had success
> using kernel 2.4 plus br-nf patch. But the configuration does not work with
> kernel 2.6.
> 
> If the default policy for the iptables FORWARD chain is ACCEPT I have a
> bridge. If iptables FORWARD chain is DROP I have an insulator (no packet
> flows). Any hint?
> 
> I did some google search and in many places they say "kernel 2.6 is not
> recommended", "no luck with kernel 2.6", etc.
> 
> Any link to a success story of a bridge firewall with kernel 2.6? Any
> personal experience?
> 
> Thanks in advance,
> 
> Edésio
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 
-- 
Покотиленко Костик <casper@meteor.dp.ua>

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-02-16 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 15:44 [LARTC] ?OT? Linux 2.6: bridge + routing firewall Edesio Costa e Silva
2007-02-16 13:37 `  [this message]
2007-02-16 14:12 ` tomdeb

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=1171633030.4769.10.camel@localhost.localdomain \
    --to=lartc@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 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.