Adding PXE boot options to a Network

I just wanted to share my experience with getting a Use Case up and running in my Home Lab environment. In the past I have used FOG for deploying Images to VM's and Computers on my networks. This required me to either add additional options on the DHCP server, Options 66 and 67, or deploy a DNSMasq server with FOG do layer those options on top of the regular DHCP server. On the surface, Firewalla does not allow that, yet.

I opened a support ticket and they were able to lead me down the right path to update the DHCP scopes on the back-end. Creating a pxe.conf file in ~/.router/config/dhcp/conf/ allows you to add custom options onto your desired scope.

The format is:

dhcp-boot=tag:[target interface],[DHCP Option number],[DHCP Option Value]

So it would come out like:

dhcp-option=tag:br0,67,undionly.kpxe

dhcp-option-force=tag:br0,66,"192.168.100.20"

One snag I hit that seems to be a bug (but might be intentional?) with the DNSMasq itself, Option 66 is not sent to clients. I had to find another option by digging through documentation and forums. This ultimately provided part 2 of my use case.

Format:

dhcp-boot=tag:[Target Interface],[PXE Boot File],[File Source Type],[Target File Server]

Example:

dhcp-boot=tag:br0,undionly.kpxe,tftp,192.168.100.20

Maybe not a lot of users here will need this, but wanted to share this for the few that do, and thanks a heap to support for getting me to the proper file location.

Sher

October 18, 2021 21:06

Thank you for writing this.Just ordered my Firewalla Gold and this is the first thing i am going to do, Do you have any blog or something on your setup?

Andre Liersch

November 12, 2021 08:07

Thanks for pointing me to the correct folder. I was using Pihole as my primary DHCP server before. I was able to use the exact same TFTP config on the FWG covering both Legacy and EFI boot now.

Adding PXE boot options to a Network

Comments

Didn't find what you were looking for?