mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-09-27 02:48:01 +00:00
Kaj SchittecatandClaude Opus 5
6d7ef3ff1f
Two reports of remote management, telemetry and ping all failing against a repeater or room server while the same operations work from other MeshCore clients, with no error anywhere: "Logging in..." disappears and nothing happens. Multi-byte path hashing fails exactly like that. sendFloodScoped() stamps path_hash_mode + 1 bytes of repeater hash onto unicast floods, which is the login / status / telemetry / ack path specifically, while channel traffic takes a different overload. A repeater that predates the feature, or does not implement it, drops 2- and 3-byte-hash packets SILENTLY, so the request never arrives and nothing on either side reports a failure. randelreiss said outright he is running 3-byte hashes (#280). It defaults to 1 byte and is opt-in, so this is behaving as designed. What is not reasonable is that someone who turned it on has no way to connect that choice to "remote management stopped working" weeks later. The timeout already had the operator's attention and was spending it on password, server and clock; it now names the path-hash setting and where to change it when the setting is not on its default. Does not change any send behaviour. This is diagnosis, not a fix for the drop itself, and it is deliberately worded as a thing to try rather than a verdict: neither reporter has confirmed the cause yet. All 8 S3 boards build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>