firewalla gold and PXE boot from iventoy
I've been at this for a few days and I think I am getting close but not sure. I have a flat network at home. Wired Ethernet throughout the house. I have iventoy which is a PXE server running on 192.168.1.95 and I am trying to get PXE clients to boot off of it. Iventoy can act as it's own DHCP server but I don't need that since my FWG is already providing that and I have static ip addresses already setup. Iventoy can provide UEFI,UEFI32 and UEFI64 PXE booting.
I have a PXE.conf file in /home/pi/.firewalla/config/dnsmasq_local that looks like:
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
dhcp-boot=net:UEFI32,iventoy_loader_16000_ia32,,192.168.1.95
dhcp-boot=net:UEFI,iventoy_loader_16000_uefi,,192.168.1.95
dhcp-boot=net:UEFI64,iventoy_loader_16000_aa64,,192.168.1.95
dhcp-boot=net:BIOS,iventoy_loader_16000_bios,,192.168.1.95
But PXE booting my test box doesn't see it. iventoy is configured to use DHCP Server mode external although I have also tried ExternalNet.
I'm guessing it is the syntax of my PXE.conf file but at this point I am not sure. Previously I had a FOG server setup which worked well but it took a lot of trial and error getting some things to boot correctly. iventoy is based on ventoy and is designed to boot all kinds of ISO files which makes it much easier than constantly editing and reediting menus in FOG.
I imagine this is a pretty unique setup but hoping someone has an idea. I have tried multiple variations of my PXE.conf file also but again, I think it is failing because of syntax. There are lots of examples for pi, which I have tried many but still no luck.
-
When I use iventoy as a dhcp server, my pxe boot test box is getting an IP assigned to it which is not the way this should be done since the FWG is already providing DHCP. When I disable that, the same PXE boot test box never receives and IP from the FWG so something is definitely missing/not configured on the FWG. If it never receives an IP, it obviously can't PXE boot either.
-
I used dhcpping on another windows box in my home network and the d option and it returns
op=BOOTREPLY chaddr=86:F8:89:01:1C:BE hops=0 xid=DE35ECDA secs=0 flags=8000
ciaddr=0.0.0.0 yiaddr=192.168.1.104 siaddr=192.168.1.95 giaddr=0.0.0.0 sname=tftp file=undionly.kpxeso I know it is passing my PXE server but not the proper boot file.
Please sign in to leave a comment.
Comments
2 comments