The issue I am facing: First, I am new to Pi-hole and am definitely no Linux expert
I have multiple VLANs on my network (Main, Guest, IoT). I want Pi-hole on on all three, with redundancy (2 Pi-holes), so I built two Ubuntu 22.04 VMs, each with a virtual NIC on each of the three VLANs. I build the Ubuntu system with the three NICs, and get Webmin installed, and reboot/shut down to test, and everything is fine. As soon as I install Pi-hole, then reboot, the NICs do not come up after the reboot, and I cannot get them up.
Details about my system:
ESXi 7.03 (latest patches)
One NIC with gateway and DNS, the other two have only IP
What I have changed since installing Pi-hole:
Nothing - it happens as soon as Pi-hole is installed.
As a baseline it'd be worth redoing one of the VMs from scratch the same way except this time without using Webmin, confirming the three NICs are up and that they come up after a reboot. Then install Pi-hole and observe the results. Repeat the process from scratch with just a single NIC instead and observe the results.
I'm thinking some interaction between Webmin's components and Pi-hole's installation, and/or some complication from the three VMware NICs somewhere in the process. Testing the above would be interesting to see where the constants are.
I am in the process of trying different iterations and sequences, and different ESXi hosts (the hosts in my home lab are not identical). At this point I have one that was completely built with one NIC, to which I then added a second NIC, and that is surviving reboots. I'll post my findings.
I need to note that with this latest attempt, two new YAML network configuration abstraction updates were available at the time of initial setup. They were not available with the previous attempts.