Network

The Network page (sidebar → Network) displays each network interface that Stranola has been detected on the host and lets you configure how each one starts up one to clients — DHCP and PXE/iPXE — either by interface or from a shared global template.

Interface Cards

Each interface has its own card: interface name, address MAC, a link status indicator (link detected / no link), and its Detected IP address (or the full CIDR when the subnet is known). A The description field can be edited online by hovering the mouse over the card and clicking the small pencil icon that appears — useful to label interfaces by classroom, rack, or switch when a server has several NICs.

Each card also has a Services switch—the control checks whether any network service is running on that interface at absolute. Disabling it disables DHCP and the PXE setting for that interface without Import your individual settings below.

There are two buttons at the top of the page: a refresh icon to "Rescan for interfaces," and a gear icon that opens the global network configuration — the shared template described above below.

Global Settings vs. Per-Interface Settings

This is the only thing you need to understand before playing either one modes: all services that can be run via an interface (DHCP, PXE…) are configured using the same three-state switch:

Status	Meaning
Global (inherited)	This interface uses whatever is set in the global configuration.
Disabled	The service is disabled on this interface, regardless of what the global template says.
Enabled	The service runs on this interface with its own configuration under the switch, ignoring the global template.

New interfaces always start in the Global state. This allows you to set reasonable default values once (in the global modal) and so that all interfaces automatically follow them, while still being able to make a one-time exception for a specific interface (a DHCP range different for the NIC of a second classroom, for example) without changing anything else.

The global settings modal (gear icon in the header of the page) and the interface-based modal (gear icon on each (card) display exactly the same tabs and fields — the difference It's just a matter of what they apply to: an interface, or the template that each one inherits from interface in "Global" state.

DHCP

• Enable DHCP — master switch for this tab (three states) in the modal via the interface, as shown above).
• DHCP Mode — Proxy PXE (recommended: Stranola responds only to specific PXE options, coexisting with an existing DHCP server on the network) or Full DHCP Server (Stranola assigns the addresses (IP itself).
• Concession Term(s), Domain, NTP (address of the (DHCP server assigned to clients).
• Allow unknown MACs — if clients with Stranola have not yet know whether or not they receive an address.
• Dynamic Range (server mode only) — Start/end IP addresses of the pool which distributes Stranola.
• Additional DHCP Options (JSON) — Raw vendor/class DHCP options for advanced settings.

PXE

• Enable PXE — Master Switch for BIOS Network Boot classic.
• Enable iPXE — defaults to PXE; enables iPXE chainloading and the URL of your script.
• Enable SecureBoot — serves the signed chain shim→GRUB→kernel to the UEFI x64 clients so they can boot with Secure Boot enabled, without change the BIOS settings.
• Boot Files — the BIOS boot file (e.g., undionly.kpxe) and the UEFI x64 file (e.g., ipxe.efi, relevant only (with iPXE enabled).
• Servers and URLs — the address of the TFTP next-server, the HTTP URL the platform from which customers obtain resources, and the URL of the iPXE boot script.
• Advanced — the directory containing resources PXE on disk and any extra kernel command-line argument passed to all clients who start up through this interface.

How does this fit in?

The first step is to ensure that DHCP and PXE are properly configured on an interface practical aspect of any deployment — see First Deployment for a path that forms a network, creates a recipe, and adds nodes to from beginning to end.