fix(nat): honest reachability detection + v0.2.4#10
Merged
Conversation
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
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.
Ships the Moss NAT-detection fix as v0.2.4 (Moss runtime → v0.3.1).
Root cause
applyExternalObservationmarked a nodePublic + PublicReachable=truefrom a single reflexive address and skipped the inbound probe. Behind any NAT the reflexive address is just the NAT's WAN IP, so every NATed node self-reported "open" → futile direct dials → peer flapping (peer_joined/peer_left).Fix (redstone-md/moss v0.3.1, commit 987e2fd)
Publictype but leavePublicReachableto an actual inbound probe (confirmReachability).symmetric_natwhen the mapped port varies.mosh
987e2fd,moss.config.json→v0.3.1.🤖 Generated with Claude Code