From owner-freebsd-net@FreeBSD.ORG Wed Mar 29 07:35:25 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DE8C16A56A for ; Wed, 29 Mar 2006 07:35:25 +0000 (UTC) (envelope-from eddy+public+spam@noc.everquick.net) Received: from a.mx.ict1.everquick.net (a.mx.ict1.everquick.net [204.10.191.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1EAD43D6D for ; Wed, 29 Mar 2006 07:35:22 +0000 (GMT) (envelope-from eddy+public+spam@noc.everquick.net) Received: from pop.ict1.everquick.net (localhost [127.0.0.1]) by a.mx.ict1.everquick.net (8.12.10/8.12.10) with ESMTP id k2T7ZJXG028429 for ; Wed, 29 Mar 2006 07:35:19 GMT X-Everquick-No-Abuse-1: Report any email abuse to or X-Everquick-No-Abuse-2: call +1 (785) 865-5885. Please be sure to reference X-Everquick-No-Abuse-3: the Message-Id and include GMT timestamps. Received: from localhost (eddy@localhost) by pop.ict1.everquick.net (8.13.3/8.13.3/Submit) with ESMTP id k2T7ZJPf028424 for ; Wed, 29 Mar 2006 07:35:19 GMT X-Authentication-Warning: pop.ict1.everquick.net: eddy owned process doing -bs Date: Wed, 29 Mar 2006 07:35:19 +0000 (GMT) From: "Edward B. DREGER" X-X-Sender: eddy@pop.ict1.everquick.net To: freebsd-net@freebsd.org In-Reply-To: <20060329044558.GC20602@blar.home.comstyle.com> Message-ID: References: <20060328205624.GZ20678@gremlin.foo.is> <20060328215911.GA20602@blar.home.comstyle.com> <20060329002015.GI45591@overlord.e-gerbil.net> <20060329020343.GB20602@blar.home.comstyle.com> <20060329035645.GK45591@overlord.e-gerbil.net> <20060329044558.GC20602@blar.home.comstyle.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: 802.3ad? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 07:35:25 -0000 B> Date: Tue, 28 Mar 2006 23:45:58 -0500 B> From: Brad B> Yes, 2 redundant paths represented by a virtual L2 interface is what he is B> asking for. VRRP is for providing L3 redundancy for the next hop. A completely B> different scenario. I hesitate to speak for others, but I'm pretty confident RAS knows that. ;-) B> > A properly designed system should be seperating out these layers B> > internally, in order to tie all of these features together under a common B> I'm not sure what exactly it is that you're describing above. It almost sounds B> as if you want a flat config with no config information split up by interfaces B> be it physical, virtual L2 or virtual L3. I can't say as I've seen *any* B> OS that can do that *exactly* as you describe. Sounds to me like a request for something analogous to netgraph(4), busdma(9), or scsipi(9). (A local attempt to integrate some custom FIB code in 4.x led me through some rather messy code. IIRC, I found several opportunities for better abstraction and lower cyclomatic code complexity. Perhaps memory fails me, or maybe things have changed.) B> trunking = 801.Q/ISL and nothing else. The IEEE has results from their "802.3 Trunking Study Group" available. If the body that writes the standard uses "802.3" and "trunking" together, I can see why others might do the same. B> link aggregation implies that all links are active. this is FAILOVER. there is B> no hash involved. [ Note: I didn't quite follow your pronoun/antecedent usage. ] There normally _is_ hashing involved with link aggregation. It's not part of the 802.3ad protocol per se, but devices spread traffic across the active links. Straight L2 devices hash on src/dst MAC addr. More intelligent counterparts inspect higher layers when selecting a link. Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: davidc@brics.com -*- jfconmaapaq@intc.net -*- sam@everquick.net Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter.