Skip to content

Release notes

The current application release is The Gateway v2.19.0, released 2 November 2026 for linux/amd64 and linux/arm64.

Read the new defaults before upgrading. Settings → Privacy now separates the gateway’s own traffic from the traffic it forwards for clients:

  • /etc/resolv.conf uses the local resolver alone by default; public fallback resolvers are no longer built in. Configure up to two explicitly in Settings → DNS if needed.
  • WAN health probes the uplink’s first hop. To detect an outage beyond a still-reachable router, configure your own probe targets or explicitly enable public-resolver probes.
  • Threat feeds, release checks/downloads and Tailscale’s relay map use a tunnel. Automatic selection follows the first hop of the highest-priority enabled VPN routing policy that is up. With no eligible tunnel they wait unless direct WAN downloads are explicitly allowed; LAN, mesh and loopback release mirrors need no tunnel.
  • Feed copies survive restarts and refresh when a day old. Ghost mode suppresses external relay-map, relay-health and captive-portal checks. The release site receives a browser-style User-Agent.

Other changes:

  • Splitting: opt-in Rotate new connections only preserves open connections during slot rotation; endpoint tables are rebuilt on apply. MASQUE reconnects its proxy session, restores a tunnel that roamed off its relay and leaves chained WireGuard tunnels unwrapped.
  • Mesh: an optional, admin-only coordination-server front lets a public gateway serve another gateway’s Headscale through the federation tunnel. It is off by default and creates a public control-plane entry when enabled.
  • Telemetry: the Tailscale Inc. endpoint-blocking preset is off by default because it can break Tailscale-hosted tailnets. The installer starts tailscaled with --no-logs-no-support.
  • Servers and updates: site downloads include signed server-role files and top up older caches; Check: never is available with manual policy. Update, rollback and reconfigure jobs finish and bind the serving role before requesting artifact review.
  • Reliability: tunnel health tolerates one lost ping; bridge-down waits for three failed ticks. Fixes cover MAC restoration after driver resets, ephemeral-port/listener collisions, full backup storage, client ACLs on forwarders and log-size enforcement.

From v2.18.2, the pre-start helper has changed. Use System → Updates → Refresh them from v2.19.0, then prepare the update; the original release requires this installer-file refresh. Schema 77 adds the telemetry-preset rows. Returning to v2.18.2 requires the updater’s rollback within its confirmation window, including the database snapshot—not a plain binary swap.

After the first start, a node without a VPN routing policy must explicitly allow Download straight over the WAN while that tunnel is down, use a local release mirror, or receive an uploaded archive to obtain future releases. Review own-traffic privacy, dual-WAN probes and the update guide.

The release file set contains 22 original Gitea assets: nine gzip-compressed binaries for each of amd64 and arm64, both installers, BUILDINFO and RELEASE_NOTES.md. Website publication preserves those bytes, adds exact decompressions of gatewayd/gwctl, and signs the checksum manifest with the existing release key. Download the signed manifest, signature, build information, bootstrap, full installer and upstream notes.

The updater now checks installed service files instead of relying on an administrator’s acknowledgement:

  • It hashes the gatewayd unit and helper scripts and compares them with BUILDINFO.installer_hash. Update preparation refuses a mismatch; a node with matching files needs no refresh acknowledgement.
  • System → Updates → Refresh them from vX runs the cached release’s verified install-gateway.sh --refresh. It refreshes only the unit and helper scripts: no package installation, configuration changes or service restart. Success requires the resulting hashes to match.
  • Older cached releases recover missing metadata fields from their original BUILDINFO.
  • During the initial confirmation grace period—one tenth of the window, up to 60 seconds—external failures are logged without extending it. After that, only a previously unseen external failure extends the window. External failures still do not themselves trigger rollback.

Upgrading from v2.18.1: the unit and helper scripts are unchanged (installer_hash starts 1766f722), but this release’s original BUILDINFO still says requires_installer: true because of a known build-tool comparison error. A v2.18.1 node may ask once for the installer’s refresh acknowledgement; ensure the refresh really ran (GATEWAY_REFRESH=1). From v2.18.2 onward the updater checks the actual files by hash. The confirmation watcher is written by the version being updated from, so an update from v2.18.1 can still show the old repeated window extensions; Confirm now ends the window. See Updates and release trust.

