mrambossekandClaude Opus 5
7eaf0c4190
v6.no_icmp_reply infers trouble from silence, which is ambiguous by construction: a firewall dropping echo requests looks the same as a network that cannot carry IPv6 at all. Two much stronger signals were already sitting unread in the link snapshot, and a test device on a Netbird tunnel surfaced both at once. v6.route_without_address — a ::/0 route with no global address. The router advertises itself as an IPv6 gateway while SLAAC produces nothing usable. Hosts believe IPv6 is available and pay a connection timeout on every dual-stack destination before falling back, which is felt as general slowness with no packet loss to explain it. v6.no_default_route — the mirror: a global address with nothing to route it. A VPN installing host routes to specific destinations produces this deliberately and it works, so a VPN transport reports it as INFO rather than as a fault; without one it means the network handed out an address it does not carry traffic for. Both are read from the routing table, so neither is inferred from silence, and both are reported per interface — "IPv6 is broken" is useless advice when wifi is the broken one and cellular is fine. Classification lives in core-measurement rather than the ViewModel so it can be tested without a device; the fixtures are a real dumpsys table (wifi advertising a route it cannot source from, working cellular, a tunnel with two host routes) because the risk here is not bad boolean logic but imagining shapes real networks do not produce. 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