{% extends "ui/_layout.html" %} {% block title %}Settings - bty-web{% endblock %} {% block content %}
bty-web is gated by the OS password of the
{{ service_user }} account. To rotate the credential,
run sudo passwd {{ service_user }} on the server.
Sessions are server-signed cookies (Starlette's
SessionMiddleware) with a sliding 7-day TTL. To
invalidate every existing session in one shot, rotate the
session secret with
sudo rm /var/lib/bty/session-secret && sudo systemctl
restart bty-web and reboot once.
Activates the dnsmasq proxy-DHCP block: bty-web responds to PXE
queries on the chosen interface. Pick the interface that faces the
target machines, supply the subnet they're on, and click Activate.
dnsmasq restarts; until then the dnsmasq config shipped
with the appliance only serves TFTP.
{{ pxe.interface }}, subnet
{{ pxe.subnet }}.
{{ pxe.interface }} but that interface is
not currently present. ``dnsmasq`` is
failing to bind. Deactivate and re-activate on a present
interface below.
boot_policy=flash won't actually be served until you
activate it here.
Proxy-DHCP only: bty assumes there is already a DHCP server on this segment. Full DHCP is intentionally not offered here - misconfigured rogue-DHCP would conflict with the LAN's real DHCP server. Run a dedicated DHCP daemon next to bty if you need one.