| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | # |
| 3 | # 802.1d Ethernet Bridging |
| 4 | # |
| 5 | |
| 6 | config BRIDGE |
| 7 | tristate "802.1d Ethernet Bridging" |
| 8 | select LLC |
| 9 | select STP |
| 10 | help |
| 11 | If you say Y here, then your Linux box will be able to act as an |
| 12 | Ethernet bridge, which means that the different Ethernet segments it |
| 13 | is connected to will appear as one Ethernet to the participants. |
| 14 | Several such bridges can work together to create even larger |
| 15 | networks of Ethernets using the IEEE 802.1 spanning tree algorithm. |
| 16 | As this is a standard, Linux bridges will cooperate properly with |
| 17 | other third party bridge products. |
| 18 | |
| 19 | In order to use the Ethernet bridge, you'll need the bridge |
| 20 | configuration tools; see <file:Documentation/networking/bridge.rst> |
| 21 | for location. Please read the Bridge mini-HOWTO for more |
| 22 | information. |
| 23 | |
| 24 | If you enable iptables support along with the bridge support then you |
| 25 | turn your bridge into a bridging IP firewall. |
| 26 | iptables will then see the IP packets being bridged, so you need to |
| 27 | take this into account when setting up your firewall rules. |
| 28 | Enabling arptables support when bridging will let arptables see |
| 29 | bridged ARP traffic in the arptables FORWARD chain. |
| 30 | |
| 31 | To compile this code as a module, choose M here: the module |
| 32 | will be called bridge. |
| 33 | |
| 34 | If unsure, say N. |
| 35 | |
| 36 | config BRIDGE_IGMP_SNOOPING |
| 37 | bool "IGMP/MLD snooping" |
| 38 | depends on BRIDGE |
| 39 | depends on INET |
| 40 | default y |
| 41 | help |
| 42 | If you say Y here, then the Ethernet bridge will be able selectively |
| 43 | forward multicast traffic based on IGMP/MLD traffic received from |
| 44 | each port. |
| 45 | |
| 46 | Say N to exclude this support and reduce the binary size. |
| 47 | |
| 48 | If unsure, say Y. |
| 49 | |
| 50 | config BRIDGE_VLAN_FILTERING |
| 51 | bool "VLAN filtering" |
| 52 | depends on BRIDGE |
| 53 | depends on VLAN_8021Q |
| 54 | default n |
| 55 | help |
| 56 | If you say Y here, then the Ethernet bridge will be able selectively |
| 57 | receive and forward traffic based on VLAN information in the packet |
| 58 | any VLAN information configured on the bridge port or bridge device. |
| 59 | |
| 60 | Say N to exclude this support and reduce the binary size. |
| 61 | |
| 62 | If unsure, say Y. |
| 63 | |
| 64 | config BRIDGE_MRP |
| 65 | bool "MRP protocol" |
| 66 | depends on BRIDGE |
| 67 | default n |
| 68 | help |
| 69 | If you say Y here, then the Ethernet bridge will be able to run MRP |
| 70 | protocol to detect loops |
| 71 | |
| 72 | Say N to exclude this support and reduce the binary size. |
| 73 | |
| 74 | If unsure, say N. |
| 75 | |
| 76 | config BRIDGE_CFM |
| 77 | bool "CFM protocol" |
| 78 | depends on BRIDGE |
| 79 | help |
| 80 | If you say Y here, then the Ethernet bridge will be able to run CFM |
| 81 | protocol according to 802.1Q section 12.14 |
| 82 | |
| 83 | Say N to exclude this support and reduce the binary size. |
| 84 | |
| 85 | If unsure, say N. |