Skip to content

v1.4.1 — Firewall guidance for console & exit nodes

Choose a tag to compare

@garyhooi garyhooi released this 13 Nov 07:00
· 11 commits to main since this release

Documentation and landing update

This release is documentation-only — no API, database, or console behaviour changed.

  • README firewall matrix clarified. The console-host table now says port 53 is console-only, and a dedicated Exit node ports table documents what a node actually needs:
    • 51820/udp inbound (or the custom WireGuard port) for peers
    • 443/tcp outbound for the agent's console polling
    • 53/udp+tcp outbound only when peers use the console's AdGuard resolver
    • 22/tcp inbound for the one-time install only
  • Exit nodes do not need inbound 80/443. Cloud-firewall guidance now distinguishes console-host rules from node rules and calls out node egress on 443.
  • New landing Firewall section at /#firewall, with console-host and exit-node port cards, inbound/outbound/internal labels, the private 3000/tcp warning, and cloud-firewall guidance.
  • Navigation: Firewall added to the header/mobile navigation and footer.

Upgrade notes

  • No migrations, configuration changes, or restarts are required for the application itself.
  • If you self-host the landing site, redeploy it to publish the new /#firewall section.

Verification

  • landing: tsc --noEmit clean.
  • landing: next build clean (10/10 static pages generated).
  • README and landing content reviewed for consistent console-host vs exit-node port guidance.