aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-10-17 10:11:12 +0200
committerChristophe Besson <cbesson@gmail.com>2026-10-17 10:11:24 +0200
commita1d18a2957d167444c6fc6c2e4ec8628509a7009 (patch)
treea6c32d665854ff27c09bd630fea7f63f2f103cf1 /docs
parent4f6189753d836e219e6ac8c421e93c766b06e52f (diff)
downloadmeshbay-a1d18a2957d167444c6fc6c2e4ec8628509a7009.tar.gz
docs: open items found with the local network refusal
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/MESHBAY_DESIGN.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index 6fe0722e..dc9cde9c 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -4803,6 +4803,9 @@ process runs it — `systemctl --user` on Linux, Task Scheduler on Windows.
| **A failed download leaves its in-flight chunks rejecting unhandled** | When `pipelinedDownload` throws, the other promises of its window are abandoned and each prints "Uncaught (in promise)" in the console. Noise, but in the log a dropped connection is read from |
| **A queued transfer logs "no answer" every minute** | The lease watchdog re-asks after 60 s of silence whatever the last answer was, so a lease the node has answered `queued` and that has not moved prints "no answer for transfer ... asking again" once a minute for as long as it waits, which reads as a fault |
| **"Prune stale entries" does not touch the index** | The Node page's maintenance button runs `prune_index_cache`, which drops rows of the hash cache and nothing else. An operator who sees a deleted file still listed reaches for it, and nothing changes: only the reconcile removes an index entry, and nothing lets the operator ask for one |
+| **The node logs `host: none` for every answer** | `webrtc_server.py` counts host candidates by `" typ host "` with a space after it, and aiortc ends those lines at `typ host`. Every answer in ten days of the test node's log read `host: none`, and it is the first thing read when a member reports "DataChannel closed": it sent the 2026-10-16 diagnosis the wrong way. A one-line fix and a test |
+| **Only the group page explains a refused local network** | `transport.js` names it (`local_network_blocked`, Android 17 and Chrome 155), and `group-page.js` says what to change. Search and the other screens that open a connection show it as a node that cannot be reached |
+| **A reconnect refused the local network says nothing** | A phone connected on mobile data that walks onto the node's Wi-Fi without the permission loses the connection when Android drops mobile data, and `_reconnectLoop` retries with the reason in the console and nowhere else |
---