Noticed Pixiecore rejects DHCP requests from firmware advertising architecture type 16 ("x86-64 UEFI HTTP Boot") with "unsupported client firmware type '16'. I checked this is a known upstream issue and pixiecore also isn't actively developed anymore.
dnsmasq handles type 16 natively and is maintained. The script pixiecore serves here (generatedPixieScript) is static and never varies per machine, so we're not even using pixiecore's main selling point.
Before I put together a PR: is a dnsmasq-based refactor of netboot/ welcome, or was pixiecore picked for a reason I'm missing?
Noticed Pixiecore rejects DHCP requests from firmware advertising architecture type 16 ("x86-64 UEFI HTTP Boot") with "unsupported client firmware type '16'. I checked this is a known upstream issue and pixiecore also isn't actively developed anymore.
dnsmasq handles type 16 natively and is maintained. The script pixiecore serves here (generatedPixieScript) is static and never varies per machine, so we're not even using pixiecore's main selling point.
Before I put together a PR: is a dnsmasq-based refactor of netboot/ welcome, or was pixiecore picked for a reason I'm missing?