Bridge¶
Bridge allows the connection of two separate networks as if they were a single network. It builds a database by inspecting the destination MAC address of packets flowing through the bridged interfaces: known destination is forwarded, unknown is broadcast to all other networks.
To configure a bridge, enter the context interface
type bridge
from the VRF
in which you plan to define the bridge logical interface. The bridge
configuration is valid as soon as the slave interfaces are set.
Here is an example of bridge named br0
in VRF main, using two interfaces
eth0
and eth1
.
vrouter running vrf main# interface bridge br0
vrouter running bridge br0# link-interface eth0
vrouter running bridge br0# link-interface eth1
vrouter running bridge br0# commit
The bridge interface is configured provided eth0
and eth1
are present in
VRF main.
Let’s fetch the state after committing this configuration:
vrouter running vrf main# interface bridge br0
vrouter running bridge br0# show state
bridge br0
oper-status UNKNOWN
enabled true
mtu 1500
link-interface eth0
link-interface eth1
ethernet
mac-address 9a:cb:9c:2e:fd:07
..
counters
in-octets 0
out-octets 0
in-errors 0
in-unicast-pkts 0
in-discards 0
out-unicast-pkts 7
out-errors 0
out-discards 0
..
ipv6
address fe80::98cb:9cff:fe2e:fd07/64
..
..
The same configuration can be made using this NETCONF XML configuration:
vrouter running config# show config xml absolute vrf main interface bridge br0
<config xmlns="urn:6wind:vrouter">
<vrf>
<name>main</name>
<interface xmlns="urn:6wind:vrouter/interface">
<bridge xmlns="urn:6wind:vrouter/bridge">
<name>br0</name>
<enabled>true</enabled>
(...)
<link-interface>
<slave>eth0</slave>
</link-interface>
<link-interface>
<slave>eth1</slave>
</link-interface>
</bridge>
</interface>
</vrf>
</config>
See also
The command reference for details.