Lines Matching refs:bridge

144 together to form a LAG.  Two or more ports (or LAGs) can be bridged to bridge
147 tools such as the bridge driver, the bonding/team drivers, and netlink-based
152 bond will see it's upper master change.  If that bond is moved into a bridge,
161 to the switchdev device by mirroring bridge FDB entries down to the device.  An
166 	- Static FDB entries installed on a bridge port
175 to support static FDB entries installed to the device.  Static bridge FDB
176 entries are installed, for example, using iproute2 bridge cmd:
178 	bridge fdb add ADDR dev DEV [vlan VID] [self]
187 Note: by default, the bridge does not filter on VLAN and only bridges untagged
190 	echo 1 >/sys/class/net/<bridge>/bridge/vlan_filtering
197 in turn, will notify the bridge driver using the switchdev notifier call:
203 SWITCHDEV_FDB_ADD, the bridge driver will install the FDB entry into the
204 bridge's FDB and mark the entry as NTF_EXT_LEARNED.  The iproute2 bridge
207 	$ bridge fdb
222 Learning on the port should be disabled on the bridge using the bridge command:
224 	bridge link set dev DEV learning off
228 	bridge link set dev DEV learning on self
229 	bridge link set dev DEV learning_sync on self
232 the bridge's FDB.  It's possible, but not optimal, to enable learning on the
233 device port and on the bridge port, and disable learning_sync.
243 The bridge will skip ageing FDB entries marked with NTF_EXT_LEARNED and it is
246 driver which in turn will notify the bridge with SWITCHDEV_FDB_DEL.  If the
249 notified to the bridge using SWITCHDEV_FDB_DEL.  See rocker driver for
256 second.  (The last-used time is visible using the bridge -s fdb option).
262 bridge driver maintains the STP state for ports, and will notify the switch
282 be sent to the port netdev for processing by the bridge driver.  The
283 bridge should not reflood the packet to the same ports the device flooded,
297 packets up to the bridge driver for flooding.  This is not ideal as the number