Date: Sat, 17 Apr 2004 13:29:07 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Lowell Gilbert <freebsd-current-local@be-well.no-ip.com> Cc: current@freebsd.org Subject: Re: RFC: ported NetBSD if_bridge Message-ID: <Pine.NEB.3.96L.1040417132536.8431D-100000@fledge.watson.org> In-Reply-To: <Pine.NEB.3.96L.1040417132238.8431C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Apr 2004, Robert Watson wrote: > On 17 Apr 2004, Lowell Gilbert wrote: > > > They're referring to IEEE 802.1d. This is an important feature for > > building large bridged networks. > > And it's an important part of many ethernet-layer redundancy solutions, > since it allows fail-over when one bridging element or graph edge goes > offline. It's something we really missed in some research work I was > working on to build link layer filters, since it was an easy way to > provide basic fail-over in the presence of ethernet link failures (and > they happen a lot!) Just as a followup for those not familiar with spanning tree in the context of ethernet, here's a URL in one of Cisco's product manuals: http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/rel_5_2/config/spantree.htm It talks a bit about how the spanning tree algorithm applies to ethernet, and applications of spanning tree. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040417132536.8431D-100000>