mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-18 10:13:57 +08:00
cf0f02d04a
Use LLC for the receive path of Spanning Tree Protocol packets. This allows link local multicast packets to be received by other protocols (if they care), and uses the existing LLC code to get STP packets back into bridge code. The bridge multicast address is also checked, so bridges using other link local multicast addresses are ignored. This allows for use of different multicast addresses to define separate STP domains. Signed-off-by: Stephen Hemminger <shemminger@osdl.org> Signed-off-by: David S. Miller <davem@davemloft.net>
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
#
|
|
# 802.1d Ethernet Bridging
|
|
#
|
|
|
|
config BRIDGE
|
|
tristate "802.1d Ethernet Bridging"
|
|
select LLC
|
|
---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.
|