Possible bug in Network Boot "Default BIOS file name" with multiple DHCP servers configured
-
Version: pfsense 2.6.0-RELEASE
TLDR: DHCP server on VLAN2 is providing the Next Server as configured on the DHCP server for VLAN2 but the Default BIOS file name from the DHCP server operating on LAN.
I've encountered what I believe to be a bug in the latest version of CE, just seeking to confirm this or tell me I'm crazy.
Previously I had a network booting configuration enabled on the LAN interface, this worked as expected with a defined Next Server and Default BIOS file name configured. Let's say that the next server is 172.17.2.10 and filename is pxelinux.0.
Fast forward a period of months and it came time to set this up on a second DHCP server that is running on a VLAN. This interface is created as expected with a static IPv4 address and configuring the DHCP server to match. On this server I specified the Next Server of 172.17.3.10 and a default file of http://myserver/boot .
After attempting to netboot a host on the VLAN and having some issues, I discovered that pfsense was providing the correct Next Server IP address of 172.17.3. 10, but was providing a file name of pxelinux.0 and not http://myserver/boot as expected.
Removing the original Network Booting configuration on the LAN server (leaving only the VLAN boot configuration) fixed the issue, but I don't believe this is operating as intended, and wanted to at least go through the process of logging a bug if appropriate.