Date: Thu, 11 Dec 2014 18:29:48 +0100 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com> To: Ryan Stone <rysto32@gmail.com>, "David P. Discher" <dpd@dpdtech.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: EM(4) - Link flap when bridged and adding members (em bridge flap) Message-ID: <5489D48C.10306@citrix.com> In-Reply-To: <CAFMmRNyVFtaZW0cu30f8_s8ABZJpnH%2ByPKSa67s%2BngNueWHhfw@mail.gmail.com> References: <BF885CAD-6A3A-4B79-B3E3-52BDF2C1497D@dpdtech.com> <CAFMmRNyVFtaZW0cu30f8_s8ABZJpnH%2ByPKSa67s%2BngNueWHhfw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
El 10/12/14 a les 19.25, Ryan Stone ha escrit: >>From a quick look at the code, whenever an interface is added to a > bridge, if that interface does not support a feature currently enabled > on the bridge then it has to disable that feature on all member > interfaces of that bridge. That would re-init the em interface, which > would cause a link flap. This is something specific to the em driver implementation I guess, because I've tried it with other drivers (bge and bce) and the connection is not dropped when the normalization of options happens. Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5489D48C.10306>