Minimal Router OS v0.1.4 (Beta)
Pre-releaseMinimal Router OS v0.1.4 — Beta
v0.1.4 is the first Minimal Router release built around the Golden Appliance
ISO installation model for AMD64/Proxmox.
Highlights
Golden Appliance ISO
A new release asset provides a complete router appliance:
minimalrouter-0.1.4-amd64.iso
Alpine Linux, the matching linux-lts kernel/modules/initramfs, MinimalRouter,
Dashboard and runtime dependencies are assembled before the user VM boots. The
live ISO is a small verified flasher, not a package installer.
The target flow is now:
boot ISO → verify Golden image → flash blank VM disk → reboot
→ firstboot → WAN/LAN → optional PPPoE → passwords → router services
Offline by construction
The user VM no longer depends on Alpine repositories during disk installation.
The live flasher does not run apk, setup-disk, mkinitfs, target chroots or
the MinimalRouter distribution installer.
This removes the package-repository and live-kernel/target-kernel mismatch failure
class encountered during earlier installer development.
Serial and recovery
- dedicated
MinimalRouter Installer (serial ttyS0 115200)boot entry; - firstboot can run entirely over serial;
- password-protected
ttyS0root recovery remains active after installation; - trusted-LAN OpenSSH recovery is configured with a separate root password;
- VGA/noVNC remains the production default and an independent pilot fallback.
Full install validation
The Appliance ISO workflow now tests the actual install rather than only booting
the ISO. It flashes a blank 8 GiB VirtIO disk, reboots, completes firstboot and
then proves:
- installed serial root login;
- a real password-authenticated SSH login;
- LAN
192.168.1.1/24; - trusted-LAN SSH nftables rule and listener;
- firstboot and canonical state markers;
- running kernel/module release match;
routerdservice/readiness;- Dashboard listener on
:8443.
The signed release workflow repeats this E2E test against the release ISO before
publishing it.
Signed release trust inside the ISO
The v0.1.4 release ISO is built from the already signed AMD64 release payload and
must contain firmware-signing.pub. A release build fails if that trust anchor is
missing. This keeps later A/B update verification aligned with archive installs.
Other v0.1.4 improvements
- boot-ID-based startup diagnostics with bounded history;
- lower passive runtime work and visibility-aware Dashboard polling;
- lightweight post-connect WAN estimate plus explicit full Speed Test;
- QoS-safe Speed Test restoration through canonical reconciliation;
- Smart Change Preview;
- conservative PPPoE auto-recovery;
- one-click network diagnostics and Startup Timeline;
- local recovery console and sanitized support-bundle workflow;
- build/version/commit/date reporting from release metadata;
- hardened signed A/B staging and anti-downgrade behavior.
See ../../CHANGELOG.md for the full change history.
Install on Proxmox
Use the currently qualified profile:
- AMD64/x86-64;
- SeaBIOS;
- 1 GiB RAM or more;
- one VirtIO disk of at least 8 GiB;
- two VirtIO NICs;
- noVNC available during the pilot;
- optional
serial0socket.
Verify:
sha256sum -c minimalrouter-0.1.4-amd64.iso.sha256Then attach the ISO and boot. Detailed instructions:
Release assets
The release workflow publishes:
minimalrouter-0.1.4-amd64.iso
minimalrouter-0.1.4-amd64.iso.sha256
minimalrouter-linux-amd64.tar.gz
minimalrouter-linux-arm64.tar.gz
minimalrouter-linux-amd64.manifest.json
minimalrouter-linux-arm64.manifest.json
minimalrouter-linux-amd64.spdx.json
minimalrouter-linux-arm64.spdx.json
SHA256SUMS
The ISO, archives/SBOMs, manifests and checksums receive the corresponding GitHub
attestations defined by the release workflow.
Current qualification boundary
This remains a Beta controlled-pilot release.
The complete installed-disk E2E target for v0.1.4 is SeaBIOS + MBR/ExtLinux +
VirtIO. The installer media retains UEFI boot metadata, but an installed UEFI
Golden target is not yet qualified.
Automated QEMU validation also does not replace real ISP PPPoE, physical NIC,
external scan, thermal, abrupt-power or long-duration testing. Keep a known-good
router available during the first real-WAN pilot.