Lines Matching refs:multicast

180 	- VLAN flooding of multicast/broadcast and unknown unicast packets
301 and other IEEE 01:80:c2:xx:xx:xx link-local multicast packets can pass.
310 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
336 The bridge multicast module will notify port netdevs on every multicast group
338 The hardware implementation should be forwarding all registered multicast
431 including multicast, DHCP, IPv4/6, etc. If necessary, it should program the
432 appropriate filters for VLAN, multicast, unicast etc. The underlying device
434 when IGMP snooping is enabled for IP multicast over these switchdev network
435 devices and unsolicited multicast must be filtered as early as possible in
541 - when IGMP snooping is turned off, multicast traffic must be flooded to all
544   IFF_ALLMULTI or IFF_PROMISC) and continue to learn multicast traffic through
546   then the CPU/management port must also be flooded and multicast filtering
549 - when IGMP snooping is turned on, multicast traffic must selectively flow
551   unknown multicast should be only towards the ports connected to a multicast
552   router (the local device may also act as a multicast router).
554 The switch must adhere to RFC 4541 and flood multicast traffic accordingly
561 A switchdev driver can also refuse to support dynamic toggling of the multicast
563 and creation of a new bridge device(s) with a different multicast snooping