From: Bart De Schuymer <bdschuym@pandora.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] FTP Connection Tracking in a Bridge
Date: Fri, 22 Aug 2003 19:12:18 +0000 [thread overview]
Message-ID: <marc-lartc-106157953709496@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106136953432545@msgid-missing>
On Wednesday 20 August 2003 15:14, S Mohan wrote:
> Doh. So dumb of me. I have documented this but this skipped my attention.
> Thanks Staf. AFAIK, in a bridged mode, only the FORWARD table is processed.
> The packet does not traverse any other traditional netfilter table. This is
> the reason for the existence of ebtables. ebtables provides all these
> tables within its realm.
Just for the record, as I'm the maintainer of ebtables and the bridge-nf code
I can safely say that these statements above are not correct.
ebtables is there to filter on non-IP stuff, more specifically the Ethernet
header. In 2.6 or in a patched (with the bridge-nf patch) 2.4 kernel, the
PREROUTING/FORWARD/POSTROUTING iptables chains see bridged traffic. This is
therefore different than the behaviour with the old patch vs 2.2 for
ipchains.
Anyone interested can go to ebtables.sourceforge.net, the working of iptables
on a bridge is explained there in detail.
Please update your documentation.
cheers,
Bart
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-08-22 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 8:48 [LARTC] FTP Connection Tracking in a Bridge Wayne
2003-08-20 9:02 ` Eric Leblond
2003-08-20 9:56 ` S Mohan
2003-08-20 10:06 ` Wayne
2003-08-20 12:24 ` Stef Coene
2003-08-20 12:26 ` Stef Coene
2003-08-20 12:38 ` Eric Leblond
2003-08-20 12:39 ` Wayne
2003-08-20 13:26 ` S Mohan
2003-08-20 15:17 ` Stef Coene
2003-08-21 7:28 ` Wayne
2003-08-22 19:12 ` Bart De Schuymer [this message]
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=marc-lartc-106157953709496@msgid-missing \
--to=bdschuym@pandora.be \
--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.