On Tue, Jun 02, 2015 at 09:06:15PM -0400, Vivien Didelot wrote: > Hi Guenter, > > On Jun 2, 2015, at 10:24 AM, Guenter Roeck li...@roeck-us.net wrote: > On 06/01/2015 06:27 PM, Vivien Didelot wrote: > >> This commit disables SA learning and refreshing for the CPU port. > >> > > > > Hi Vivien, > > > > This patch also seems to be unrelated to the rest of the series. > > > > Can you add an explanation why it is needed ? > > > > With this in place, how does the CPU port SA find its way into the fdb ? > > Do we assume that it will be configured statically ? > > An explanation might be useful. > > Without this patch, I noticed the CPU port was stealing the SA of a PC > behind a switch port. this happened when the port was a bridge member, > as the bridge was relaying broadcast coming from one switch port to the > other switch ports in the same vlan. > Makes me feel really uncomfortable. I think we may be going into the wrong direction. The whole point of offloading bridging is to have the switch handle forwarding, and that includes multicasts and broadcasts. Instead of doing that, it looks like we put more and more workarounds in place.
Maybe the software bridge code needs to understand that it isn't support to forward broadcasts to ports of an offloaded bridge, and we should let the switch chip handle it ? Thanks, Guenter -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
