| Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 1 | # |
| 2 | # 802.1d Ethernet Bridging |
| 3 | # |
| 4 | |
| 5 | config BRIDGE |
| 6 | tristate "802.1d Ethernet Bridging" |
| Stephen Hemminger | cf0f02d | 2006-03-20 22:59:06 -0800 | [diff] [blame] | 7 | select LLC |
| Patrick McHardy | 7c85fbf | 2008-07-05 21:25:56 -0700 | [diff] [blame] | 8 | select STP |
| Sam Ravnborg | 6a2e9b7 | 2005-07-11 21:13:56 -0700 | [diff] [blame] | 9 | ---help--- |
| 10 | If you say Y here, then your Linux box will be able to act as an |
| 11 | Ethernet bridge, which means that the different Ethernet segments it |
| 12 | is connected to will appear as one Ethernet to the participants. |
| 13 | Several such bridges can work together to create even larger |
| 14 | networks of Ethernets using the IEEE 802.1 spanning tree algorithm. |
| 15 | As this is a standard, Linux bridges will cooperate properly with |
| 16 | other third party bridge products. |
| 17 | |
| 18 | In order to use the Ethernet bridge, you'll need the bridge |
| 19 | configuration tools; see <file:Documentation/networking/bridge.txt> |
| 20 | for location. Please read the Bridge mini-HOWTO for more |
| 21 | information. |
| 22 | |
| 23 | If you enable iptables support along with the bridge support then you |
| 24 | turn your bridge into a bridging IP firewall. |
| 25 | iptables will then see the IP packets being bridged, so you need to |
| 26 | take this into account when setting up your firewall rules. |
| 27 | Enabling arptables support when bridging will let arptables see |
| 28 | bridged ARP traffic in the arptables FORWARD chain. |
| 29 | |
| 30 | To compile this code as a module, choose M here: the module |
| 31 | will be called bridge. |
| 32 | |
| 33 | If unsure, say N. |