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