Warning: The actions described below are dangerous and can cause loosing of remote access to the server. It is recommended to have direct access to the server in order to revert the changes back in case of emergency.
If the server is in OVH infrastructure, additional configuration steps are required MAC assigning per IP Address
- Connect to the slave KVM node via SSH
Disable Network Manager as it may interfere with the bridge.
Additionally, it makes sense to review the network configuration file, e.g. /etc/sysconfig/network-scripts/ifcfg-eth0 and verify that it is disabled there as well
Example of basic network configuration file /etc/sysconfig/network-scripts/ifcfg-eth0 before bridge interface is configured
Install bridge-utils package:
Create a copy of the network interface to make changes revertible:
Note: It is recommended move non-used configuration files out of the network-scripts/ sub-directory. Be aware that configuration files that starts from ifcfg-* files will be applied, including ifcfg-eth0.backup file.
Create the bridge file:
Copy network configuration settings from ifcfg-eth0 to ifcfg-br0 file to make it look like below:
Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 as below:
Warning: All parameters should be written with capitalized characters, e.g. BRIDGE=br0 and NOT Bridge=br0
Warning: In case there is a /etc/sysconfig/network-scripts/route-eth0 file (some Hetzner installation has them), the file should be renamed to /etc/sysconfig/network-scripts/route-br0 accordingly.
Restart the network service to apply the changes:
Check that physical interface eth0 is linked to bridged interface br0If there are any errors while configuring bridge check for known issues on our Support Portal, like below:
Bridge interface does not work on the fresh install
During configuration of bridge interface network fails to restart: bridge support not available: brctl not found