netdev - Re: Is 802.3ad mode in bonding useful ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1304090462.9358.1617.camel@tardy>
Date:	Fri, 29 Apr 2011 08:21:02 -0700
From:	Rick Jones <rick.jones2@...com>
To:	John Lumby <johnlumby@...mail.com>
Cc:	Neil Horman <nhorman@...driver.com>,
	WeipingPan <panweiping3@...il.com>, netdev@...r.kernel.org
Subject: Re: Is 802.3ad mode in bonding useful ?

> >> What is looped back frames here ?
> > In this case they are frames that get received by the bond, which the bond
> > itself sent.  In modes where more than one slave is active, and in which the
> > switch has no additional knoweldge of the aggregate (e.g. round robin mode), the
> > bond can send a frame on one slave, which the switch may broadcast to all ports,
> 
> 
> Isn't this (broadcasting or repeating on all ports other than incoming) 
> more associated with simple hubs rather than switches?     I would think 
> any switch with layer 2 capability does not do that (does it?)

Perhaps when a frame is sent via the bond to a destination MAC not yet
learned by the switch?  

Until a switch sees a MAC as a src, it does not know to which port the
frame(s) should be forwarded, so it must send the frame out all ports
but the ingress port.

rick jones

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html