Lines Matching full:bridge
11 operation of bridges in computer networks. A bridge, in the context of this
14 model. The purpose of a bridge is to filter and forward frames between
17 Bridge kAPI
20 Here are some core structures of bridge code. Note that the kAPI is *unstable*,
23 .. kernel-doc:: net/bridge/br_private.h
26 Bridge uAPI
29 Modern Linux bridge uAPI is accessed via Netlink interface. You can find
30 below files where the bridge and bridge port netlink attributes are defined.
32 Bridge netlink attributes
36 :doc: Bridge enum definition
38 Bridge port netlink attributes
42 :doc: Bridge port enum definition
44 Bridge sysfs
53 The STP (Spanning Tree Protocol) implementation in the Linux bridge driver
56 bridge context, STP is crucial for network stability and availability.
70 Bridge Ports and STP States
73 In the context of STP, bridge ports can be in one of the following states:
75 BPDUs (Bridge Protocol Data Units) from other devices to determine the
86 Root Bridge and Convergence
89 In the context of networking and Ethernet bridging in Linux, the root bridge
93 Here's how the STP works and root bridge is chosen:
94 1. Bridge Priority: Each bridge running a spanning tree protocol, has a
95 configurable Bridge Priority value. The lower the value, the higher the
96 priority. By default, the Bridge Priority is set to a standard value
98 2. Bridge ID: The Bridge ID is composed of two components: Bridge Priority
99 and the MAC address of the bridge. It uniquely identifies each bridge
100 in the network. The Bridge ID is used to compare the priorities of
102 3. Bridge Election: When the network starts, all bridges initially assume
103 that they are the root bridge. They start advertising Bridge Protocol
104 Data Units (BPDU) to their neighbors, containing their Bridge ID and
106 4. BPDU Comparison: Bridges exchange BPDUs to determine the root bridge.
107 Each bridge examines the received BPDUs, including the Bridge Priority
108 and Bridge ID, to determine if it should adjust its own priorities.
109 The bridge with the lowest Bridge ID will become the root bridge.
110 5. Root Bridge Announcement: Once the root bridge is determined, it sends
111 BPDUs with information about the root bridge to all other bridges in the
113 shortest path to the root bridge and, in doing so, create a loop-free
115 6. Forwarding Ports: After the root bridge is selected and the spanning tree
116 topology is established, each bridge determines which of its ports should
118 the blocking state (used to prevent loops). The root bridge's ports are
121 7. Root Ports: After the root bridge is selected and the spanning tree
122 topology is established, each non-root bridge processes incoming
124 root bridge based on the information in the received BPDUs. This port is
128 bridge will forward traffic towards the designated segment. Designated ports
130 bridge that are not designated for specific segments are placed in the
137 Proper configuration of STP parameters, such as the bridge priority, can
138 influence network performance, path selection and which bridge becomes the
139 Root Bridge.
144 The user space STP helper *bridge-stp* is a program to control whether to use
145 user mode spanning tree. The ``/sbin/bridge-stp <bridge> <start|stop>`` is
146 called by the kernel when STP is enabled/disabled on a bridge
147 (via ``brctl stp <bridge> <on|off>`` or ``ip link set <bridge> type bridge
171 bridge supports both the IEEE 802.1Q and `802.1AD
176 on a bridge is disabled by default. After enabling VLAN filtering on a bridge,
183 The Linux bridge driver has multicast support allowing it to process Internet
185 messages, and to efficiently forward multicast data packets. The bridge
203 When created, the Linux bridge devices have multicast snooping enabled by
210 The Linux bridge supports IGMPv3/MLDv2 EHT (Explicit Host Tracking), which
211 was added by `474ddb37fa3a ("net: bridge: multicast: add EHT allow/block handling")
230 The Linux bridge also supports `per-VLAN multicast snooping
239 Linux Bridge Switchdev is a feature in the Linux kernel that extends the
240 capabilities of the traditional Linux bridge to work more efficiently with
241 hardware switches that support switchdev. With Linux Bridge Switchdev, certain
247 To use Linux Bridge Switchdev, you need hardware switches that support the
257 The bridge netfilter module is a legacy feature that allows to filter bridged
264 The br_netfilter module intercepts packets entering the bridge, performs
267 the ip and ipv6 netfilter hooks from the bridge layer, i.e. ip(6)tables
277 see traffic that is forwarded by a bridge either, but that's very much how it
282 netfilter hooks from the bridge so users had access to the more feature-rich
287 ip(6)tables to filter packets forwarded by the bridge, or NAT bridged
293 The Linux bridge also supports `IEEE 802.11 Proxy ARP
307 What does a bridge do?
310 A bridge transparently forwards traffic between multiple network interfaces.
311 In plain English this means that a bridge connects two or more physical
317 Yes. The bridge sees all frames, but it *uses* only L2 headers/information.
325 Nikolay Aleksandrov <[email protected]>. Bridge bugs and enhancements
327 bridge@lists.linux.dev.
335 https://wiki.linuxfoundation.org/networking/bridge