// the take
Firmware for a dedicated wardriving device built on the ESP32-C5, logging 2.4GHz, 5GHz, and BLE networks to SD in WiGLE format with GPS tagging. It's for people who already wardrive and want a purpose-built handheld instead of a laptop-and-dongle setup, with enough configuration depth (geofencing, SSID exclusions, multi-node collection) to appeal to the WiGLE leaderboard crowd specifically.
5GHz wardriving is genuinely uncommon — most wardriving tools and dongles are 2.4GHz-only, so doing dual-band on a single ESP32-C5 is a real capability most competing projects don't have. The Node/Core architecture for fanning out multiple collection devices to one GPS+SD unit is a sensible way to scale physical coverage without duplicating GPS/SD hardware on every unit. The browser-based Web Serial installer plus automatic SD-card `.bin` update fallback covers both the easy path and the no-laptop-in-the-field path well. Dock mode (auto-detect a trigger SSID, upload pending logs, resume scanning) removes the manual pull-data-off-SD step that kills a lot of similar DIY projects' usability.
The admin AP ships with identical default SSID and password (`c5wardriver`/`c5wardriver`) on every unit, and the web UI itself has no auth unless you explicitly set an admin password — for a device whose whole job is collecting and holding location data, that's a soft spot out of the box. Node-to-Core traffic is unencrypted by default and even encryption, when enabled, caps the mesh at 6 nodes for memory reasons, so anyone scaling up a multi-node setup is pushed back toward cleartext OTA transmission of collected data. It's tied to one specific dev board (ESP32-C5-DevKitC-1) and a matching host board/enclosure, so there's no portability to other ESP32 variants if that hardware goes away or gets hard to source. Visible test coverage is a couple of standalone test files for channel-dwell logic — there's nothing covering the harder-to-get-right runtime interactions (SD card pulled mid-write, GPS fix lost mid-geofence, Core/Node desync), which is where firmware like this tends to fail in the field.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →