First off, I would like to thank you for this project. I will soon buy the pro version to help support this project.
I am running 2 instances of pihole in a high avail. These are set up as dhcp servers and hand out static and dynamic leases. So iventoy is set to use external dhcp. In dnsmasq.conf I have the boot option for the "next-server":
dhcp-boot=iventoy_loader_16000,10.10.8.86,10.10.8.86
I get to boot from the pxe server just fine. But when I try to install from a Linux ISO like debian or ubuntu I get network problem. You can see from the images below that I get two "network cards" when I boot from the pxe server. One with the actual network card "ens160", and one called "wired connection 1". With the actual network card, it gets assigned with an ip address but not with dns, but if I switch to the "wired connection" it gets assigned with ip address and dns. With boot from pxe i auto assign the "ens160" network card on debian and ubuntu.
Am I missing some crucial settings in my dnsmaq config file? Or is this a bug with iventoy running with external dhcp server? I am running iventoy-1.0.09 on debian but I also tried this on windows.
I am running 2 instances of pihole in a high avail. These are set up as dhcp servers and hand out static and dynamic leases. So iventoy is set to use external dhcp. In dnsmasq.conf I have the boot option for the "next-server":
dhcp-boot=iventoy_loader_16000,10.10.8.86,10.10.8.86
I get to boot from the pxe server just fine. But when I try to install from a Linux ISO like debian or ubuntu I get network problem. You can see from the images below that I get two "network cards" when I boot from the pxe server. One with the actual network card "ens160", and one called "wired connection 1". With the actual network card, it gets assigned with an ip address but not with dns, but if I switch to the "wired connection" it gets assigned with ip address and dns. With boot from pxe i auto assign the "ens160" network card on debian and ubuntu.
Am I missing some crucial settings in my dnsmaq config file? Or is this a bug with iventoy running with external dhcp server? I am running iventoy-1.0.09 on debian but I also tried this on windows.
