From: Joel Newkirk <netfilter@newkirk.us>
To: hare ram <hareram@sol.net.in>, netfilter@lists.samba.org
Subject: Re: Bridge with iptables
Date: Thu, 3 Apr 2003 10:24:03 -0500 [thread overview]
Message-ID: <200304031024.03315.netfilter@newkirk.us> (raw)
In-Reply-To: <071f01c2f9ef$86489980$13fcc5cb@Housecall>
On Thursday 03 April 2003 09:44 am, hare ram wrote:
> Hi
>
> iam trying to setup a bridge with iptable
> i have setup the transparent bridge,
>
> and iam try to mark the http packets for QOS
> iam not able to see the packets
>
> i was going through the Lartc.org
> some where i read at this stage ( kernel 2.4.18-27 Redhat iam using)
> bridge will not support iptables.
> it will support only on kernel 2.5, is this true
>
> if false, where can i get the right documentation which help me to
> setup bridge with packet filtering
It is possible to patch the 2.4.x kernel. Then you select "802.1d
Ethernet Bridging" and "netfilter (firewalling) support" when
configuring the kernel.
You need to download the br-nf patch and patch the kernel source with it.
It is available at:
http://bridge.sourceforge.net/
The file you are looking for is:
http://bridge.sourceforge.net/devel/bridge-nf/bridge-nf-0.0.7-against-2.4.19.diff
The documentation I successfully followed to build a transparent
filtering bridge with a 2.4.x kernel is:
http://www.think-future.de/DOCUMENTATION/Ethernet-Bridge-netfilter-HOWTO/
I browsed other documents, and found another well-written one that
covered the initial steps well, but when I tried to bring the bridge
interface up using those instructions it failed. The above link's
approach worked painlessly, and it took about 25 minutes from download
to a working filtering bridge, which now sits between an ISP and the
internet.
j
next prev parent reply other threads:[~2003-04-03 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 14:44 Bridge with iptables hare ram
2003-04-03 15:24 ` Joel Newkirk [this message]
2003-04-04 15:11 ` hare ram
2003-04-03 15:56 ` pieter claassen
2003-04-03 16:02 ` Drew Einhorn
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=200304031024.03315.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=hareram@sol.net.in \
--cc=netfilter@lists.samba.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.