All 22 original Gitea files are mirrored byte for byte, without rebuilding or recompressing. Raw daemon/CLI copies are exact decompressions. The original BUILDINFO, including the known flag issue, is preserved. Download the signed manifest, signature, build information, bootstrap, full installer and upstream notes.

Released 26 October 2026. The gateway and install.sh now include both release-signing public keys: primary 03ea7f6bcef4ab19 and reserve e740c848903fec85. The release cache recognizes releases signed by these keys, and the updater verifies the signed release channel, its expiry and key revocations. Automatic updates remain opt-in, require a built-in-key signature, and respect the configured delay and maintenance window.

The bootstrap refuses an unsigned or untrusted manifest. Older unsigned releases require the explicit GATEWAY_ALLOW_UNSIGNED=1 override. Newly generated BUILDINFO uses LF line endings; the original v2.18.0 file remains unchanged.

Upgrading: a gateway running v2.18.0 has no built-in keys, so upload and accept the v2.18.1 release manually in System → Updates, or run the installer. From v2.17.0, run the installer because the release requires installer changes. See Updates and release trust.

All 22 original Gitea files are mirrored byte for byte, with raw daemon/CLI copies made only by decompression and signed publication manifests. Download the signed manifest, signature, build information, bootstrap, full installer and upstream notes.

The gateway can now provision and maintain its surrounding servers over SSH, use a common release cache for server roles, and update itself from that cache.

  • Server management: admin-only and off by default; managed SSH, monitor-only and manual-script modes. Host keys are pinned and checked, and ownership markers prevent conflicting management after a restore or takeover.
  • Server roles: DERP relays, bridges, Splitting components and complete gateway nodes. Setup includes inventory, a reviewable plan, resumable job logs, recorded artifacts, integration and final checks. Updates, reinstall, rollback, file-drift checks and per-server maintenance windows are supported.
  • Updates: resumable release uploads, release cache, candidate sandbox checks, a confirmation watcher and binary/database rollback. External tunnel, WAN or peer failures extend confirmation and raise an alert rather than independently causing rollback.
  • Mesh and routing: linked self-hosted meshes through federation, DERP over TLS on port 443, and SNI/Host steering for bridges on shared CDN addresses. Fresh installations have no relay until one is configured.
  • Encrypted storage: a LUKS2 vault for backups and keys, unlocked in the web UI. Tunnel keys stay outside so VPN connectivity can start before unlocking.
  • Activity cleanup: soft wipe preserves configuration while clearing logs and activity history; medium wipe preserves the live database but destroys the vault. The dead-man timer follows admin logins and fires once per absence. See the updated threat model.
  • Chain Routing retired: use multi-hop routing policies; legacy state is cleaned up at boot.

Trust limitation: v2.18.0 contains no release-signing public keys. Releases enter its cache as unsigned and require manual administrator acceptance; auto updates accept nothing. The bootstrap checks checksums but not the manifest signature. Embedded keys are included from v2.18.1; they are not retrofitted into v2.18.0. See Updates and release trust.

The upstream release supplies 22 original files: nine binaries for each of two architectures, compressed as gzip, plus install.sh, install-gateway.sh, JSON BUILDINFO and UTF-8 RELEASE_NOTES.md. The binary names are gatewayd, gwctl, gateway-srv-agent, gateway-derp-admit, derper, bridge-node, masque-proxy, reassembler and echo-server.

Those files are mirrored byte for byte. Only gatewayd and gwctl also have raw copies, made by decompressing the original gzip archives—not by rebuilding or stripping. UPSTREAM_SHA256SUMS records every decompressed binary; SHA256SUMS covers all published files except itself and its signature. Download the signed manifest, signature, build information and upstream notes. See the download paths.

Migrations 061–076 run on the first start after v2.17.0. Server management remains off until enabled by an administrator and requires sign-in. Back up first, retain console access, and review the server-management guide and update behavior.

The upstream development record reports deployments r1–r135, 332 stage checks at the final deployment, leak tests, UI-value/action harnesses and server-role exercises on real servers and systemd containers. These are project-reported results, not a fresh production rollout or independent audit by this website publication. See release evidence.

Released 12 October 2026. Tunnels as proxies exposes a connected WireGuard or OpenVPN tunnel through SOCKS5 and HTTP on the same port. The proxy follows the tunnel’s live interface and DNS; it refuses connections when the tunnel is down, with no WAN fallback. Routing policies can select a local proxy:<id> hop. An unauthenticated proxy on every address is refused where it would become an open proxy.

