non-efi netboot through IPXE broken when IPv6 configured properly

[Stéphane Graber]

I was recently wondering why it was that I was running SLAAC on my MAAS-managed VLANs rather than just having my gateway set the managed flag indicate of DHCPv6 and let MAAS handle it as it should.

So I fixed my config to have my router properly set the Managed bit, then rebooted a test system.

That's when I got reminded of why I had to do this in the past.
Properly configuring IPv6 to have MAAS handle DHCPv6 makes iPXE detect IPv6 support, grab an address from MAAS over DHCPv6 and then parse the next-server data received in there.

So far it all sounds sensible but that's when it all goes south. The DHCPv6 packet somehow tells iPXE to perform EFI boot, loading boox64.efi and crashing because, well, this isn't an EFI system.

Seems like MAAS needs some DHCPv6 config to properly distinguish between EFI and non-EFI and return appropriate paths when not in a UEFI environment.

[Jerzy Husakowski (jhusakowski)]

Issues with IPv6 support are moved to product feedback backlog (internal ref PF-3897)