Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Scott MacKay <scottmackay@yahoo.com>
To: netfilter@lists.netfilter.org
Subject: Re: Iptables not working with RH9
Date: Thu, 20 Nov 2003 09:53:10 -0800 (PST)	[thread overview]
Message-ID: <20031120175310.69017.qmail@web13909.mail.yahoo.com> (raw)
In-Reply-To: <20031120171724.GB21892@cannon.eng.us.uu.net>

Very true.  To use iptables, you need a bridge patch,
such as ebtables on sourceforge.net.  It patches the
OS to allow netfilter to hook into bridge for the
rules.  Works fine!  I would suggest getting the
2.4.22 kernel, get the latest off of sourceforge
(under 'ebtables').
You get into the dist dir, do a patch -p1 < PATCHFILE,
use make menuconfig or whatever to activate the
modules and rebuild the kernel.  Works like a charm.


--- Ramin Dousti <ramin@cannon.eng.us.uu.net> wrote:
> I have no experience with bridging code on linux but
> one thing comes to mind
> about your setup. A bridge acts at layer 2.
> Netfilter is hooked into the IP
> layer (layer 3). So when you're bridging, I'd say,
> it's normal that the drop
> policy has no effect... Or I may be wrong...
> 
> Ramin
> 
> On Thu, Nov 20, 2003 at 10:54:41AM -0500, Derek
> Storvik wrote:
> 
> > Hello all
> >   Hopefully someone can see my error.   
> > I have been running RH7.3 with it's standard
> kernal version 2.4.18-3 for several months
> configured as a transparent bridging firewall. We
> recently purchased a new machine and wanted to
> install RH9 with its standard kernal 2.4.20( i
> think)I followed the same steps installed with
> iptables and bridging utils and used my same script
> file to setup the bridge with two nics and fill in
> all my rules. This didn't seem to work right and on
> further testing realized NOTHING was being filtered.
> I then rebooted and manualy set up the bridge and
> cleared all the tables and set the default policy to
> drop. SO at this point nothing should get through.
> Well it bridges everything, and the counters in
> iptables do not increment. The system acts as if it
> is not there what so ever.
> > 
> > here is the setup after the basic minimal install
> > brctl addbr br0
> > brctl addif br0 eth0
> > brctl addif br0 eth1
> > ifconfig eth1 0.0.0.0 promisc
> > ifconfig eth0 0.0.0.0 promisc
> > #bring up bridge with either of the next two
> commands
> > ifconfig br0 up
> > ip link set br0 up
> > #both do the same thing  namely nothing
> > iptables -X
> > iptables -F
> > iptables -P FORWARD DROP
> > iptables -P INPUT DROP
> > iptables -P OUTPUT DROP
> > 
> > This setup happily bridges packets right on
> through with no updates to the iptables counters.
> > 
> > I have been experimenting with devil linux as well
> recently and it exhibits the same problem. 
> > 
> > ip_forwarding is set to 0  as it has been on my
> working rh7.3 machine I tried setting it to 1 but
> that didn't help the problems. Im not 100% sure what
> exactl the ip_forwarding property corresponds to
> anyway.
> > 
> > any help would be greatly appreciated!
> >    Thanks
> >          Derek
> > 
> 


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree


  reply	other threads:[~2003-11-20 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 15:54 Iptables not working with RH9 Derek Storvik
2003-11-20 16:17 ` Scott MacKay
2003-11-20 17:17 ` Ramin Dousti
2003-11-20 17:53   ` Scott MacKay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 16:29 Derek Storvik
2003-11-21  1:47 ` Josh Berry
2003-11-24 13:51 Derek Storvik

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=20031120175310.69017.qmail@web13909.mail.yahoo.com \
    --to=scottmackay@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox