Networking - two networks and shell behavior

[AccelerationLab]

I have a server running at a remote location so I want to retain a backup link in the event of a problem in the future. So I created a bond0 that contains 5 network interfaces that are connected to the local network. I then created a bridge vmbr0 and made bond0 as its slave. This works well all the virtual machines are connected to it and they work great.

For the backup connection, I created a second bridge vmbr1 and made the 6th ethernet adapter its slave.

vmbr0 = CIDR: 10.3.10.4/24 GW: 10.3.10.1
vmbr1 = CIDR: 10.3.10.250/24 GW:

The issue here is if is set the GateWay in vmbr1 to the same gateway in vmbr0 the settings would not be feasible. Rightfully so. The problem I run into is the shell commands. In the shell of proxmox sometimes it has a preference for vmbr1 vs vmbr0. When it does updating can become impossible.

Any suggestions on how to get Proxmox VE to prefer one connection over the other?

output of 'route'

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.3.10.1       0.0.0.0         UG    0      0        0 vmbr0
10.3.10.0       0.0.0.0         255.255.255.0   U     0      0        0 vmbr1
10.3.10.0       0.0.0.0         255.255.255.0   U     0      0        0 vmbr0

 

[bbgeek17]

Dont do it.
https://access.redhat.com/solutions/30564

Resolution
Is is usually not a good idea to connect two interfaces using the same subnet on the system, as you may run into the issues presented in the following two pages:

Why is my server responding to arp requests from the wrong interface on Red Hat Enterprise Linux ?
When RHEL has multiple IPs configured, only one is reachable from a remote network. Or why does RHEL ignore packets when the route for outbound traffic differs from the route of incoming traffic?

The recommended solution is to use a single interface or a single bond/team interface, then add the other IP addresses to that interface in the form of an alias IP address. If fault tolerance and/or load balancing is required at the network interface level, then an alias on a bond or team should be used. Please note that teaming is not supported in Red Hat Enterprise Linux 6 or earlier. If fault tolerance and/or load balancing is not needed at the interface level, then you can add the alias IP address to a single interface.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox