From: "David S. Miller" <davem@redhat.com>
To: randy.dunlap@verizon.net
Cc: linux-kernel@vger.kernel.org, ahu@ds9a.nl
Subject: Re: Silly advise in bridge Configure help
Date: Thu, 07 Nov 2002 01:15:26 -0800 (PST) [thread overview]
Message-ID: <20021107.011526.120464470.davem@redhat.com> (raw)
In-Reply-To: <3DC9EA2A.142559AA@verizon.net>
From: "Randy.Dunlap" <randy.dunlap@verizon.net>
Date: Wed, 06 Nov 2002 20:20:58 -0800
Sounds good, so here's the patch to 2.5.46 Kconfig to do that
if you want it.
I had a similar patch in my queue from Lennert Buytenhek (written by
Bart De Schuyer) which I'm about to send to Linus.
[BRIDGE] update help docs
--- linux-2.5.45/net/Kconfig Thu Oct 31 01:41:43 2002
+++ linux-2.5.45-bezig/net/Kconfig Sat Nov 2 12:25:21 2002
@@ -382,10 +382,10 @@
for location. Please read the Bridge mini-HOWTO for more
information.
- Note that if your box acts as a bridge, it probably contains several
- Ethernet devices, but the kernel is not able to recognize more than
- one at boot time without help; for details read the Ethernet-HOWTO,
- available from in <http://www.linuxdoc.org/docs.html#howto>.
+ If you enable iptables support along with the bridge support then you
+ turn your bridge into a bridging firewall.
+ iptables will then see the IP packets being bridged, so you need to
+ take this into account when setting up your firewall rules.
If you want to compile this code as a module ( = code which can be
inserted in and removed from the running kernel whenever you want),
next prev parent reply other threads:[~2002-11-07 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 4:20 Randy.Dunlap
2002-11-07 9:15 ` David S. Miller [this message]
2002-11-07 9:18 ` bert hubert
2002-11-07 9:49 ` David S. Miller
2002-11-07 10:39 ` bert hubert
2002-11-07 10:41 ` bert hubert
2002-11-07 10:52 ` David S. Miller
2002-11-07 11:16 ` bert hubert
2002-11-07 13:02 ` IPSEC FIRST LIGHT! (by non-kernel developer :-)) bert hubert
2002-11-07 13:14 ` James Morris
2002-11-07 13:21 ` David S. Miller
2002-11-07 14:12 ` bert hubert
2002-11-07 15:18 ` David S. Miller
2002-11-07 15:33 ` bert hubert
2002-11-07 17:49 ` kuznet
2002-11-07 18:41 ` bert hubert
2002-11-07 19:05 ` kuznet
2002-11-08 1:59 ` [LARTC] " Mike Diehl
2002-11-08 9:41 ` [documentation] " bert hubert
2002-11-08 9:52 ` David S. Miller
2002-11-08 11:15 ` bert hubert
2002-11-08 11:27 ` bert hubert
2002-11-08 12:25 ` bert hubert
2002-11-08 13:31 ` kuznet
2002-11-08 13:44 ` bert hubert
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 13:35 Silly advise in bridge Configure help bert hubert
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=20021107.011526.120464470.davem@redhat.com \
--to=davem@redhat.com \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@verizon.net \
/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
Powered by JetHome