I have a multihome TrueNAS box (see signature) with networking roughtly like this:
oce0 ----> LAGG0 ----- bridge0 [ ADMIN NET xxx.xxx.161.0/24 ]
igb0 --------/
oce1 ----> LAGG1 ----> bridge1 [ User NET xxx.xxx.162.0/24 ] <----- vnet0 [plex jail]
igb1 --------/ \------------------------------------ vnet1 [Linux VM in bhyve]
After a reboot of the system, vnet0 to the Jail and vnet1 to the VM basically keep coming up on bridge0. This is even although they are supposed to be bridged to bridge1 and the management UI shows this. This also happens if I reboot the Linux VM - it gets wrongly reconnected to bridge0.
I can log in manually and fix it of course use ifconfig lagg0 deletem vnet0 && ifconfig lagg1 addm vnet0 which is easy enough but a bit of a PITA. I suppose I could automatically get around it with a cron job too.
I've seen there's a few posts about this kind of issue previously but I didn't yet find a workable (for me) solution and wondered if this has been resolved yet, maybe in TrueNAS 13 or TrueNAS Scale. So anyway..
Thanks in advance,
Aidan
oce0 ----> LAGG0 ----- bridge0 [ ADMIN NET xxx.xxx.161.0/24 ]
igb0 --------/
oce1 ----> LAGG1 ----> bridge1 [ User NET xxx.xxx.162.0/24 ] <----- vnet0 [plex jail]
igb1 --------/ \------------------------------------ vnet1 [Linux VM in bhyve]
After a reboot of the system, vnet0 to the Jail and vnet1 to the VM basically keep coming up on bridge0. This is even although they are supposed to be bridged to bridge1 and the management UI shows this. This also happens if I reboot the Linux VM - it gets wrongly reconnected to bridge0.
I can log in manually and fix it of course use ifconfig lagg0 deletem vnet0 && ifconfig lagg1 addm vnet0 which is easy enough but a bit of a PITA. I suppose I could automatically get around it with a cron job too.
I've seen there's a few posts about this kind of issue previously but I didn't yet find a workable (for me) solution and wondered if this has been resolved yet, maybe in TrueNAS 13 or TrueNAS Scale. So anyway..
Thanks in advance,
Aidan