Repository navigation
[feat] Move the relay to upstream 0.4.2 and report port-unstable - #13
Merged
Merged
Conversation
The status and members pages now read "Mirall Relay" instead of the package id. Upstream's v0.4.1 tag moved to carry it; the package version is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Pins the submodule to v0.4.2. Internet Reachability now fails on state "port-unstable" (outbound port rewritten) instead of reading green, and shows loading for up to 10 minutes while the relay re-learns its address after an IP change. Test Reachability explains each state and shows the address seen from outside. Docs cover the three setups, limitation 12 and a fault-injection recipe. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
StartOS installs the relay with public addresses off, and the firewalled message and instructions only said to forward the port. Both now name the Public address switch. A router address is enabled per literal IP, so it drops at every ISP IP change: StartTunnel is now the recommended home setup, and a router forward only for a static IP. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Upstream 0.4.2 (ok/mirall-relay#22) stops reporting a relay as reachable when hyperdht cannot offer clients a direct connection:
/readyznow carriesstate(reachable,firewalled,port-unstable,unknown, …) and returns 200 only forreachable. Until now Internet Reachability stayed green while the relay's outbound port was rewritten and members could not connect (the 2026-09-21 incident).What
v0.4.2. Re-checked thestartos/utils.tsassumptions against it (uid, node path,keys.jsexports, admin token file, members path, env names): all hold;/readyzand/status.jsonshapes updated inReadyzBody/StatusReachabilityand UPDATING.md.port-unstable; shows loading for up to 10 min onunknown(address re-learning after an IP change), then fails. Falls back to the oldfirewalled-only logic whenstateis absent.0.4.2:0release notes in all five locales; new strings translated.97738e8(operator-page title fix, previously unpushed).Verified
npm run checkand prettier clean;makebuilds both arches (x86_64 manifest0.4.2:0). Note: on this MacmakeneedsBUILDX_BUILDER=<a docker-container builder>while Docker Desktop's containerd image store is off.wg0)/readyz200reachableat178.105.135.38:49737within 13 s, and the monitor's member probe bridged (2 sessions, 1 pairing, 68 KB).🤖 Generated with Claude Code