Lines Matching full:bridge

21 *bridge*
22   Every switch port is part of one configurable Ethernet bridge
26   Ethernet bridge.
75 *bridge*
108 *bridge*
120     # create bridge
121     ip link add name br0 type bridge
123     # add ports to bridge
128     # configure the bridge
131     # bring up the bridge
149     # create bridge
150     ip link add name br0 type bridge
152     # add ports to bridge
156     # configure the bridge
159     # bring up the bridge
172   The configuration can only be set up via VLAN tagging and bridge setup.
193     # create bridge
194     ip link add name br0 type bridge
197     ip link set dev br0 type bridge vlan_filtering 1
205     bridge vlan add dev lan1 vid 1 pvid untagged
206     bridge vlan add dev lan2 vid 2 pvid untagged
207     bridge vlan add dev lan3 vid 3 pvid untagged
214     # bring up the bridge devices
218 *bridge*
234     # create bridge
235     ip link add name br0 type bridge
238     ip link set dev br0 type bridge vlan_filtering 1
240     # add ports to bridge
247     bridge vlan add dev lan1 vid 1 pvid untagged
248     bridge vlan add dev lan2 vid 1 pvid untagged
249     bridge vlan add dev lan3 vid 1 pvid untagged
251     # configure the bridge
254     # bring up the bridge
275     # create bridge
276     ip link add name br0 type bridge
279     ip link set dev br0 type bridge vlan_filtering 1
288     bridge vlan add dev lan1 vid 1 pvid untagged
289     bridge vlan add dev lan2 vid 1 pvid untagged
290     bridge vlan add dev wan vid 2 pvid untagged
296     # bring up the bridge devices
303 the software FDB of the bridge in sync with the hardware tables, so the two
304 tables are managed separately (``bridge fdb show`` queries both, and depending
305 on whether the ``self`` or ``master`` flags are being used, a ``bridge fdb
306 add`` or ``bridge fdb del`` command acts upon entries from one or both tables).
308 Up until kernel v4.14, DSA only supported user space management of bridge FDB
309 entries using the bridge bypass operations (which do not update the software
315     bridge fdb add dev swp0 00:01:02:03:04:05 self static
317     bridge fdb add dev swp0 00:01:02:03:04:05 static
319 Due to a bug, the bridge bypass FDB implementation provided by DSA did not
328     bridge fdb add dev swp0 00:01:02:03:04:05 static
330     bridge fdb add dev swp0 00:01:02:03:04:05 local
333     bridge fdb add dev swp0 00:01:02:03:04:05
335 The last command is an incorrect way of adding a static bridge FDB entry to a
336 DSA switch using the bridge bypass operations, and works by mistake. Other
341 adding a bridge FDB entry to the switch: the bridge bypass discussed above, as
343 software bridge too.
347     bridge fdb add dev swp0 00:01:02:03:04:05 master static
349 Since kernel v5.14, DSA has gained stronger integration with the bridge's
350 software FDB, and the support for its bridge bypass FDB implementation (using
357     bridge fdb add dev swp0 00:01:02:03:04:05 master static
360     bridge fdb add dev swp0 00:01:02:03:04:05
362     bridge fdb add dev swp0 00:01:02:03:04:05 static
365 flags when working with bridge FDB entries on DSA switch interfaces.