Wardriving rig
Every Wi-Fi network and Bluetooth device it hears, stamped with a position, uploaded to a private map when the car gets home.
- Capture
- Kismet, a u-blox GPS puck, a Bluetooth sniffer dongle
- Screen
- 3.5 inch panel through the kernel framebuffer driver
- Trigger
- Leave home and it records. Come home and it publishes.
- Summaries
- Written on a separate Pi so they never fight the radio work
It starts on position, not on a button
Nobody remembers to press record, so it watches position instead. It waits for a satellite fix before starting, because the Wi-Fi adapter's own interference makes a fix much harder to get. That costs about a mile at the beginning of every drive.
Three things that need specific handling
The touchscreen does not work through the generic interface. It needs the kernel driver for that controller and a vendor init sequence, or chip select never asserts and the panel stays white.
Kismet's export tags Bluetooth devices as Wi-Fi, so everything is re-filtered by radio type before it reaches the map. And the GPS has to be pinned to its hardware path, or the Bluetooth dongle takes its device name on the next boot.
Pointing it at a target
The second function is aiming the rig at a specific, pre-authorized network to show that a weakness is real. The authorization layer is strict by design: explicit targets with expiry dates, dry-run by default, and it refuses anything out of scope.
The effector is a second board running modified firmware. It needed a new build target, because the prebuilt image sends its console to a port this board does not have, so it flashes fine and then appears dead. That work is an open pull request upstream.