PXE boot (iVentoy) with Adguard Home (DHCP) and Unbound problem

[realmax44]

Hello, I have installed DietPi with Adguard and Unbound on my Raspi 3B+. During the installation DietPi did the configuration itself.

In my network I also have a small Unraid server on which iVentoy is running in a Linux VM and from which I have always been able to boot ISOs via PXE without any problems. Unfortunately, this no longer works since I configured Adguard Home as a DHCP server and set the DHCP setting in iVentoy to external.

After a short research I found out that this is a known problem which can be solved with the help of dnsmasq. However, this is where another problem starts for me, as I can’t get dnsmasq to work due to a port conflict. I have to say that I am more of a beginner when it comes to such things.

I know that once dnsmaq is running, I need to create a config with the following entries (the 10.0.0.15 is my iVentoy IP):

dhcp-match=set:bios,60,PXEClient:Arch:00000 
dhcp-boot=tag:bios,iventoy_loader_16000,,10.0.0.15
dhcp-match=set:efi32,60,PXEClient:Arch:00002 
dhcp-boot=tag:efi32,iventoy_loader_16000,,10.0.0.15
dhcp-match=set:efi32-1,60,PXEClient:Arch:00006 
dhcp-boot=tag:efi32-1,iventoy_loader_16000,,10.0.0.15
dhcp-match=set:efi64,60,PXEClient:Arch:00007 
dhcp-boot=tag:efi64,iventoy_loader_16000,,10.0.0.15
dhcp-match=set:efi64-1,60,PXEClient:Arch:00008 
dhcp-boot=tag:efi64-1,iventoy_loader_16000,,10.0.0.15
dhcp-match=set:efi64-2,60,PXEClient:Arch:00009 
dhcp-boot=tag:efi64-2,iventoy_loader_16000,,10.0.0.15

These entries should restore the function of iVentoy. Can anyone help me with my problem? I think that the port settings of dnsmasq have to be adjusted during installation, which I can’t do on my own. Maybe someone has another solution for this problem. The best solution would of course be to have the options for next-server and bootfile in AGH DHCP settings.

[realmax44]

Ok @ALL. Solution for this problem is to switch to pi-hole with dnsmasq as there is no help from adgurdteam. Bye!

[realmax44]

YEs