Repository navigation
Rebuild PXE provisioning with iPXE and ProxyDHCP - #1
Merged
Merged
Conversation
greksw
marked this pull request as ready for review
September 15, 2026 09:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rebuilds the legacy PXE installer into a portfolio-ready Linux provisioning toolkit while preserving repository history.
Main changes
undionly.kpxe) and x86_64 UEFI (ipxe-snponly-x86_64.efi);Architecture
Existing DHCP provides IP/gateway/DNS. dnsmasq only answers PXE discovery in proxy mode. Firmware receives an iPXE chainloader over TFTP, then iPXE retrieves the menu and installation assets over HTTP.
Follow-up
After review, the repository can be renamed to
linux-pxe-provisioning. The separatepxe_server2repository can then be archived because its useful multi-distribution provisioning concept is represented in this v2 implementation.Validation status
GitHub Actions Bash syntax validation and ShellCheck pass on the current branch. End-to-end BIOS/UEFI network boot should still be validated on a disposable VM or isolated provisioning VLAN before production use.