Orange Pi5 kernel

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