9.2.5. Network Bridge

A network bridge is a Link Layer device which forwards traffic between networks based on MAC addresses and is therefore also referred to as a Layer 2 device. It makes forwarding decisions based on tables of MAC addresses which it builds by learning what hosts are connected to each network. A software bridge can be used within a Linux host in order to emulate a hardware bridge, for example in virtualization applications for sharing a NIC with one or more virtual NICs. This case will be illustrated here as an example.

To create a network bridge, create a file in the /etc/sysconfig/network-scripts/ directory called ifcfg-brN, replacing N with the number for the interface, such as 0.

The contents of the file is similar to whatever type of interface is getting bridged to, such as an Ethernet interface. The differences in this example are as follows:

• The DEVICE directive is given an interface name as its argument in the format brN, where N is replaced with the number of the interface.
• The TYPE directive is given an argument Bridge or Ethernet. This directive determines the device type and the argument is case sensitive.
• The bridge interface configuration file now has the IP address and the physical interface has only a MAC address.
• An extra directive, DELAY=0, is added to prevent the bridge from waiting while it monitors traffic, learns where hosts are located, and builds a table of MAC addresses on which to base its filtering decisions. The default delay of 30 seconds is not needed if no routing loops are possible.
• The NM_CONTROLLED=no should be added to the Ethernet interface to prevent NetworkManager from altering the file. It can also be added to the bridge configuration file in case future versions of NetworkManager support bridge configuration.

The following is a sample bridge interface configuration file using a static IP address:

Example 9.2. Sample ifcfg-br0 interface configuration file

 

DEVICE=br0
TYPE=Bridge
IPADDR=192.168.1.1
NETMASK=255.255.255.0
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
DELAY=0

 To complete the bridge another interface is created, or an existing interface is modified, and pointed to the bridge interface. The following is a sample Ethernet interface configuration file pointing to a bridge interface. Configure your physical interface in /etc/sysconfig/network-scripts/ifcfg-ethX, where X is a unique number corresponding to a specific interface, as follows:

 

 

Example 9.3. Sample ifcfg-ethX interface configuration file

 

DEVICE=ethX
TYPE=Ethernet
HWADDR=AA:BB:CC:DD:EE:FF
BOOTPROTO=none
ONBOOT=yes
NM_CONTROLLED=no
BRIDGE=br0

 Note

 

For the DEVICE directive, almost any interface name could be used as it does not determine the device type. Other commonly used names include tap, dummy and bond for example. TYPE=Ethernet is not strictly required. If the TYPE directive is not set, the device is treated as an Ethernet device (unless it's name explicitly matches a different interface configuration file.)

You can refer to Section 9.2, “Interface Configuration Files” for a review of the directives and options used in network interface config files.

 

Warning

If you are configuring bridging on a remote host, and you are connected to that host over the physical NIC you are configuring, please consider the implications of losing connectivity before proceeding. You will lose connectivity when restarting the service and may not be able to regain connectivity if any errors have been made. Console, or out-of-band access is advised.

 

service network restart 

 

Restart the networking service, in order for the changes to take effect, as follows:

 

service network restart 

An example of a network bridge formed from two or more bonded Ethernet interfaces will now be given as this is another common application in a virtualization environment. If you are not very familiar with the configuration files for bonded interfaces then please refer to Section 9.2.4, “Channel Bonding Interfaces”

 

 

Create or edit two or more Ethernet interface configuration files, which are to be bonded, as follows:

 

DEVICE=ethX
TYPE=Ethernet
USERCTL=no
SLAVE=yes
MASTER=bond0
BOOTPROTO=none
HWADDR=AA:BB:CC:DD:EE:FF
NM_CONTROLLED=no

 Note

 

Using ethX as the interface name is common practice but almost any name could be used. Names such as tap, dummy and bond are commonly used.

 

Create or edit one interface configuration file, /etc/sysconfig/network-scripts/ifcfg-bond0, as follows:

 

DEVICE=bond0
ONBOOT=yes
BONDING_OPTS='mode=1 miimon=100'
BRIDGE=brbond0
NM_CONTROLLED=no

For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to Section 28.7.2, “Using Channel Bonding”. 

 

Create or edit one interface configuration file, /etc/sysconfig/network-scripts/ifcfg-brbond0, as follows:

 

DEVICE=brbond0
ONBOOT=yes
TYPE=Bridge
IPADDR=192.168.1.1
NETMASK=255.255.255.0
NM_CONTROLLED=no

 

 Figure 9.1. A network bridge consisting of two bonded Ethernet interfaces.

 

We now have two or more interface configuration files with the MASTER=bond0 directive. These point to the configuration file named /etc/sysconfig/network-scripts/ifcfg-bond0, which contains the DEVICE=bond0 directive. This ifcfg-bond0 in turn points to the /etc/sysconfig/network-scripts/ifcfg-brbond0 configuration file, which contains the IP address, and acts as an interface to the virtual networks inside the host.

Restart the networking service, in order for the changes to take effect, as follows: