mrambossekandClaude Opus 5
cfa58e8d60
The probe counted any well-formed packet from the server as "the server answers", checking only the transaction id and a minimum length. REFUSED and SERVFAIL are well-formed packets. So a server actively refusing this client would have been reported as healthy, and the finding — whose whole output is "the network is fine, your device is not" — would have pointed confidently at the wrong component. It now requires rcode 0 and at least one record, and reports a refusal as what it is: a working server saying no, which points back at the network. The rcode is named rather than numbered, because "REFUSED" is a fact an operator can act on and "rcode 5" is a lookup. Caught by decoding what fmr's router actually replied — ab cd 81 80 00 01 00 02, NOERROR with two answers — after realising the earlier check only counted bytes. The reply was genuinely good, so the finding on the tablet stands; the check was wrong regardless. The advice is broader too. That tablet's fault survived a reboot, which makes "toggle wifi and it clears" wrong as a flat claim: it now says what to look at when a restart does not fix it — something on the device filtering DNS, or a per-client rule on the router. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Echolot
Free software for detecting and debugging local network issues from an Android phone — built for people who actually know what a neighbor table is.
Most "wifi analyzer" apps show you signal bars. Echolot aims at the layer where home and office networks actually break: duplicate DHCP servers, broken IPv6 RAs, MTU black holes, NAT64 weirdness, multicast that dies at the AP, DNS that answers differently than it should. It records what it observed, separates observation from interpretation, and exports the whole run so you can argue with it later.
Status: pre-release. The capability prober runs on real hardware; the production app and the probe server are not built yet.
Repository layout
docs/ design docs — the contract for everything below
echolot-prober/ capability prober: validates the no-root feasibility matrix on real devices
The Go probe server and the production app land here as siblings.
Design docs
The three specs are draft-complete and reviewed; treat them as the contract.
| Doc | What it defines |
|---|---|
| docs/feature-catalog-and-feasibility.md | Full feature list + the no-root feasibility matrix |
| docs/measurement-schema.md | Archived/exportable measurement JSON (observation vs finding, two-clock rule, anonymization) |
| docs/probe-protocol.md | Client↔server wire protocol (pinned TLS control plane, binary UDP data plane, STUN, canary DNS) |
| docs/build-status.md | Running log of decisions and next steps |
Privilege tiers
Every result records which tier produced it:
app— no root, no special setup. The bulk of the functionality.shizuku— ADB-shell privileges via wireless pairing, no root. Shipped in v1.root— future optional module.
Licensing
| Part | License | Why |
|---|---|---|
| All code (app, prober, server) | GPL-3.0-or-later | The value here is the platform-API research; copyleft keeps derivative apps free |
docs/ (the specs) |
CC-BY-4.0 | A wire protocol and a measurement format should be implementable by anyone, without license anxiety |
Full texts: LICENSE (GPLv3) and docs/LICENSE (CC BY 4.0).
Sources carry SPDX-License-Identifier headers.
If you want to build a compatible server or client, the protocol and schema docs are deliberately permissive — go ahead.
Building
See echolot-prober/README.md. Short version, from echolot-prober/:
echo "sdk.dir=/path/to/Android/sdk" > local.properties
./gradlew :app:assembleDebug