Changelog
Highlights of the current firmware release. Previous versions remain in the release archive.
[3.0.29] - 2026-11-19
Fixed
- A USB SIM stick on the same network as the home LAN (for example a stick that always uses 192.168.1.x, like many home routers) no longer cuts the gateway off from the home devices. Before, traffic for the home network could leave through the stick: device checks, LAN → Tailnet access and subnet routing stopped working, and with the stick as the main uplink the home router's DNS could not be reached, so names did not resolve and Tailscale kept disconnecting and reconnecting. Home addresses now go through Wi-Fi or Ethernet; only the stick's own addresses (and its gateway while the stick carries the Internet traffic) go to the stick. Diagnostics → Route lookup shows the reason.
- With mobile data as the main uplink, name lookups use it too. A DNS server of the home network (learned from Wi-Fi) is replaced by the stick's while the stick carries the Internet traffic, and comes back when Wi-Fi or Ethernet does. A DNS server you chose outside the home network (for example 1.1.1.1) is kept.
- System → About and the update page link the RecoveryGateway repository, and the release-notes link is shown again for its releases.
[3.0.28] - 2026-11-19
Changed
- New name: RecoveryGateway (formerly ESP32 Tailnet Gateway). Same firmware, same settings: nothing to reconfigure. The web interface, Home Assistant device, notifications, logo, covers, website and release files carry the new name. The first-boot Wi-Fi of a new device is now
RecoveryGateway-Setup-XXXX. - New addresses: the repository is now
Mattboxx/RecoveryGatewayand the website moved with it. Old website links open the same page at the new address. - The updater looks for releases in
Mattboxx/RecoveryGatewayfirst. Gateways on 3.0.27 or older still look under the old name, where a redirect repository keeps this 3.0.28 release for them: check for updates, install 3.0.28, and later updates come from the new repository.
Website
- A "Which board?" button (a chip icon in the header on computers, buttons on the home, install and getting-started pages) leads to the tested boards.
[3.0.27] - 2026-11-18
Fixed
- Key expiry times with a time zone offset or a late year (possible with some control servers, for example "+01:00") are read correctly; before, one such device made the gateway refuse the whole device list and block the tunnel, like the 64-bit ID issue fixed in 3.0.26. Malformed times are still refused. The gateway's own key expiry shown on the Tailscale page also honours the offset.
- The user ID of the registration is read exactly (shown in the log).