-----Original Message-----
From: Lennert Buytenhek [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 24, 2001 10:11 AM
To: Marc Cozzi
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Bridge] will not filter correctly



On Sat, Dec 22, 2001 at 03:25:56PM -0500, Marc Cozzi wrote:

> Happy holidays,

Same (currently bumming around in Germany, sorry for response delays :)


>  However, none of the following
> iptables commands seem to restrict data flow.
> 
> iptables -I INPUT -s 2.3.4.5 -j DROP

This command should work independently of any extra patches you might need.
If this command does not restrict data flow between the local host and the
2.3.4.5 machine, something is _very_ wrong.  Are you sure you didn't already
have an 'ACCEPT' rule above?


> Do I need to go back and apply any of the patches? It's not
> clear to me what the order of patches are for the 2.4.16
> kernel.

You will want:
- patches to bring the in-kernel bridge code up to date
- a patch for adding a link between the bridge code and netfilter code

The first can be got from http://bridge.sf.net/patchtracker.html.  The
second from http://bridge.sf.net/download.html.  Alternatively, you can use
the prebuilt Red Hat 7.2 kernel.


Thanks,
Does that mean I apply ALL the patches from the
http://bridge.sf.net/patchtracker.html site first, then
apply the bridge-nf-0.0.4-against-2.4.16.diff file from
the http://bridge.sf.net/download.html site. Then build
the new 2.4.16 kernel with all the netfilter, bridge options
selected?

Alternatively,
If I use the stock kernel source that came with RH 7.2, can
I just build the kernel with the netfilter, bridge stuff turned
on then RPM install the kernel-2.4.9-13brnf0.0.4.i686.rpm file?


Thanks again for all the help.
  marc




cheers,
Lennert
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge

Reply via email to