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