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-
Thanks ryan - this did appear work around the issue.
-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz
On Dec 10, 2014, at 10:25 AM, Ryan Stone wrote:
> From a quick look at the code, whenever an interface is added to a
> bridge, if that interface does not support a f
>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.
I’m seeing this in -head as well as 10-stable (r274577) on two different sets
of hardware.
When an em interface is a member of a bridge, (if_bridge(4)), the link flaps.
This is reported on the console as well as can be seen with loss of
connectivity. This seems to be easily replicated.
i