Other changes include a WiFi AP watchdog for USB re-enumeration, serialized privacy toggles, proxy health/protocol fixes and the missing runtime dependencies in the installers. Migration 060 adds proxy_servers.tunnel_ref. Existing proxies listening on all addresses without authentication may need a login or a specific listen address.

The upstream reference-node report records 202 value checks / 0 failures, 290 action checks / 0 failures with six conditional/review-only skips, 22 node checks / 0 failures and 9/9 leak checks. It also reports SOCKS5, HTTP CONNECT and plain-HTTP tunnel-proxy verification from LAN and mesh clients. See VPN tunnels.

The 7 October installer maintenance added missing runtime dependencies such as OpenVPN, diagnostics tools, and a distro-supported DHCP client. The full installer added --with-bluetooth, enabled by default for rpi and full profiles. Update mode repairs missing dependencies before comparing binary versions.

That maintenance did not change the v2.16.0 binaries or checksums at the time. The later signed-release transition includes a separately authorized correction to the raw v2.16.0 daemons; older release directories remain unchanged. See installation and update behavior.

Path Purpose
/install.sh One-shot bootstrap installer. Downloads the verified binary and hands off to the full installer.
/install-gateway.sh Full profile-driven installer for rpi, vps, node, full, and custom installs.
/releases/latest/gatewayd-linux-amd64 Original amd64 daemon, decompressed from the upstream archive.
/releases/latest/gatewayd-linux-arm64 Original arm64 daemon, decompressed from the upstream archive.
/releases/latest/gatewayd-linux-{amd64,arm64}.gz Original upstream release archives; preferred by the bootstrap.
/releases/latest/gwctl-linux-{amd64,arm64}.gz Original upstream CLI archives for both architectures.
/releases/latest/BUILDINFO Upstream JSON build provenance and version.
/releases/latest/RELEASE_NOTES.md Unmodified upstream release notes.
/releases/latest/SHA256SUMS Checksums for every hosted file except the manifest and its signature.
/releases/latest/SHA256SUMS.sig Detached Ed25519 signature of the exact manifest bytes.
/releases/latest/UPSTREAM_SHA256SUMS Upstream checksums of the uncompressed original binaries.
/releases/channel.json and .sig Signed current-release channel and its expiry.
/releases/v2.10.0/ Pinned v2.10.0 archive.
/releases/v2.11.0/ Pinned v2.11.0 archive.
/releases/v2.12.0/ Pinned v2.12.0 archive.
/releases/v2.12.1/ Pinned v2.12.1 archive.
/releases/v2.13.1/ Pinned v2.13.1 archive.
/releases/v2.14.0/ Pinned v2.14.0 archive.
/releases/v2.15.0/ Pinned v2.15.0 archive.
/releases/v2.16.0/ Pinned archive; raw daemon correction is part of the signed-release transition.
/releases/v2.17.0/ Pinned tunnels-as-proxies release.
/releases/v2.18.0/ Pinned server-management release.
/releases/v2.18.1/ Pinned release with built-in signing keys.
/releases/v2.18.2/ Pinned release with installer-file verification and confirmation-window fixes.
/releases/v2.19.0/ Pinned release with own-traffic privacy defaults and new-connections-only rotation.

Released 3 October 2026. This release audits the admin interface against API data and node state, closes the project’s 55-item UI audit ledger, and adds controls for previously configuration-only settings.

  • Managed accounts: Settings → Users and gatewayd user add|list|del manage users beside the built-in admin. Deleting a user revokes its tokens; concurrent edits and reserved-name handling are fixed.
  • Static DHCP reservations: pin a MAC to an address from the DHCP page. Reserved addresses may be outside the dynamic pool; other clients cannot take them. DHCP settings now apply to the running server while retaining leases, rather than waiting for a daemon restart.
  • Restart enforcement: when reconciliation is disabled, initial device allow rules, per-class DoT blocks and chain-routing marks are still installed once at startup.
  • Privacy and WAN fixes: IPv6 block restoration no longer stacks duplicate rules or re-enables a disabled toggle. The WAN stall watchdog adds ARP handling, confirmation ping, recovery backoff and corrected cooldown accounting to avoid unnecessary interface bounces.
  • Role-aware controls: viewer writes are disabled with a reason; admin-only sections are labelled; operator access no longer blanks the application on a Secrets 403. API denial reasons remain visible.
  • More settings: static WAN address/gateway/subnet, AP subnet, WAN-side admin access, Pi-hole backend, per-interface gateway/DNS, and live reconciliation on/off and interval. Some network settings still require restart; see Settings reference.
  • Truthful status: corrected routing, WiFi, firewall, bridge and discovery counts; absent services no longer show live controls; hosts without a temperature sensor return cpu_temp: null. Audit-log paging and snapshot age are exposed.

