From owner-freebsd-net Fri Feb 26 11: 4:19 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D2B0414FC6 for ; Fri, 26 Feb 1999 11:04:03 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA13668; Fri, 26 Feb 1999 11:02:46 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdg13651; Fri Feb 26 19:02:35 1999 Date: Fri, 26 Feb 1999 11:02:23 -0800 (PST) From: Julian Elischer To: Luigi Rizzo Cc: Archie Cobbs , venkats@austin.ibm.com, freebsd-net@FreeBSD.ORG Subject: Re: etherchannel support In-Reply-To: <199902261641.RAA25760@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 26 Feb 1999, Luigi Rizzo wrote: > > Luigi Rizzo writes: > > > > > Does freebsd have support for Cisco's etherchannel ? > ... > > > hmm... i see it easy for incoming path, but what about the outgoing ? > > > How do you chose which interface to use for output, what about load > > > balancing, etc ? > > Well, what does Cisco do? > > hey, i asked first! The answer is that we could easily do whatever is required in a small single module.. The reason I can't say more is because I don't actually know the details of etherchannel aggregative routing. > > cheers > luigi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message