Today I started experimenting with virtualization, I could not deploy a VM on my bond interface, I think because I already have an IPVLAN created in Portainer for my Dockers, I then created a new bridge interface, which worked I could deploy my VM but it was extremely laggy and slow and inside the VM the “wired connection” would not work, after then I gave up for today, an hour later I had to restart my TrueNAS, It did not got back up, I immediately knew it had something to do with that bridge interface I created, I hooked up a monitor and deleted the bridge interface via the console, rebooted and it ran again, now, did I do something wrong when I tried to deploy a VM? I can’t have a IPVLAN and a MACVLAN on the same bond interface? For it to work, do I need to break my bond/loadbalancing interface, seperate them, 1 NIC for my IPVLAN/Dockers/Portainer and 1 for virtualization in TN? Or is there another way?
Not sure if this will help, but any IP address needs to be on the bridge, if you IP on the vlan or nic it will not work (the VM will not communicate on that network), you’ll need to move the IP address to the bridge.
My VM’s then connect to the bridge, except for when I don’t have an IP on the nas and the VM just needs an access vlan, it uses vlan or nic without a vlan.
For docker, what are you using? I use my own compose yaml and do not need to do anything special for it to work. I do configure specific IP address for ports, but don’t do any docker networks atm. I do this on other docker instances, but don’t have a use case yet on the nas.
I get it, but how do I connect my existing bond to the bridge interface?
I created an IPVLAN on Portainer so my Dockers are in a seperate network, when I first heard of it (NetworkChuck has a video on it, the advantages etc, and how to set it up, which is fairly easy) I tried it out and it took me hours because I could not get it too work, turned out, I was already using a MACVLAN and when I deleted that, the IPVLAN instantly came up, so my conclusion was that it’s either a MACVLAN (which I see on the settings when you create a VM on TrueNAS) OR an IPVLAN, which I already have in use… and I do not want to get rid off…
The problem was that when I rebooted, I could not reach my TrueNAS, it showed the correct IP when I plugged the monitor in, it just wasn’t accessible, when I deleted that bridge I created my instance instantly came back up, OR maybe I have not configured the “network side” of TrueNAS correctly, the only thing I did was bond 2 NIC’s together into a loadbalancing bond, no bridge, no nothing except for the IPVLAN in Portainer
I don’t have any bonded interfaces, but you should see the bond under the bridge members on the bridge.
Typically for bonded interfaces you need to do link aggregation such as ethernet-channel on the switch side. If you havn’t done this, or cannot, it might explain your issue???
Not for loadbalancing, but for link-aggregation yes, but that part works, I have 1 IP adres and if I pull either cable out everything remains working and I see activity on both NIC’s on the LED’s and on the network page of TrueNAS, I think the way I set up the bond and IPVLAN just cannot work with the VM’s on top of that, because the VM’s only (as far as I know now) support MACVLAN
Solved it, I created another IPVLAN but on my router, I created the VLAN in TrueNAS in networks and I can attach my VM’s to that VLAN, everything works as expected, also rebooted a couple of times to make sure that worked too!