The upstream primary-mode Raspberry Pi 4 record reports 208 value checks / 0 failures, 293 action checks / 0 failures with four review-only skips, 22 node checks / 0 failures, 9/9 leak checks, and 48/48 page sweeps for both regular and viewer roles. These are project-reported results, not an independent audit or a throughput benchmark. The embedded-mode VPS was still running v2.13.1: its read-only fixture checks passed 84 rows and failed 12 for fixes not yet deployed there. See release verification.

Original archives: daemon amd64, daemon arm64, CLI arm64. Manifests: hosted files and uncompressed upstream originals.

The Gitea archives remain unchanged. On 26 October 2026, the raw daemon downloads were corrected to be exact decompressions of those archives, replacing the former stripped compatibility builds from source commit 17b154d4. SHA256SUMS now includes UPSTREAM_SHA256SUMS and has an Ed25519 signature. This is a one-time correction; older release directories are unchanged. v2.16.0 provides an arm64 CLI archive, not an amd64 CLI archive, and does not include version-pinned installers. The root installer scripts now come from v2.19.0.

No configuration change is required. Migration 059 creates dhcp_reservations. With reconcile.disabled: true, startup now applies initial policy enforcement once: device rules, DoT blocks and chain-routing marks no longer wait for manual reconciliation. API clients must accept cpu_temp: null on hosts without a sensor. Back up the database and configuration before upgrading; changing website downloads does not upgrade any running gateway.

Released 1 October 2026. v2.15.0 adds optional weighted WAN load balancing on top of v2.14.0 failover. It is off by default: a single-uplink node or a node with balancing disabled retains the previous behaviour.

  • Enable network.wan_balance: true with wan_failover_mode: auto to install weighted multipath across healthy balancing-eligible uplinks. wans[].weight sets relative flow weight; this is not bonding or a guaranteed bandwidth ratio.
  • Set wans[].balance: false to keep a metered uplink eligible for failover but exclude it from balancing.
  • The manager installs the main default (metric 50), WAN-facing policy defaults, direct-egress grants and DNS pins together. Routine policy applies no longer flatten multipath routes.
  • A degraded leg is removed after its first failed probe; the checker runs on a five-second cadence. Primary changes still use the failover path before eligible legs are restored.
  • Interfaces → WAN Uplinks & Failover now includes balancing controls, editable per-uplink options, Save/Reset, validation warnings and installed egress state. The manager API adds egress and balanced.
  • Failback resolves the wan-failover alert. The stall watchdog follows configured uplinks every 30 seconds, without a restart for newly added interfaces.
  • Probe tables and marks remain stable per interface across priority edits. Removed uplinks leave the checker and their obsolete masquerade rules are removed.

The project’s Pi test used weights 3:1 and recorded an 8:4 spread over twelve destinations, stable across applies, 22 node checks passed / 0 failed and 9/9 leak checks. Five primary-link outages were tested under balancing; failover to a single leg was recorded at 21 seconds. These observations are not a distribution guarantee or an SLA.

Evidence limit: both test uplinks used the same router and public address. Asymmetric or independent ISPs were not exercised. Balancing remains disabled in the reference node’s normal single-WAN operation. See release verification.

Download original archives: daemon amd64, daemon arm64, CLI arm64. Manifests: hosted files and uncompressed upstream originals.

Original Gitea .gz archives are hosted unchanged and checked against the release description’s uncompressed SHA256 values. The bootstrap verifies both the downloaded archive and the decompressed original binary.

The original daemon binaries exceed the static host’s per-file size limit when uncompressed. Existing raw download URLs therefore serve separately built, stripped compatibility binaries from tag v2.15.0, commit 3d3ca09d. Their checksums differ from the original upstream binaries; use SHA256SUMS for hosted files and UPSTREAM_SHA256SUMS for decompressed originals. The upstream release supplies an arm64 gwctl archive, not an amd64 CLI archive.

The full installer is unchanged in this application release and remains byte-identical to the tag. The website bootstrap adds verified compressed downloads while retaining support for older pinned raw-binary releases.

