All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux bridging and cascaded switches
Date: Tue, 19 Jun 2007 23:03:25 +0000	[thread overview]
Message-ID: <20070619230325.GR24808@samad.com.au> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A210B8D8@mail733.InfraSupportEtc.com>


[-- Attachment #1.1: Type: text/plain, Size: 1786 bytes --]

On Tue, Jun 19, 2007 at 05:54:46PM -0500, Greg Scott wrote:
> Hi -
>  
> Still plugging away at my Linux bridge/firewall and thinking through the
> consequences.  In a normal firewall situation, the Internet is on one
> side, the internal LAN on the other. Duh!  But now, with a Linux bridge
> in the middle, the whole thing becomes one big messy LAN.  So we have a
> scenario that looks like this:
> 
> Internal---User---Core-----Firewall---Internet---Internet router
> Servers   switch  switch  (Bridged)    switch   (and default GW for
>                                                  internal servers)
> 
out of curiosity why would you want to bridge at the firewall.  is this meant 
to be a drop in-line firewall appliance



> The scenario is a little more complex than I drew above because the
> internal side has more than one LAN segment participating in the bridge.
> I'm working on a way to simulate all this here - before going into
> production - but I have a big question;
> 
> That firewall/bridge is no longer a router - it's a bridge.  Well, a
> bridge that also does a bunch of stateful IP layer 3 filtering.  So now,
> it will participate in a spanning tree setup with all those switches, on
> both sides of it - right?  I'm guessing I want to turn off STP in this
> case.  Am I on the right track?

if there is only 1 way to connect from the corporate (private LAN) to the 
public (internet) then I don't think you will need STP - it was meant to stop 
loops in ethernet segments.

If you have multiple paths you might still need it


> 
> Thanks
> 
> - Greg Scott
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-06-19 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 22:54 [LARTC] Linux bridging and cascaded switches Greg Scott
2007-06-19 23:03 ` Alex Samad [this message]
2007-06-19 23:35 ` Greg Scott
2007-06-20  3:31 ` Greg Scott
2007-06-20  4:07 ` Alex Samad
2007-06-20 20:58 ` John Default
2007-06-21  1:34 ` Grant Taylor
2007-06-21  1:41 ` Grant Taylor
2007-06-21  1:45 ` Grant Taylor

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=20070619230325.GR24808@samad.com.au \
    --to=alex@samad.com.au \
    --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.