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: Wed, 20 Jun 2007 04:07:17 +0000	[thread overview]
Message-ID: <20070620040717.GT24808@samad.com.au> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A210B8D8@mail733.InfraSupportEtc.com>


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

On Tue, Jun 19, 2007 at 06:35:46PM -0500, Greg Scott wrote:
> > out of curiosity why would you want to bridge at the firewall.  is
> this meant to be a drop in-line firewall appliance
> 
> Long story but yes, it is essentially a drop in-line system.  It's a
> mess.  
> 
> So will that Internet router really see 4 "switches" - a switch, a
> bridge, and 2 switches - between it and the internal servers?  I don't
> remember all my LAN rules but that feels way too deep to me.  
I think that was the old 5-4-3 or was it 4-3-2 ... I think that was more in the 
days of repeater and broadcast hubs.  Modern day switch I believe allow for a 
lot more.

> 
> - Greg
> 

[-- 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

  parent reply	other threads:[~2007-06-20  4:07 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
2007-06-19 23:35 ` Greg Scott
2007-06-20  3:31 ` Greg Scott
2007-06-20  4:07 ` Alex Samad [this message]
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=20070620040717.GT24808@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.