{% extends "ui/_layout.html" %}
{% block title %}Netboot artifacts - bty-web{% endblock %}
{% block subnav %}
{% with sections=[
{"key": "list", "label": "List", "icon": "list-ul", "href": "/ui/boot"},
{"key": "dhcp-pxe", "label": "DHCP / PXE", "icon": "hdd-network", "href": "/ui/boot?section=dhcp-pxe"},
{"key": "tftp", "label": "TFTP daemon", "icon": "cpu", "href": "/ui/boot?section=tftp"},
] , active=section %}
{% include "ui/_subnav.html" %}
{% endwith %}
{% endblock %}
{% block intro %}
{% from "ui/_intro_box.html" import render as intro_box %}
{% call intro_box() %}
The bty live env that PXE clients chain into when their
assignment has boot_policy=flash. Until these
files are present, machines with boot_policy=flash
cannot actually flash. Use the Fetch control in
the table header below (tag defaults to latest) to
populate them from GitHub releases.
{% endcall %}
{% endblock %}
{% block content %}
{% if section == "dhcp-pxe" %}
{# Router-side cheatsheet. The bits the operator pastes into
UniFi / pfSense / dnsmasq DHCP config to point PXE clients
at this appliance. Reference-only; no editable fields here
-- bty doesn't run DHCP, the LAN router does. #}
bty-server runs a TFTP daemon (dnsmasq) and serves boot artifacts over HTTP. The DHCP side stays with your LAN's router (or DHCP server); bty deliberately doesn't try to replace it. Point your router at this appliance with the settings below.
{% if missing_netboot_artifacts %}{{ boot_root }}:
{% for name in missing_netboot_artifacts %}
{{ name }}{% if not loop.last %}, {% endif %}
{% endfor %}.
PXE clients will chain into iPXE but get 404 on the
kernel fetch until these files are present.
| Interface | State | IPv4 |
|---|---|---|
{{ iface.name }} |
{{ iface.operstate }} |
{% if iface.ipv4 %}
{{ iface.ipv4 }}/{{ iface.prefix }}
{% else %}
(no address)
{% endif %}
|
| (no interfaces detected) | ||
Configure your LAN's DHCP server to tag PXE clients with the options below. For UniFi: Settings → Networks → [your LAN] → Advanced → DHCP → Network Boot. For pfSense / OpenWRT / dnsmasq: equivalent options on the DHCP service.
| Option | Value | Notes |
|---|---|---|
option 60 |
PXEClient |
Vendor-class echo. Strict UEFI firmware filters offers without it. |
option 66 / Next-Server |
{% if primary and primary.ipv4 %}
{{ primary.ipv4 }}
{% else %}
(this appliance's LAN IP)
{% endif %}
|
The TFTP server. Same box as bty-web. |
option 67 / Boot-Filename |
ipxe.efi |
For UEFI PXEClient (arch 6/7/9). Use undionly.kpxe for legacy BIOS (arch 0). |
option 67 for user-class=iPXE |
http://{% if primary and primary.ipv4 %}{{ primary.ipv4 }}{% else %}<bty-server>{% endif %}:8080/pxe-bootstrap.ipxe
|
Stops iPXE chain-loop. Different bootfile when iPXE re-DHCPs. |
For UEFI HTTP-Boot (vendor-class HTTPClient), point
option 67 at
http://{% if primary and primary.ipv4 %}{{ primary.ipv4 }}{% else %}<bty-server>{% endif %}:8080/boot/ipxe.efi
instead (no TFTP roundtrip).
The local dnsmasq.service serves the TFTP root
(/var/lib/tftpboot). Stop it to take PXE offline
without disabling DHCP; restart it to pick up new bootfiles
staged into the TFTP root.
dnsmasq.service
| Tag | Status | Progress | Bytes | Action |
|---|---|---|---|---|
| No fetches yet. | ||||