Released 30 September 2026. This release adds priority-based WAN failover and recovery, configured through network.wans or Interfaces → WAN Uplinks & Failover.

  • Internet-reachability probes use per-uplink, device-bound TCP connections rather than relying on first-hop ICMP. Default targets are 1.1.1.1:443 and 8.8.8.8:443; per-uplink probe targets are supported.
  • A single WAN manager chooses the preferred usable uplink, with a 60-second failback hold, a 30-second minimum dwell and flap pinning after three flaps in ten minutes.
  • A shared transition updates the default route, policy uplink routes, NAT, tunnel binding, conntrack and DNS pins.
  • The UI and API expose editable uplinks, manual/automatic mode, health, active/standby state, reasons and timings.
  • Standby addressing, per-uplink firewall scopes and fail-closed handling are covered. Single-uplink nodes retain their previous behaviour.
  • Privacy-rule restoration no longer temporarily clears DoH/DoT and STUN block toggles. Other fixes cover a fail-open routing table, missing leak-monitor tunnel information and OpenVPN route-pin cleanup.

The upstream release record reports three primary-link outages on a Raspberry Pi 4: down detection in 20–22 seconds, failover in 21–24 seconds, and 22 passed / 0 failed node checks, with 9/9 leak checks, on the standby. Protected traffic and gateway DNS pause for approximately 10 seconds while tunnels rebind. These are observations from that configuration, not an SLA or an independent audit.

Not included: WAN load balancing or bonding. weight is stored but not used for distribution. The failover alert is not automatically resolved on failback, and a newly added uplink enters the stall watchdog’s watched set after a daemon restart.

The site’s binaries are stripped builds from tag v2.14.0 (source commit fd2d2ffe). Their SHA256SUMS identify these hosted builds, not the artifacts used on the project’s reference node. See Dual-WAN failover for the supported setup.

v2.13.1 is a verification-driven patch release on top of v2.13.0. Its fixes came from running the product’s own node and leak checks against live reference deployments.

The important operator-facing fixes are:

  • dns.upstream_mode now reaches the DNS plane, so configured DoT/DoH is actually applied at boot.
  • Privacy mode no longer downgrades a configured encrypted DNS upstream to cleartext.
  • Leak checks understand encrypted upstreams instead of reporting them as ISP leaks.
  • /whoami redacts API keys, bearer tokens, cookies, and proxy credentials.
  • The node verifier no longer risks disabling Pi-hole while checking role scope.
  • Automatic rollback stops the service and atomically swaps the binary, avoiding ETXTBSY false-successes.
  • Release tooling now checks the embedded UI, installer heredocs, installer embeds, shell syntax, builds, vet, and tests together.
  • Both reference nodes passed 18/18 verification checks and 9/9 leak checks.

Before upgrading a live gateway:

  1. Take a backup before replacing the binary.

  2. No configuration change is required for single-uplink or failover-only operation. For a staged rollout, start with wan_failover_mode: manual and balancing off. After checking health and proposed decisions, use auto; opt into wan_balance: true only when intended. Keep a recovery path and allow for session/DNS interruption during a move.

  3. Create a diagnostics-role API key at /root/.gateway-api-key before running scripts/verify-node.sh; without it, API-gated checks are skipped.

  4. Prefer the update mode for an already-installed node:

    Terminal window
    curl -fsSL https://thegateway.pro/install.sh | sudo env GATEWAY_UPDATE=1 bash

For the original amd64 release binary:

Terminal window
curl -fsSLO https://thegateway.pro/releases/v2.19.0/SHA256SUMS
curl -fsSLO https://thegateway.pro/releases/v2.19.0/UPSTREAM_SHA256SUMS
curl -fsSLO https://thegateway.pro/releases/v2.19.0/gatewayd-linux-amd64.gz
sha256sum --ignore-missing -c SHA256SUMS
gzip -dk gatewayd-linux-amd64.gz
sha256sum --ignore-missing -c UPSTREAM_SHA256SUMS

For arm64, substitute gatewayd-linux-arm64.gz. Download into an empty directory and require the requested file to report OK. Checksums detect corruption, not a compromised source: authenticate the manifest signature with an independently obtained release public key. See Updates and release trust. Raw daemon downloads from corrected v2.16.0 onward match the upstream-original manifest; the historical v2.15.0 and earlier compatibility builds do not.