Repository navigation
Firmware v3.0.26 — fix for tunnels blocked by new devices, Headscale with a private CA, profiles for every goal
Firmware v3.0.26 — fix for tunnels blocked by new devices, Headscale with a private CA, profiles for every goal
Fixed
- Tunnel blocked in tailnets with recently added devices. The log showed
"Authorization/peer update needs a full refresh; tunnel data blocked
(stage=policy reason=peer-id ...)". Tailscale device IDs are 64-bit numbers;
devices added recently have IDs larger than the gateway's JSON reader could
hold exactly, so the gateway refused the whole device list and blocked the
tunnel. IDs are now read exactly, also in device updates and removals.
Added
- Headscale with a private CA or a self-signed certificate: a Login
server certificate field on the Tailscale page, trusted only for the login
server and its relays, from the next restart (the server name is still
checked; updates, MQTT and notifications keep public certificates only). - First connection without working DNS: the Tailscale control server is
found through a Tailscale relay at a built-in address, as the official
client does. - ACL rules with "cap:" sources admit the devices that hold that
capability. - Two relays to other regions at once for devices without a direct path.
- LAN → Tailnet: up to 5 allowed devices per rule, and a guide to share
one of your services with another network:docs/SERVICE-GATEWAY.md. - Configuration profiles for every first-boot goal (System → General):
two new ones (LAN → Tailnet services, Home Assistant), in the setup's
order, the goals chosen at first boot marked "chosen at setup", guided
steps for everything added since 3.0. Profiles never open access, change
routes or send data by themselves. - Date and time in the pre-crash log.
Still open: IPv6 inside the tailnet (use a device's 100.x address) and very
large tailnets above about 250-500 devices.
Install: web installer, Easy Install package, or OTA (System → Updates).
Verify the files against SHA256SUMS.txt.