Files
Kernel/net/bridge/Kconfig

57 lines
2.0 KiB
Plaintext

#
# 802.1d Ethernet Bridging
#
config BRIDGE
tristate "802.1d Ethernet Bridging"
select LLC
select STP
---help---
If you say Y here, then your Linux box will be able to act as an
Ethernet bridge, which means that the different Ethernet segments it
is connected to will appear as one Ethernet to the participants.
Several such bridges can work together to create even larger
networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
As this is a standard, Linux bridges will cooperate properly with
other third party bridge products.
In order to use the Ethernet bridge, you'll need the bridge
configuration tools; see <file:Documentation/networking/bridge.txt>
for location. Please read the Bridge mini-HOWTO for more
information.
If you enable iptables support along with the bridge support then you
turn your bridge into a bridging IP firewall.
iptables will then see the IP packets being bridged, so you need to
take this into account when setting up your firewall rules.
Enabling arptables support when bridging will let arptables see
bridged ARP traffic in the arptables FORWARD chain.
To compile this code as a module, choose M here: the module
will be called bridge.
If unsure, say N.
# brcm start
config BR_IGMP_SNOOP
tristate "Bridge IGMPv2/3 Snooping"
---help---
If you say Y here, it will enable IGMP snooping which optimizes
multicast forwarding
config BR_IGMP_SNOOP_SWITCH_PATCH
tristate "Software patch for Switch IGMP Packet flooding"
---help---
IGMP snooping does not work properly if more than one LAN client is
connected to LAN side & these hosts want to join same IGMP grup. This
problem is due to ROBO switch 5325/5398 flooding igmp report packets
on all LAN ports & IGMP report suppression mechanism. If you say Y,
here it will enable a software patch to avoid this problem.
config BR_MLD_SNOOP
tristate "Bridge MLDv1/2 Snooping"
---help---
If you say Y here, it will enable IPV6 MLD snooping which optimizes
multicast forwarding
# brcm end