Skip to content

Firmware v3.0.25-beta.24 — Tailnet access fixes, simpler LAN → Tailnet tab

Pre-release
Pre-release

Choose a tag to compare

@Mattboxx Mattboxx released this 18 Nov 10:02

Firmware v3.0.25-beta.24 — Tailnet access fixes, simpler LAN → Tailnet tab

Beta for testing. It contains the Tailnet fixes found after a user's
report on 3.0.24 (official Tailscale, 18 devices, "invalid key"), a review of
the whole Tailnet path for other cases where access could fail, and a
redesigned LAN → Tailnet tab. USB modems and adapters (since beta.5) are still
untested with real devices; please report your board and device. New
behaviour that could change your setup is off by default.

Tailnet: cases where the gateway could not be used

  • Single-use auth keys no longer take the gateway offline. The default key
    in the Tailscale admin console is single-use; the gateway sent it again at
    every reconnect and restart, the control server refused it, and the device
    stayed offline with "invalid key". The key is now used only to log in, as the
    official client does. A refused key is retried once without it; a device
    deleted in the console stops with "enter a new auth key".
  • No 16-peer limit. A tailnet with more than 16 other devices (stale ones
    count) was refused as a whole and every tunnel was blocked. Maps, policy and
    peer table are sized by the tailnet (host tests with 300 and 2000 peers). 20
    tunnel slots are in use at a time; when they are full, a peer that needs one
    takes the slot of an offline or idle peer, and a peer that reaches out gets
    one at once.
  • A gateway alone in its tailnet (or the first device) works: the first
    map without peers was treated as incomplete and blocked the tunnel.
  • ACL rules with "cap:" sources no longer block all traffic.
  • No limit on ACL rules (was 128 expanded rules); every advertised subnet
    of a peer is reachable
    (was its own address plus one route).
  • Networks that block port 80 use TLS on port 443, as the official client.
  • Networks that block NTP: the clock is taken from the control server.
  • DNS failures: the last working address of the control server is used
    (also for Headscale and HTTPS login servers), and relay nodes are reached by
    the address in the DERP map.
  • Peers homed on another relay region are reachable from the gateway even
    without a direct path: when the home relay reports a peer missing, the
    gateway opens one more relay connection to that peer's region (closed after
    60 s idle), as the official client does.
  • Expired node key: shown with a warning 14 days ahead; entering a valid
    auth key renews it for the same device, without a reset. The expired state
    no longer loops.
  • Peer key renewal applies at once, without a full refresh.
  • Headscale: a server that got a new key is picked up without restarting
    the gateway.
  • Auth keys pasted with spaces or line breaks are accepted; a registered
    gateway starts without a saved auth key.

Easier to understand

  • The Tailscale page says why the gateway is not connected (key refused or
    needed, waiting for approval, key expired), shows Tailnet Lock with the
    command to sign this gateway, messages from the control server, peers and
    tunnels in use, and why the control server refused a connection (client
    version, wrong URL or proxy, access refused, rate limit, server error).
  • LAN → Tailnet tab redesigned. Three steps explain what a rule does. Each
    rule shows on one line whether it has a time limit and when it closes, with
    one choice: "Stays open: No time limit, 15 minutes, 1 hour, 8 hours, 1 day,
    7 days", applied with Save. Before, the timer lived in a separate section,
    and after it had been used once, every new or edited rule silently stopped
    forwarding until confirmed there. A rule closed by its time limit now says
    so. One LAN device can be entered as a plain address.

Other

  • Far fewer flash writes: the peer cache was rewritten (about 7.7 KB) for every
    peer at every reconnect; now only when a peer changes.
  • The control and relay connections accept the protocol upgrade only on a real
    "101" status.

Open limitations are listed in docs/TAILNET-ACCESS-AUDIT.md (very large
tailnets above about 250-500 devices, IPv6 inside the tailnet, private-CA
certificates for HTTPS login servers).

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