This directory contains everything needed to set up a PXE boot server for DriveWipe Live. Clients network-boot directly into the DriveWipe TUI, with no USB drives required.
live/pxe/
├── dnsmasq.conf # DHCP + TFTP server configuration
├── ipxe/
│ ├── boot.ipxe # iPXE chainload script (auto-boot)
│ └── menu.ipxe # iPXE boot menu with options
└── README.md # This file
- dnsmasq — DHCP + TFTP server (
apt install dnsmasq/dnf install dnsmasq) - iPXE — Network boot firmware (optional, for HTTP boot; TFTP works without it)
- DriveWipe Live artifacts — Built via
scripts/build-live.sh:vmlinuz— Linux kernelinitramfs.img— DriveWipe Live initramfsdrivewipe-live.iso— Full ISO (optional, for hybrid boot)
# From the repository root:
./scripts/build-live.sh
# Or via xtask:
cargo xtask live-buildsudo mkdir -p /var/lib/tftpboot/drivewipe
sudo cp output/vmlinuz /var/lib/tftpboot/drivewipe/
sudo cp output/initramfs.img /var/lib/tftpboot/drivewipe/
sudo cp live/pxe/ipxe/boot.ipxe /var/lib/tftpboot/drivewipe/
sudo cp live/pxe/ipxe/menu.ipxe /var/lib/tftpboot/drivewipe/# Edit the configuration for your network interface:
sudo cp live/pxe/dnsmasq.conf /etc/dnsmasq.d/drivewipe.conf
sudo vi /etc/dnsmasq.d/drivewipe.conf # adjust interface, DHCP range
# Restart dnsmasq:
sudo systemctl restart dnsmasqSet the client machine to PXE boot (usually F12 or network boot in BIOS/UEFI). The iPXE menu will appear, and the client will auto-boot into DriveWipe Live after a 10-second timeout.
# Test PXE boot locally without hardware:
qemu-system-x86_64 \
-m 2G \
-boot n \
-device virtio-net-pci,netdev=net0 \
-netdev user,id=net0,tftp=/var/lib/tftpboot,bootfile=drivewipe/boot.ipxe- PXE server and clients must be on the same Layer 2 network (same VLAN/subnet)
- No other DHCP servers should be running on the same network segment
- If using an existing DHCP server, configure it to point
next-serverandfilenameto the PXE server instead of running dnsmasq DHCP
- The PXE boot process is unencrypted over TFTP — only use on trusted networks
- DriveWipe Live runs with root privileges for direct drive access
- Consider using HTTPS boot (iPXE supports it) in production environments