From owner-freebsd-stable@FreeBSD.ORG Wed Sep 27 16:44:09 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 75D0416A40F for ; Wed, 27 Sep 2006 16:44:09 +0000 (UTC) (envelope-from javier@kjsl.com) Received: from skyhawk.kjsl.com (skyhawk.kjsl.com [69.36.241.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E87D43D7E for ; Wed, 27 Sep 2006 16:44:09 +0000 (GMT) (envelope-from javier@kjsl.com) Received: from [64.102.196.31] (dhcp-64-102-196-31.cisco.com [64.102.196.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: javier) by skyhawk.kjsl.com (Postfix) with ESMTP id 756F8B83B6; Wed, 27 Sep 2006 12:44:08 -0400 (EDT) In-Reply-To: <20060927155047.GA14563@icarus.home.lan> 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> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6BFCD3E5-13D8-4712-B2F4-722522983010@kjsl.com> Content-Transfer-Encoding: 7bit From: Javier Henderson Date: Wed, 27 Sep 2006 12:44:04 -0400 To: Jeremy Chadwick X-Mailer: Apple Mail (2.752.2) 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 16:44:09 -0000 On Sep 27, 2006, at 11:50 AM, Jeremy Chadwick wrote: > On Wed, Sep 27, 2006 at 09:56:22AM -0400, Mike Tancsa wrote: >> If it up / downs the interface, it can be painful depending on your >> setup. In one of the colos I dont have control over, the switch port >> will block for 15 seconds for Spanning Tree when the interface >> transitions like that. Even in cases where this does not happen, a >> 1-2 second network outage can play havoc with some applications. > > Ouch! This is one of many reasons people don't use STP. (I did note > the "colos I don't have control over" part -- frustrating eh?) You could enable port fast and still have spanning tree in place. What many reasons do you and others have to shun STP? -jav