From: John Default <default@advaita.sytes.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux bridging and cascaded switches
Date: Wed, 20 Jun 2007 20:58:53 +0000 [thread overview]
Message-ID: <4679950D.8080102@advaita.sytes.net> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A210B8D8@mail733.InfraSupportEtc.com>
Hi
Greg Scott wrote:
> More fundamentally, can I cascade these switches and my bridge/firewall
> this deep? How do the Internet router and internal servers find each
> others' MAC addresses when they are 4 "hops" (OSI layer 2 hops)
> separated? Or am I making this too complicated?
>
>
i was taught that you should have no more than 4 switches between any
two LAN nodes, so this should work. STP should be ok, but not needed
until you have some redundant links between bridge/fw and core switches
(if you have more core switches, you would probably like to use more
links for redundancy).
[you would probably want the core switch to become STP root then.. ]
when switch doesn't know destination it works like hub, so at the
beginning your network will be flooded with frames and this way all
switches will learn mac addresses no matter how many hops. (frame will
be broadcasted to all corners of LAN).
servers and router will search for each other's MAC using ARP
broadcasts, which will get to every node in LAN (if you don't filter
them out : ) ). Therefore they will certainly find each other.
(( 4 switches add constant delay to your traffic that i think you would
like to avoid. if you could make internet router a firewall (you
probably can't : ) ), that would remove 2 layers of bridging, would be
more simple and allow more control.
servers--distribution_switch--core_switch--router/firewall
|
internet switch
))
>> Internal---User---Core-----Firewall---Internet---Internet router
>> Servers switch switch (Bridged) switch (and default GW for
>> internal servers)
>>
>
> Thanks
>
> - Greg
>
___________________________________
S pozdravom / Best regards
John Default
__________________________________
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-20 20:58 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
2007-06-20 20:58 ` John Default [this message]
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=4679950D.8080102@advaita.sytes.net \
--to=default@advaita.sytes.net \
--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.