Changes

Jump to: navigation, search

Bridges

405 bytes added, 09:00, 28 March 2014
Example
== Introduction ==
A bridge works like a transparent switch/hub between two or more interfaces and clients on computers behind any of the bridged interfaces can communicate with each other exactly as if they are were part of the same network. The bridge will learn which computers are behind what interface based on their MAC address and will only forward traffic to the necessary interface(s) which reduces traffic load in the network. For bridging two interfaces in two geographically separate locations over a tunnel see the article on [[EtherIP]].
== Example ==
Below is a complete example in [[Configuration_file|plain-text]] for bridging two local (LAN) interfaces with each other and clients on either side of the bridge computers behind both interfaces sharing the same [[DHCP#Server|DHCP Serverserver]] , default gateway and [[Firewalling|firewall rules]]. This can of course be configured using the graphical web administration, as well. Pay particular attention to the fact that the vr2 interface does not have any [[Addressing|IP address]] assigned to it. For bridging two interfaces in two geographically separate locations over a tunnel see and that the computers will instead use the article on [[EtherIP]]IP assigned to vr1 as their default gateway.
firewall {
group "mgmt"
address 192.168.1.1/24
dhcp-server { }
}
interface vr2 {
description "LAN"
group "lan"
group "mgmt"
editors
334
edits

Navigation menu