All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edesio Costa e Silva <edesio@softaplic.com.br>
To: lartc@vger.kernel.org
Subject: [LARTC] ?OT? Linux 2.6: bridge + routing firewall
Date: Thu, 15 Feb 2007 15:44:59 +0000	[thread overview]
Message-ID: <20070215154459.GC6325@softaplic.com.br> (raw)

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

             reply	other threads:[~2007-02-15 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 15:44 Edesio Costa e Silva [this message]
2007-02-16 13:37 ` [LARTC] ?OT? Linux 2.6: bridge + routing firewall 
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=20070215154459.GC6325@softaplic.com.br \
    --to=edesio@softaplic.com.br \
    --cc=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.