Bonded network configuration

[Tom Moyer]

I have a server that I want to have the following configuration. Two network interfaces in a bonded configuration and a third separate connection that can be used mostly for SSH. I thought the network configuration shown below would work, but SSH and the web UI stop responding. Any insight into how to configure this would be helpful.

 

[aaron]

Well, two things I noticed. First, there is a typo in bond-slaCes, should be bond-slaves.

Then having two interfaces (vmbr0, enp0s9) in the same subnet (172.16.10.0/24) is problematic as the machine can reach the same network on both interfaces. This usually leads to unexpected routing behavior.

What does ip route show?

Either you can separate your networks into different subnets or remove one of the interfaces. If you can separate them, please be aware that there can only be one default gateway. If certain traffic needs to go out via another interface, you need to define more granular routes.

 

[Tom Moyer]

I moved the ens0s9 interface to another network and fixed the typo. Now I have access through SSH and the Web UI. However, when I create a container and put it on the bridge interface vmbr0 the container does not get an IP address (using DHCP) and if I statically assign an IP address it still does not have network access.

Here is the updated configuration for the host:

and here is the output of "ip route" and "ip a":

 

[spirit]

try with a simple active-backup bond first. (I'm not sure that dhcp is playing well with balance xor)

also "bond-primary" option should be setup in the bond interface, not enp0s3 (and it's working with active-backup only).