RecoveryGateway

Features

Choose what you want the ESP32-S3 to do. Each card leads to the relevant guide.

Connect a device to one Tailnet service

Point a LAN device at the ESP32's address and port. A TCP or UDP rule forwards it to a selected service, such as MQTT or a NAS dashboard.

Set up the Service Gateway

Reach your LAN or connect IoT devices

Advertise a subnet to reach it from the tailnet, or put devices on the gateway's Wi-Fi to give them access without a VPN client. Exit node and local firewall controls are available.

Compare network modes

Wake a NAS or PC

Save up to 12 devices, send Wake-on-LAN and verify whether a host or service responds. Use Telegram or ntfy with Tailscale disabled. The gateway can run while your NAS or automation server is off.

Configure remote recovery

Get alerts and automate

Use Home Assistant via MQTT, receive alerts through Telegram, email or ntfy, or query read-only SNMP. Power-return alerts can trigger Home Assistant automations.

Choose an integration

See what happened

Check live traffic, record events and chart resource trends. Test service reachability or export diagnostics for troubleshooting.

See the monitoring interface

Set up, back up and update

Pair and configure the board through the first-boot wizard. Use settings backups and the Web UI updater to manage an existing gateway.

Start with a new board · Update a gateway

Capabilities and defaults

CapabilityUseful whenDefault
Event historyYou want to know what happened while you were away: starts and power losses, crashes, updates, Wi-Fi and tailnet drops, failed admin logins, settings copies. Kept in the gateway's flash across restarts.Off
Trends with a chartYou want to see how memory, uplink traffic, Wi-Fi signal, CPU load and online peers behave over time: 6 hours at one-minute detail, about 45 days in summary.Off
Settings copiesAn update or a wrong change must be reversible: up to three copies of every setting, by hand or automatically before each update; restore needs the admin password.Off
Tailnet names for local devicesDevices without Tailscale on the gateway's Wi-Fi or your home LAN should reach peers by name (nas, nas.your-tailnet.ts.net). A name is not access: rules and policies still apply.Off
Telegram and email notificationsYou want problems or every event on your phone or in your inbox. Email over TLS (465) or STARTTLS (587) with verified certificates; passwords are never sent without TLS.Off
Throughput testYou need to know whether the link is fast enough: the gateway downloads from a URL (a NAS through the tailnet, or the internet), or the browser downloads from the gateway.On request
Cellular uplink (experimental)A site has no usable Wi-Fi: a UART modem with a SIM as primary or failover uplink. Not yet tested with a real modem.Off
One image, every languageEnglish, Italiano, Español, 简体中文, Français and Deutsch in the same firmware, plus the W5500 Ethernet driver (experimental, off until configured).—

Disabled optional features do not run their background jobs; their compiled code and static state still occupy space. Runs on ESP32-S3 N8R8 and N16R8: see supported boards.

Network gateway

CapabilityWhat it doesDefault
Selective Service GatewayUp to 8 TCP/UDP rules from a LAN listen port to one Tailnet IPv4 destination (literal or MagicDNS name), each with a mandatory source CIDR, binding token and optional expiry.Rules start disabled
Subnet routerAdvertise the uplink LAN and/or the AP subnet to the tailnet; optional source NAT; optional 4via6 for overlapping IPv4 sites.Off
AP gatewayOwn WiFi access point with DHCP reservations, MAC denylist, cached DNS forwarder, NAT and AP-side port forwarding.Recovery-only AP
Exit nodeSend AP traffic through a Tailnet exit node (fails closed), or advertise the ESP32 itself as an IPv4 exit node.Off
FirewallFour first-match chains with hit counters; Tailnet authorization on original packets before NAT.Allow when empty

Recovery and device management

Monitoring and diagnostics

Configuration and management

Automation and integrations

Optional possible-blackout MQTT events and Home Assistant Discovery support power-return automations, with per-boot identity, duplicate suppression and retained diagnostics for catch-up. Software restarts and brief network disconnects do not produce this event.

MQTT with Home Assistant Discovery, ntfy alerts and commands, Telegram and email (SMTP) notifications, read-only SNMP v1/v2c. Each is supervised and off by default; none can block routing or local administration. See Automation.

Support Mattboxx Edition

Enjoying the gateway? Choose where to leave a tip or support its development.

GitHub SponsorsSupport via GitHub Ko-fiLeave a tip on Ko-fi

Entirely optional. The firmware and all features stay free. Payments are handled on your chosen provider's website.