Product SiteDocumentation Site

Chapter 4. Configure Network Bonding

4.1. Understanding the Default Behavior of Master and Slave Interfaces
4.2. Creating a Bond Connection Using a GUI
4.2.1. Establishing a Bond Connection
4.3. Using the Command Line Interface (CLI)
4.3.1. Check if Bonding Kernel Module is Installed
4.3.2. Create a Channel Bonding Interface
4.3.3. Creating SLAVE Interfaces
4.3.4. Activating a Channel Bond
4.3.5. Creating Multiple Bonds
4.3.6. Configuring a VLAN over a Bond
4.4. Using Channel Bonding
4.4.1. Bonding Module Directives
4.5. Using the NetworkManager Command Line Tool, nmcli
4.6. Additional Resources
4.6.1. Installed Documentation
4.6.2. Online Documentation
Fedora allows administrators to bind multiple network interfaces together into a single, bonded, channel. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.


The use of direct cable connections without network switches is not supported for bonding. The failover mechanisms described here will not work as expected without the presence of network switches.


The active-backup, balance-tlb and balance-alb modes do not require any specific configuration of the switch. Other bonding modes require configuring the switch to aggregate the links. For example, a Cisco switch requires EtherChannel for Modes 0, 2, and 3, but for Mode 4 LACP and EtherChannel are required. See the documentation supplied with your switch and see

4.1. Understanding the Default Behavior of Master and Slave Interfaces

When controlling bonded slave interfaces using the NetworkManager daemon, and especially when fault finding, keep the following in mind:
  1. Starting the master interface does not automatically start the slave interfaces.
  2. Starting a slave interface always starts the master interface.
  3. Stopping the master interface also stops the slave interfaces.
  4. A master without slaves can start static IP connections.
  5. A master without slaves waits for slaves when starting DHCP connections.
  6. A master with a DHCP connection waiting for slaves completes when a slave with a carrier is added.
  7. A master with a DHCP connection waiting for slaves continues waiting when a slave without a carrier is added.