Lines Matching full:bridge

154 together to form a LAG.  Two or more ports (or LAGs) can be bridged to bridge
157 tools such as the bridge driver, the bonding/team drivers, and netlink-based
162 bond will see it's upper master change.  If that bond is moved into a bridge,
171 to the switchdev device by mirroring bridge FDB entries down to the device.  An
176 	- Static FDB entries installed on a bridge port
185 to support static FDB entries installed to the device.  Static bridge FDB
186 entries are installed, for example, using iproute2 bridge cmd::
188 	bridge fdb add ADDR dev DEV [vlan VID] [self]
197 Note: by default, the bridge does not filter on VLAN and only bridges untagged
200 	echo 1 >/sys/class/net/<bridge>/bridge/vlan_filtering
207 in turn, will notify the bridge driver using the switchdev notifier call::
213 SWITCHDEV_FDB_ADD, the bridge driver will install the FDB entry into the
214 bridge's FDB and mark the entry as NTF_EXT_LEARNED.  The iproute2 bridge
217 	$ bridge fdb
232 Learning on the port should be disabled on the bridge using the bridge command::
234 	bridge link set dev DEV learning off
238 	bridge link set dev DEV learning on self
239 	bridge link set dev DEV learning_sync on self
242 the bridge's FDB.  It's possible, but not optimal, to enable learning on the
243 device port and on the bridge port, and disable learning_sync.
251 The bridge will skip ageing FDB entries marked with NTF_EXT_LEARNED and it is
254 driver which in turn will notify the bridge with SWITCHDEV_FDB_DEL.  If the
257 notified to the bridge using SWITCHDEV_FDB_DEL.  See rocker driver for
264 second.  (The last-used time is visible using the bridge -s fdb option).
270 bridge driver maintains the STP state for ports, and will notify the switch
290 be sent to the port netdev for processing by the bridge driver.  The
291 bridge should not reflood the packet to the same ports the device flooded,
295 forwarded by setting the skb->offload_fwd_mark bit. The bridge driver will mark
296 the skb using the ingress bridge port's mark and prevent it from being forwarded
297 through any bridge port with the same mark.
300 packets up to the bridge driver for flooding.  This is not ideal as the number
310 In order to support IGMP snooping, the port netdevs should trap to the bridge
312 The bridge multicast module will notify port netdevs on every multicast group