Scout Lite ESP32-C5 dual-band 5 GHz Wi-Fi 6 wardriver for Flipper Zero

Can Flipper Zero Really Wardrive on 5 GHz? ESP32-C5 vs S3/C6 (2026)

PINGEQUA Lab · ESP32-C5 Wardriving · 8 min read · Updated 2026-08-03

Can Flipper Zero wardrive on 5 GHz? The honest answer depends entirely on which ESP32 chip is soldered to the board you're using — not on which firmware you flash. Here's what the ESP32-C5 actually changes, and how far along 5 GHz wardriving really is as of mid-2026.

Quick answer Yes — but only on boards built around Espressif's ESP32-C5 chip. Every other ESP32 that Flipper Zero add-ons use — the original ESP32, S2, S3, C3, and C6 — is 2.4 GHz only at the silicon level, so no firmware, including ESP32 Marauder, can add a 5 GHz radio that isn't there. ESP32-C5 boards like the Scout Lite ship with the dual-band hardware that can, though 5 GHz wardriving itself is still an early, maturing feature.

Why classic ESP32 can't see 5 GHz

The Wi-Fi radio on a chip is fixed in silicon. A 2.4 GHz-only RF front end cannot be reprogrammed to transmit or receive on 5 GHz, no matter what firmware runs on top of it. That's the whole story for Flipper Zero's ESP32 add-ons: the original ESP32, ESP32-S2, ESP32-S3, ESP32-C3, and ESP32-C6 are all 2.4 GHz only at the chip level. ESP32 Marauder — or Bruce, or any other firmware — inherits whatever radio the module underneath it has. None of them can conjure a 5 GHz band that isn't wired into the hardware.

This trips people up most with the ESP32-C6, because Espressif markets it as a Wi-Fi 6 chip. Wi-Fi 6 is a protocol generation (802.11ax), not a frequency guarantee — C6 implements Wi-Fi 6, but only on the 2.4 GHz band. It's genuinely faster and more efficient than older 2.4 GHz silicon, but it still can't see a single 5 GHz access point. For why 2.4 GHz-only boards increasingly fall short as networks shift to 5 GHz, see our 2.4 GHz vs 5 GHz breakdown.

Users noticed the gap early. Marauder GitHub issue #645, opened 2025-01-21, is a running thread of people asking when 5 GHz support is coming — over a year of demand for hardware that, at the time, didn't exist yet.

What the ESP32-C5 changes

ESP32-C5 is Espressif's answer: the company's first dual-band chip, supporting both 2.4 GHz and 5 GHz Wi-Fi 6, released in 2024. It's the only ESP32 variant in this lineup with an actual 5 GHz radio in silicon — which is why any board claiming "5 GHz wardriving" for Flipper Zero in 2026 has to be built around C5, not a relabeled S3 or C6.

That hardware capability showed up in Marauder firmware earlier in 2026, and it wasn't smooth. Issue #1216 (2026-04-16) reported deauth simply not working on a C5 DevKit running firmware 1.11.1, and issue #1268 (2026-05-07) reported C5 scanning failing to start at all, with boot logs showing "Could not detect GPS baudrate" and "GPS Not Found" on firmware 1.12.1. The radio was there; the firmware driving it was still catching up.

The bigger recent shift is on the data pipeline, not the radio itself. Marauder v1.14.0, released 2026-07-22, added the first direct-from-device upload to WiGLE and WDGWars — no phone or PC relay app required — and extended that direct-upload capability specifically to the ESP32-C5 DevKit. The same release added a FindMy Live backend and a Mini v3 flasher. A follow-up, v1.14.1 (2026-08-01), shipped authoritative stable installer manifests with no major new features.

