Date: Mon, 3 Oct 2005 10:37:52 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Dominic Marks <dom@helenmarks.co.uk> Cc: freebsd-net@FreeBSD.org Subject: Re: Packet loss with ng_one2many Message-ID: <20051003063752.GB45345@cell.sick.ru> In-Reply-To: <4452.195.12.22.194.1126884783.squirrel@www.helenmarks.co.uk> References: <4452.195.12.22.194.1126884783.squirrel@www.helenmarks.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 16, 2005 at 04:33:03PM +0100, Dominic Marks wrote:
D> I'm trying to use two gigabit links together using ng_one2many.
D>
D> I haven't done this before, so here is the environment:
D>
D> FreeBSD 6 system with four gigabit interfaces, two of the four are going
D> to be used a single interface. I've attached em0 and em1 to a gigabit
D> switch and read manual pages / googled for information on how to configure
D> this.
D>
D> I have the following script to set things up:
D>
D> ngctl mkpeer em0: one2many upper one
D> ngctl connect em0: em0:upper lower many0
D> ngctl connect em1: em0:upper lower many1
D> ngctl msg em1: setpromisc 1
D> ngctl msg em1: setautosrc 0
D> ngctl msg em0:upper \
D> setconfig "{ xmitAlg=1 failAlg=1 enabledLinks=[ 1 1 ] }"
D>
D> I get 50% packet loss when using this. It seems to me like only the em0
D> interface is operating properly, although both NICs are connected and work
D> alright without ng_one2many.
D>
D> Any clues as to what I am doing wrong / guides to implementation
D> ng_one2many? Is this email related to my problem?
Is your em1 interface UP?
Have you configured trunk group on the switch?
D> http://lists.freebsd.org/pipermail/freebsd-net/2005-February/006500.html
May be. To make ng_one2many notice link state changes on Ethernet interfaces
you need to set failAlg=2.
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051003063752.GB45345>