Skip to content

fix(nat): honest reachability detection + v0.2.4 #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ForeverInLaw merged 3 commits into from
Jun 3, 2026
Merged

fix(nat): honest reachability detection + v0.2.4 #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
43807a6
chore(moss): bump runtime to v0.3.1 (honest NAT reachability detection)
ForeverInLaw Jun 3, 2026
38c17dd
chore(release): v0.2.4
ForeverInLaw Jun 3, 2026
546684d
chore(moss): re-pin to v0.3.1 with changelog (e0c14eb)
ForeverInLaw Jun 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,21 @@ All notable changes to Mosh are documented here. Format follows
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.2.4] - 2026-06-03

### Fixed
- **Honest NAT reachability detection (peer flapping).** A node behind NAT was
classified as publicly reachable ("open") from a single reflexive address —
which is only the NAT's WAN IP — so peers kept attempting futile direct dials
and the connection flapped (rapid `peer_joined`/`peer_left`). The Moss runtime
(bumped to v0.3.1) now leaves reachability to an actual inbound probe and
detects symmetric NAT from varying mapped ports.

### Note
- Two peers both behind symmetric NAT still require a relay/supernode to
connect; correct detection lets Moss pick relay paths instead of looping on
direct dials.

## [0.2.3] - 2026-06-03

### Fixed
Expand Down
2 changes: 1 addition & 1 deletion moss
Open in desktop
Submodule moss updated 3 files
+13 −0 CHANGELOG.md
+8 −8 internal/mesh/node_reachability.go
+49 −1 internal/mesh/reachability_test.go
2 changes: 1 addition & 1 deletion moss.config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"moss": {
"repository": "redstone-md/moss",
"version": "v0.3.0"
"version": "v0.3.1"
}
}
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "mosh",
"private": true,
"version": "0.2.3",
"version": "0.2.4",
"type": "module",
"scripts": {
"dev": "vite",
Expand Down
2 changes: 1 addition & 1 deletion src-tauri/Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion src-tauri/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "mosh"
version = "0.2.3"
version = "0.2.4"
description = "Desktop-first decentralized messenger"
authors = ["Mosh contributors"]
edition = "2021"
Expand Down
2 changes: 1 addition & 1 deletion src-tauri/tauri.conf.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"$schema": "https://schema.tauri.app/config/2",
"productName": "Mosh",
"version": "0.2.3",
"version": "0.2.4",
"identifier": "app.mosh.desktop",
"build": {
"beforeDevCommand": "npm run moss:prepare && npm run dev",
Expand Down
Loading