From owner-freebsd-stable@FreeBSD.ORG Wed Sep 27 17:26:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F6E716A407 for ; Wed, 27 Sep 2006 17:26:12 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [204.127.225.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92BE843D6E for ; Wed, 27 Sep 2006 17:26:11 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (alnrmhc14) with ESMTP id <20060927172611b1400jbbh6e>; Wed, 27 Sep 2006 17:26:11 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id AFD7D1FA039; Wed, 27 Sep 2006 10:26:10 -0700 (PDT) Date: Wed, 27 Sep 2006 10:26:10 -0700 From: Jeremy Chadwick To: Javier Henderson Message-ID: <20060927172610.GA23562@icarus.home.lan> Mail-Followup-To: Javier Henderson , freebsd-stable@freebsd.org References: <451A1375.5080202@gneto.com> <20060927071538.GF22229@e-Gitt.NET> <451A4189.5020906@samsco.org> <20060927094509.GB75104@hugo10.ka.punkt.de> <451A71B6.6040201@crc.u-strasbg.fr> <20060927132555.GB83422@hugo10.ka.punkt.de> <7.0.1.0.0.20060927095043.17915d48@sentex.net> <20060927155047.GA14563@icarus.home.lan> <6BFCD3E5-13D8-4712-B2F4-722522983010@kjsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6BFCD3E5-13D8-4712-B2F4-722522983010@kjsl.com> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org Subject: Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Sep 2006 17:26:12 -0000 On Wed, Sep 27, 2006 at 12:44:04PM -0400, Javier Henderson wrote: > You could enable port fast and still have spanning tree in place. > > What many reasons do you and others have to shun STP? Rather than ramble off all the things I've experienced with STP, most of them are covered in this caveat document written by none other than Cisco: http://www.cisco.com/warp/public/473/16.html portfast is mentioned, but I'll remind you that not everyone uses Cisco equipment (nor should they). I consider portfast admission that STP wasn't such a great idea after all. My logic is as follows: a properly managed network should never encounter layer 1 loops. STP is most commonly used for "oh crap, I made a mistake" situations. Humans aren't perfect, but if you've engineers who continue to make physical segment loops over and over, you're better off getting different engineers rather than deploying STP and making a mess of network fail-over reliability. Regardless, this is totally off-topic for the list. I'll be more than happy to discuss all of this privately. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |