netboot
netboot copied to clipboard
danderson
Packages and utilities for network booting
sudo pixiecore quick xyz --dhcp-no-bind [DHCP] Offering to boot 08:00:46:45:c1:bf [PXE] Unusable packet from 08:00:46:45:c1:bf (192.168.0.10:68): unsupported client firmware type '0' (please file a bug!) [PXE] Unusable packet from 08:00:46:45:c1:bf...
Hey, first of all, this is a great tool, thank you for your work. I have managed to boot Ubuntu Focal using the 'quick' command, which takes me to the...
How can I setup the tool to do pxe installation for only one time ? My server boot order is PXE first, so after installation is done and on next...
I wasn't able to run your test suite: > $make test > > GO111MODULE=on go test ./... > ? go.universe.tf/netboot/cmd/pixiecore [no test files] > ? go.universe.tf/netboot/cmd/pixiecore-apache2 [no test files] >...
``` [DHCP] Offering to boot 54:bf:64:25:70:b2 [TFTP] Send of "54:bf:64:25:70:b2/2" to 192.168.1.113:1427 failed: "192.168.1.113:1427": sending OACK: client aborted transfer: User aborted the transfer [TFTP] Sent "54:bf:64:25:70:b2/2" to 192.168.1.113:1428 [DHCP] Offering...
``` FreeBSD% go version go version go1.17.1 freebsd/amd64 FreeBSD% go install pixiecore go install: version is required when current directory is not in a module Try 'go install pixiecore@latest' to...
I'm running pixiecore in a docker container and when I start a new device from pxe, it first seems to boot correctly, as it is able to enter iPXE 1.0.0+,...
Pixiecore currently plays nice with existing DHCP servers, which is great... but that means you have to do more work if you _don't_ have an existing DHCP server, e.g. when...
Not a big issue, but I happened to notice that the `quick` cmd for serving up netboot.xyz is hardcoded to serve the legacy bios kernel image even to uefi clients...
It fails because there is no latest tag, only master, so it would be, pixiecore/pixiecore:master