Lines Matching full:bridge

21 *bridge*
22   Every switch port is part of one configurable Ethernet bridge
26   Ethernet bridge.
72 *bridge*
105 *bridge*
117     # create bridge
118     ip link add name br0 type bridge
120     # add ports to bridge
125     # configure the bridge
128     # bring up the bridge
146     # create bridge
147     ip link add name br0 type bridge
149     # add ports to bridge
153     # configure the bridge
156     # bring up the bridge
169   The configuration can only be set up via VLAN tagging and bridge setup.
190     # create bridge
191     ip link add name br0 type bridge
194     ip link set dev br0 type bridge vlan_filtering 1
202     bridge vlan add dev lan1 vid 1 pvid untagged
203     bridge vlan add dev lan2 vid 2 pvid untagged
204     bridge vlan add dev lan3 vid 3 pvid untagged
211     # bring up the bridge devices
215 *bridge*
231     # create bridge
232     ip link add name br0 type bridge
235     ip link set dev br0 type bridge vlan_filtering 1
237     # add ports to bridge
244     bridge vlan add dev lan1 vid 1 pvid untagged
245     bridge vlan add dev lan2 vid 1 pvid untagged
246     bridge vlan add dev lan3 vid 1 pvid untagged
248     # configure the bridge
251     # bring up the bridge
272     # create bridge
273     ip link add name br0 type bridge
276     ip link set dev br0 type bridge vlan_filtering 1
285     bridge vlan add dev lan1 vid 1 pvid untagged
286     bridge vlan add dev lan2 vid 1 pvid untagged
287     bridge vlan add dev wan vid 2 pvid untagged
293     # bring up the bridge devices
300 the software FDB of the bridge in sync with the hardware tables, so the two
301 tables are managed separately (``bridge fdb show`` queries both, and depending
302 on whether the ``self`` or ``master`` flags are being used, a ``bridge fdb
303 add`` or ``bridge fdb del`` command acts upon entries from one or both tables).
305 Up until kernel v4.14, DSA only supported user space management of bridge FDB
306 entries using the bridge bypass operations (which do not update the software
312     bridge fdb add dev swp0 00:01:02:03:04:05 self static
314     bridge fdb add dev swp0 00:01:02:03:04:05 static
316 Due to a bug, the bridge bypass FDB implementation provided by DSA did not
325     bridge fdb add dev swp0 00:01:02:03:04:05 static
327     bridge fdb add dev swp0 00:01:02:03:04:05 local
330     bridge fdb add dev swp0 00:01:02:03:04:05
332 The last command is an incorrect way of adding a static bridge FDB entry to a
333 DSA switch using the bridge bypass operations, and works by mistake. Other
338 adding a bridge FDB entry to the switch: the bridge bypass discussed above, as
340 software bridge too.
344     bridge fdb add dev swp0 00:01:02:03:04:05 master static
346 Since kernel v5.14, DSA has gained stronger integration with the bridge's
347 software FDB, and the support for its bridge bypass FDB implementation (using
354     bridge fdb add dev swp0 00:01:02:03:04:05 master static
357     bridge fdb add dev swp0 00:01:02:03:04:05
359     bridge fdb add dev swp0 00:01:02:03:04:05 static
362 flags when working with bridge FDB entries on DSA switch interfaces.