Skip to content

Firmware v3.0.26-beta.2 — fix for tunnels blocked by new devices, Headscale with a private CA

Pre-release
Pre-release

Choose a tag to compare

@Mattboxx Mattboxx released this 18 Nov 19:51

Firmware v3.0.26-beta.2 — fix for tunnels blocked by new devices, Headscale with a private CA, first connection without DNS

Beta for testing. It builds on 3.0.25 (the current stable release) and
extends what the gateway can reach in a tailnet. New behaviour that could
change your setup is off by default or only used when you set it.

Tailnet

  • 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.
    This affects 3.0.25 and earlier.
  • Headscale with a private CA or a self-signed certificate. The Tailscale
    page has a Login server certificate field: paste the CA (or the server
    certificate) as PEM text. It is trusted only for the login server and its
    relays, from the next restart and only while a login server is set. The
    server name and validity are still checked; firmware updates, MQTT and
    notifications keep using public certificates only. Saving or removing it
    needs the admin password.
  • First connection without working DNS. When the Tailscale control
    server's name cannot be resolved and no working address is known yet, the
    gateway asks a Tailscale relay at a built-in address for it over a verified
    TLS connection, as the official client does. The address is kept in memory
    only, and the server is still verified by its certificate and key.
  • ACL rules with "cap:" sources work. Such a rule now admits the devices
    that hold that capability (from their tailnet addresses), instead of nobody.
  • Two relays to other regions at once. Devices homed on two different
    relay regions, both without a direct path, are reachable at the same time
    (one extra relay before). Each extra relay opens only when needed and closes
    after a minute without traffic.

LAN → Tailnet

  • Up to 5 allowed devices per rule ("192.168.1.20, 192.168.1.30"), next to
    one device or a whole subnet.
  • New guide: share one service with another network. A gateway placed in
    a friend's home, joined to your tailnet with a tagged key, lets a few of
    their devices use one of your services (one address and port) and nothing
    else: your tailnet ACL limits what the gateway reaches, the rule limits who
    may use it. See docs/SERVICE-GATEWAY.md.

Other

  • The pre-crash log shows date and time for the lines of the crashed run
    when that run had the clock; the crash header no longer shows the time twice.
  • The optional UDP helpers of the VPN library call the network stack from its
    own thread, and a full network queue can no longer use up the zero-copy send
    slots.

Still open (docs/TAILNET-ACCESS-AUDIT.md): IPv6 inside the tailnet (use a
device's 100.x address) and very large tailnets above about 250-500 devices.

Install: web installer or OTA (System → Updates with "Include beta /
pre-release updates" on). Verify firmware.bin against SHA256SUMS.txt.