tobix / pxe

tftproot for PXE boot menu

tftproot for PXE

This is a simple setup for a PXE environment on a Debian 10 (buster) system.

This repository uses a Git submodule to include localboot.lua, so you should probably use

git clone --recursive https://github.com/TobiX/pxe.git

or update the submodules after the clone:

git submodule init
git submodule update

Most tools are just symlinked into the matching Debian packages, so you should install at least

syslinux-common syslinux-efi pxelinux

MultiArch support

Since 2021-05, this repository uses a bunch of symlinks to support BIOS and EFI64 boot from the same config. While this seems to work for some options, the EFI code path is much less tested then the BIOS code path. (there are probably some options which flat-out don't work in EFI mode)

Debian Installer

To use the Debian installer entry, install di-netboot-assistant, configure it to your liking and run

di-netboot-assistant --arch=amd64 install stable stable-gtk

(or similar).

grml

Grab the files vmlinuz and initrd.img from the grml ISO (they are somewhere in boot/grml64*/) and put them into the grml directory. Put the GRML SquashFS (In live/grml64*/*.squashfs on the ISO) on a webserver and adjust the URL in default.cfg.

Using with dnsmasq

This is probably the minimal setup to use this setup with dnsmasq (assuming this isn't the "main" DHCP server):

dhcp-range=192.168.1.0,proxy
pxe-service=x86PC,"pxelinux BIOS",bios/pxelinux
pxe-service=x86-64_EFI,"syslinux EFI64",efi64/syslinux.efi
enable-tftp
tftp-root=/srv/tftp

# Disable DNS (if you are using a different server for DNS)
port=0

pxe's Issues

Security Policy violation Branch Protection

This issue was automatically created by Allstar.

Security Policy Violation
No protection found for branch main

---

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

Security Policy violation SECURITY.md

This issue was automatically created by Allstar.

Security Policy Violation
Security policy not enabled.
A SECURITY.md file can give users information about what constitutes a vulnerability and how to report one securely so that information about a bug is not publicly visible. Examples of secure reporting methods include using an issue tracker with private issue support, or encrypted email with a published key.

To fix this, add a SECURITY.md file that explains how to handle vulnerabilities found in your repository. Go to https://github.com/TobiX/pxe/security/policy to enable.

For more information, see https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository.

---

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.