Lines Matching +full:self +full:- +full:working +full:- +full:mode
1 .. SPDX-License-Identifier: GPL-2.0
11 Copyright |copy| 2014-2015 Scott Feldman <[email protected]>
14 The Ethernet switch device driver model (switchdev) is an in-kernel driver
19 an example setup using a data-center-class switch ASIC chip. Other setups
20 with SR-IOV or soft switches, such as OVS, are possible.
25 User-space tools
28 +-------------------------------------------------------------------+
31 +--------------+-------------------------------+
35 +----------------------------------------------+
41 +--+----+----+----+----+----+---+ +-----+-----+
45 +--------------+----------------+ +-----------+
48 +-------------------------------------------------------------------+
50 +--------------+----------------+
52 | +----+ +--------+
55 +--|----|----+----+----+----+---+
60 front-panel ports
67 -------------
76 -------------
83 ------------
95 There is (currently) no higher-level kernel object for the switch beyond the
120 Hard-coding of kernel netdev names within the driver is discouraged; let the
125 useful for dynamically-named ports where the device names its ports based on
134 is the port name or ID, and Z is the sub-port name or ID. For example, sw1p1s0
135 would be sub-port 0 on port 1 on switch 1.
140 dev->netns_local
144 the port netdev from being moved out of the default netns. A netns-aware
153 higher-level switching constructs. The default construct is a standalone
156 L2 networks. VLANs can be applied to sub-divide L2 networks. L2-over-L3
158 tools such as the bridge driver, the bonding/team drivers, and netlink-based
169 ---------------------
177 - Static FDB entries installed on a bridge port
178 - Notification of learned/forgotten src mac/vlans from device
179 - STP state changes on the port
180 - VLAN flooding of multicast/broadcast and unknown unicast packets
189 bridge fdb add dev DEV ADDRESS [vlan VID] [self] static
191 (the "static" keyword is non-optional: if not specified, the entry defaults to
194 The "self" keyword (optional because it is implicit) has the role of
244 00:02:00:00:02:00 dev sw1p1 self
247 00:02:00:00:03:00 dev sw1p2 self
248 33:33:00:00:00:01 dev eth0 self permanent
249 01:00:5e:00:00:01 dev eth0 self permanent
250 33:33:ff:00:00:00 dev eth0 self permanent
251 01:80:c2:00:00:0e dev eth0 self permanent
252 33:33:00:00:00:01 dev br0 self permanent
253 01:00:5e:00:00:01 dev br0 self permanent
254 33:33:ff:12:35:01 dev br0 self permanent
262 bridge link set dev DEV learning on self
263 bridge link set dev DEV learning_sync on self
286 notification will reset the FDB entry's last-used time to now. The driver
288 second. (The last-used time is visible using the bridge -s fdb option).
293 Internally or with a third-party STP protocol implementation (e.g. mstpd), the
301 and other IEEE 01:80:c2:xx:xx:xx link-local multicast packets can pass.
319 forwarded by setting the skb->offload_fwd_mark bit. The bridge driver will mark
342 ------------------
414 -------------------------------
419 Configuration-less state
427 use per-port VLAN identifiers unless a better mechanism is available
438 When configuring VLANs on top of the network device, all VLANs must be working,
440 of a VLAN-aware bridge doing ingress VID checking). See below for details.
443 promiscuous mode should allow the reception of all VLAN tags (including those
450 not disrupt any functionality of non-bridged network devices and they
457 The Linux bridge allows the configuration of a VLAN filtering mode (statically,
461 - with VLAN filtering turned off: the bridge is strictly VLAN unaware and its
462 data path will process all Ethernet frames as if they are VLAN-untagged.
468 - with VLAN filtering turned on: the bridge is VLAN-aware and frames ingressing
477 - with VLAN filtering turned off, the bridge will process all ingress traffic
487 untagged packets. This internal VID spans all ports of the VLAN-unaware
494 - with VLAN filtering turned on, these VLAN devices can be created as long as
499 Non-bridged network ports of the same switch fabric must not be disturbed in any
503 'rx-vlan-filter: on [fixed]' in the ethtool features.
514 hardware and driver may still configure itself in a VLAN-aware mode provided
519 VLAN-untagged packets, as well as packets tagged with 802.1Q headers, as
529 priority-tagged packets must be accepted and forwarded according to the
541 - when IGMP snooping is turned off, multicast traffic must be flooded to all
549 - when IGMP snooping is turned on, multicast traffic must selectively flow