From owner-freebsd-net Mon Oct 28 15: 0:36 2002 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 A383737B401 for ; Mon, 28 Oct 2002 15:00:34 -0800 (PST) Received: from InterJet.elischer.org (12-232-206-8.client.attbi.com [12.232.206.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CCEC43E6E for ; Mon, 28 Oct 2002 15:00:34 -0800 (PST) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA25785; Mon, 28 Oct 2002 14:52:01 -0800 (PST) Date: Mon, 28 Oct 2002 14:52:00 -0800 (PST) From: Julian Elischer To: Don Bowman Cc: Sean Chittenden , "Carlos A. Carnero Delgado" , Kevin Stevens , freebsd-net@freebsd.org Subject: RE: Annoying ARP warning messages. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 28 Oct 2002, Don Bowman wrote: > > From: Julian Elischer [mailto:julian@elischer.org] > > > Is there support for 802.3ad in FreeBSD? This would be the best > > > way to gang interfaces together in a standard fashion. It involves > > > LACP (Link Aggregation Control Protocol), which prevents loops > > > @ L2 (I think its an extension of STP). Packet reordering is also > > > solved (the simple round robin scheme achieves rather poor > > performance > > > due to this problem). > > > > > > > This could be (relatively) easy in netgraph.. it was designed for that > > sort of thing. > > > > I assume you mean with a user-mode daemon, sort of a LACPD, like > in the linux model? (http://www.st.rim.or.jp/~yumo/), and then > a version of one2many that did the src^dst hash to prevent re-ordering? > Or would you implement the control protocol inside netgraph as well? you'd put as much in the netgraph node as possible. A daemon might do some ocnfiguration etc. but you don't want it near the data. Examples of link-level protocols in netgraph modules include ppp (multilink ppp), frame relay, 802.1x, (or is that 11x) bluetooth, the cisco bonding (ng_nge from Bill Paul, though it doesn't really use netgraph properly) and the netgraph atm stack. > > On a side note, is there anything netgraph can't solve :) not good at level3 protocols as far as I can see. > > --don (don@sandvine.com www.sandvine.com) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message