From owner-freebsd-net@FreeBSD.ORG Fri Aug 4 02:01:14 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 9042816A4DA for ; Fri, 4 Aug 2006 02:01:14 +0000 (UTC) (envelope-from lukem@cse.unsw.edu.au) Received: from note.orchestra.cse.unsw.EDU.AU (note.orchestra.cse.unsw.EDU.AU [129.94.242.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB53343D45 for ; Fri, 4 Aug 2006 02:01:13 +0000 (GMT) (envelope-from lukem@cse.unsw.edu.au) Received: From wagner.orchestra.cse.unsw.EDU.AU ([129.94.242.19]) (ident-user root) (cse-authentic-sender lukem) By note With Smtp ; Fri, 4 Aug 2006 12:01:05 +1000 Received: From wagner With LocalMail ; Fri, 4 Aug 2006 12:01:05 +1000 From: lukem.freebsd@cse.unsw.edu.au Sender: lukem@cse.unsw.edu.au To: Antony Mawer Date: Fri, 4 Aug 2006 12:01:05 +1000 (EST) In-Reply-To: <44D18EAF.1010907@mawer.org> Message-ID: References: <44D18EAF.1010907@mawer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: Plans to port OpenBSD trunk(4)? 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: Fri, 04 Aug 2006 02:01:14 -0000 On Thu, 3 Aug 2006, Antony Mawer wrote: > Is there any interest or plans underway to port the trunk(4) feature from > OpenBSD? OpenBSD's trunk(4) appears to be exactly what I'm looking for, but > there doesn't appear to be anything I can find on a port to FreeBSD. > > http://www.openbsd.org/cgi-bin/man.cgi?query=trunk&sektion=4 > > I've been tasked with setting up a system that will have 2x Intel Pro/1000 > network adapters linked to an HP ProCurve 5300XL modular switch. > > I stumbled across ng_fec(4), but it refers explicitly to Cisco Fast > EtherChannel; some information suggests that this is supported by the HP > switch... would using Netgraph with ng_fec achieve the same end result? Has > anyone successfully used it as such? You HP switch will probably support FEC trunking (the ones I have do), so using the ng_fec netgraph module is probably what you want to do. In fact, even if your switch uses something other than the FEC scheduler to distribute incoming packets, ng_fec will still work to distribute outgoing packets. Here is the config I use (on a 5.x system)... #!/bin/sh ngctl mkpeer fec dummy fec ngctl msg fec0: add_iface '"em0"' ngctl msg fec0: add_iface '"em1"' ngctl msg fec0: add_iface '"em2"' ngctl msg fec0: add_iface '"em3"' ifconfig fec0 192.168.1.1 255.255.255.0 #this next line should be implied by the previous, but... ifconfig fec0 up -- Luke