Here I am again,
the issue is quite simple (and was probably there for a few months but I never realised).
The promox I took over already had one linux bridge setup, VMBR0 (which I'm guessing is from the installation), I then created a second linux bridge to isolate my lxc's and vm's >> VMBR1.
All was good, untill I needed to make another linux Bridge. I do the exact same things, but when I try to make lxc's ping each other it doesn't work. So I look around, and surprise the NIC is down. I try to bring it up, but nothing. I go in the server room, and of course, no cables were plugged (except for the first one > VMBR0 ).
So I am sitting there with my colleagues, wondering how the heck it's been working for the past months.
Been doing some tests today and I realised that lxc's using VMBR0 could still ping lxc's using VMBR1 and vice versa. Am I missing something (probably) ?
192.168.100.10 can ping 192.168.100.254 and vice versa.
Physically speaking, eno5 (vmbr0) and eno6 (vmbr1) are plugged on a switch.
the issue is quite simple (and was probably there for a few months but I never realised).
The promox I took over already had one linux bridge setup, VMBR0 (which I'm guessing is from the installation), I then created a second linux bridge to isolate my lxc's and vm's >> VMBR1.
All was good, untill I needed to make another linux Bridge. I do the exact same things, but when I try to make lxc's ping each other it doesn't work. So I look around, and surprise the NIC is down. I try to bring it up, but nothing. I go in the server room, and of course, no cables were plugged (except for the first one > VMBR0 ).
So I am sitting there with my colleagues, wondering how the heck it's been working for the past months.
Been doing some tests today and I realised that lxc's using VMBR0 could still ping lxc's using VMBR1 and vice versa. Am I missing something (probably) ?
192.168.100.10 can ping 192.168.100.254 and vice versa.
Physically speaking, eno5 (vmbr0) and eno6 (vmbr1) are plugged on a switch.
Friendly yours,
Anone