DHCPv6 does not pass PXE options to UEFI IPv6 clients
Peek last edited by
UEFI IPv6 PXE clients cannot network boot via pfsense. Using an "external" ISC-DHCP-Server confirms the issue.
- TFTP Server
- Install, enable & upload "snponly.efi"
- Router Advertisement
- Set to either "assisted" or "managed"
- DHCPv6 Server
- Check "Enable network Booting" and
- set "bootfile URL" to "tftp://[2001:fb::1]/snponly.efi"
PXE client will only repetatively retry to acquire IPv6 address. (as seen form /var/log/dhcp.log )
- DHCPv6 Options
- Setting additional BOOTP/DHCP Options to "59" with "tftp://[2001:fb::1]/snponly.efi" has not effect.
However, setting up a VM with ISC-DHCP-Server as to only provide DHCPv6 option 59:
option dhcp6.bootfile-url code 59 = string; option dhcp6.bootfile-url "tftp://[2001:fb::1]/snponly.efi
then disabling pfsense's DHCPv6 server and starting the ISC-DHCP-Server will allow the UEFI IPv6 PXE Client to acquire the bootfile from pfsense's TFTP server ... and be merily on it's way.
So what does the config on pfSense look like vs your external server config? There must be some difference in the formatting or naming of the option to explain what is happening.