Hello Experts,
I'm encountering strange behaviour in version 3.1-17.
My physical server has 2 NICs, with 4 ints. Currently:
eth0 - vmbr0 - 10.2.x.x
eth1 - vmbr1 - 10.6.x.x
eth2 - unused
eth3 - unused
When I add a new bridged interface as follows, through the web ui:
eth2 - vmbr2 - 10.5.x.x
and reboot, I lose web gui and ssh access to the server. For some reason, it switches to use the new interface and instead of being accessible through 10.2.x.x as before, it's now accessible through 10.5.x.x.
Obviously this breaks other things I have configured. Why is it changing the default interface from vmbr0 to vmbr2, and how can I stop this from happening? I don't recall this happening when I setup my other bridged int, eth1, but that was nearly a year ago..
I'm encountering strange behaviour in version 3.1-17.
My physical server has 2 NICs, with 4 ints. Currently:
eth0 - vmbr0 - 10.2.x.x
eth1 - vmbr1 - 10.6.x.x
eth2 - unused
eth3 - unused
When I add a new bridged interface as follows, through the web ui:
eth2 - vmbr2 - 10.5.x.x
and reboot, I lose web gui and ssh access to the server. For some reason, it switches to use the new interface and instead of being accessible through 10.2.x.x as before, it's now accessible through 10.5.x.x.
Obviously this breaks other things I have configured. Why is it changing the default interface from vmbr0 to vmbr2, and how can I stop this from happening? I don't recall this happening when I setup my other bridged int, eth1, but that was nearly a year ago..
Last edited: