Lines Matching refs:multicast
179 - VLAN flooding of multicast/broadcast and unknown unicast packets
300 and other IEEE 01:80:c2:xx:xx:xx link-local multicast packets can pass.
309 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
335 The bridge multicast module will notify port netdevs on every multicast group
337 The hardware implementation should be forwarding all registered multicast
430 including multicast, DHCP, IPv4/6, etc. If necessary, it should program the
431 appropriate filters for VLAN, multicast, unicast etc. The underlying device
433 when IGMP snooping is enabled for IP multicast over these switchdev network
434 devices and unsolicited multicast must be filtered as early as possible in
540 - when IGMP snooping is turned off, multicast traffic must be flooded to all
543 IFF_ALLMULTI or IFF_PROMISC) and continue to learn multicast traffic through
545 then the CPU/management port must also be flooded and multicast filtering
548 - when IGMP snooping is turned on, multicast traffic must selectively flow
550 unknown multicast should be only towards the ports connected to a multicast
551 router (the local device may also act as a multicast router).
553 The switch must adhere to RFC 4541 and flood multicast traffic accordingly
560 A switchdev driver can also refuse to support dynamic toggling of the multicast
562 and creation of a new bridge device(s) with a different multicast snooping