Outside the Flipper accessory world, justcallmekoko (Marauder's author) also maintains a standalone ESP32DualBandWardriver — informally the "C5 Wardriver" — that's seeing active releases (v2.3.0 on 2026-07-09, v2.3.1 on 2026-08-02). That kind of ongoing, author-driven iteration is a better signal of real progress than any single feature announcement.

"5 GHz" vs "5.8 GHz"

Worth clearing up before you read another product listing: Wi-Fi's "5 GHz band" (roughly 5.15–5.85 GHz depending on region and channel), cellular "5G," and the 5.8 GHz ISM band used by FPV drone video links are three different things that happen to share a number. "5G" is a network-generation name — it runs on a mix of sub-6 GHz and mmWave spectrum, none of which is the Wi-Fi 5 GHz band Marauder scans. The 5.8 GHz drone band sits near the top of Wi-Fi's 5 GHz range, but it's a different use case, different modulation, and a different regulatory class.

Some vendor copy blurs this on purpose or by accident. The JCMK Marauder C5 Adapter, for example, is marketed with "5.8GHz" language even though it's running the same ESP32-C5 Wi-Fi radio as everything else in this piece — and its firmware has open bugs of its own. When a listing says "5G" or "5.8GHz wardriving," check whether that means the real Wi-Fi 5 GHz band on genuine C5 silicon, or just a marketing number.

Is 5 GHz wardrive actually stable yet?

Short answer: it's early. Wardriving on Marauder — 2.4 GHz or 5 GHz — has had rough edges independent of band. Issue #1343 (2026-06-30) reported a white-screen freeze after exiting wardrive mode, reproducing around 20 files / 15.7 MB of logged data, and issue #1087 (2026-01-28) reported memory climbing to 95% during a wardrive session before a single AP had even been scanned. 5 GHz support on C5 adds its own layer of open issues on top of that baseline.

An honest 2026 note: 5 GHz wardriving on ESP32-C5 is maturing, not turnkey. Issue #1216 (2026-04-16) found deauth not working on the C5 DevKit under firmware 1.11.1. Issue #1268 (2026-05-07) found C5 scanning failing to start, with GPS baudrate detection errors on firmware 1.12.1. And the new direct-to-WiGLE upload path from v1.14.0 has its own open bug — issue #1409 (2026-07-30) — describing upload failures and devices rebooting mid-upload on v7 hardware. None of this is specific to any one board brand: it's Marauder firmware behavior, and any ESP32-C5 board running the same firmware version can hit it, Scout Lite included.

If you want 5 GHz wardriving today

Two things actually matter if 5 GHz wardriving is the goal: genuine ESP32-C5 silicon (not a 2.4 GHz-only S3 or C6 board with "5G" in the product name), and built-in GPS plus SD storage that work the moment you power on, because Marauder's wardrive app needs both to log anything useful. GPS in particular needs open sky and roughly 30 seconds to 2 minutes for a cold-start fix — it won't lock indoors or under heavy cover. Storage has its own hard rule: Marauder requires FAT32-formatted SD cards of 32 GB or smaller. If you're weighing specific boards, our best ESP32-C5 wardriving board guide compares every current option side by side.

Scout Lite is built around exactly that combination: genuine ESP32-C5, a hard-wired Quectel L86-M33 GPS module with no pin mapping to fight, onboard microSD, and ESP32 Marauder preloaded out of the box. It doesn't carry sub-GHz or NRF24 radios, so it's not a do-everything multitool — just a dedicated C5 wardrive board that skips the wiring step. It runs the same Marauder firmware as every other C5 board, though, so it inherits whatever firmware-layer bugs are open at the time — see the note above.

If your actual goal is 5 GHz packet capture rather than GPS wardriving — PMKID handshakes, PMF-aware deauth — that's a different job. Our 5Ghost vs ESP32 Marauder on 5 GHz breakdown covers that BW16-based approach instead.

Wardrive on 5 GHz without wiring a GPS module yourself

Scout Lite ships with ESP32-C5, a hard-wired GPS, and onboard microSD — Marauder preloaded, ready to scan out of the box.

Get the Scout Lite →
Read the setup guide →

FAQ

Can ESP32 Marauder do 5 GHz?
Only on ESP32-C5 hardware. Marauder is firmware — it can only use the radio that's physically on the board. The original ESP32, ESP32-S2, ESP32-S3, ESP32-C3, and ESP32-C6 are all 2.4 GHz only at the chip level, so Marauder can't add a 5 GHz band on those. On genuine ESP32-C5 boards, Marauder can scan 5 GHz, though the feature is still early and has open firmware bugs (see issues #1216 and #1268).
Is 5 GHz the same as 5G or 5.8 GHz?
No. Wi-Fi's 5 GHz band, cellular 5G, and the 5.8 GHz ISM band used by FPV drones are three different things that share a number. 5G is a network-generation name running on its own mix of spectrum, not the Wi-Fi band Marauder scans. The 5.8 GHz drone band sits near the top of Wi-Fi's 5 GHz range but is a separate use case and regulatory class. Some vendor listings mix these terms loosely, so check what a '5GHz' or '5.8GHz' claim actually refers to.
Is C5 5 GHz wardrive reliable yet?
Not fully. As of August 2026, Marauder's 5 GHz support on ESP32-C5 still has open GitHub issues — #1216 (deauth not working on C5 DevKit, firmware 1.11.1), #1268 (C5 scanning failing to start due to GPS baudrate detection, firmware 1.12.1), and #1409 (WiGLE/WDGWars uploads failing and devices rebooting mid-upload on v1.14.0). It works, but it's a maturing feature rather than a finished one, and that applies to any board running the same firmware.
Do I even need 5 GHz for wardriving?
Not necessarily. Most access points still broadcast on 2.4 GHz alongside 5 GHz, and the bulk of existing WiGLE data was collected on 2.4 GHz-only hardware for years. 5 GHz support adds coverage for dual-band-only or 5 GHz-only networks, but a 2.4 GHz-only ESP32 board can still wardrive productively — 5 GHz just closes a gap rather than being a hard requirement to start.

Sources & further reading (verified 2026-08-03): Espressif ESP32-C5 product page · Marauder v1.14.0 release notes · Marauder v1.14.1 release notes · Issue #645 — 5 GHz support requests · Issue #1216 — C5 deauth not working · Issue #1268 — C5 scanning does not start · Issue #1409 — WiGLE/WDGWars upload failures · Issue #1343 — white-screen freeze after wardrive · Issue #1087 — memory spike during wardrive · Marauder FAQ — SD card requirements · Marauder wardrive wiki — GPS behavior · justcallmekoko ESP32DualBandWardriver (C5 Wardriver).

For authorized security testing and education only. Test only networks and devices you own or have explicit written permission to test. You are responsible for compliance with all applicable laws and radio regulations (e.g. FCC Part 15 in the US). "Flipper Zero" and "ESP32 Marauder" are referenced for compatibility and comparison; PINGEQUA is independent and not affiliated with or endorsed by their respective owners.

Zurück zum Blog