How to Do Your First Wardrive with Flipper Zero + Scout Lite (Step by Step, 2026)

PINGEQUA Lab · Flipper Wardriving · 8 min read · Updated 2026-08-04

Your first wardrive is mostly about one thing: getting a GPS fix before you start scanning, so every Wi-Fi network you log arrives on WiGLE with real coordinates instead of being silently dropped.

Quick answer To do your first wardrive with a Flipper Zero, attach a GPS-equipped Wi-Fi board, open ESP32 Marauder's WarDrive mode (WiFi > Sniffers > Wardrive), wait outdoors until the screen shows real latitude/longitude instead of "No Fix", then move — Marauder writes a wardrive_ CSV to the SD card that you upload at wigle.net. With a pre-flashed, GPS-onboard board like PINGEQUA's Scout Lite ($64.98), there's no soldering, no PC, and no firmware install between you and that first CSV.

What you need for your first wardrive (the whole checklist)

Wardriving is just passive Wi-Fi scanning tagged with GPS coordinates and uploaded to a map like WiGLE. It never needs deauth or any attack feature — only a working scan loop and a GPS fix. That keeps the shopping list short:

Requirement Why it matters How Scout Lite covers it
Wi-Fi scan radio Finds the access points you log; dual-band catches 5 GHz APs a 2.4-only board misses ESP32-C5 — Espressif's first single-chip dual-band 2.4 & 5 GHz Wi-Fi 6 (802.11ax) MCU
GPS with a fix Every logged network needs coordinates, or Marauder drops the row Onboard L86 GPS, hard-soldered — nothing to wire
microSD card WarDrive logs (wardrive_*.csv) are written to the SD card Onboard microSD slot
Marauder firmware Provides the WarDrive scanning mode itself Pre-flashed with ESP32 Marauder out of the box
A Flipper Zero Hosts the board, shows the scan screen, powers it over GPIO Connects to the Flipper's GPIO header
A free WiGLE account Where you upload the CSV and see your map Create one at wigle.net before you go out

If you already own a different C5 board or a devboard you flashed yourself, the steps below are identical — the only difference is that a single-SKU, pre-flashed board removes the setup that trips up most first-timers. If you want the zero-setup path spelled out, see our no-soldering, no-PC Scout Lite quick start.

Before you scan anything: wardriving law varies by country and by what you do with the data. Logging beacon metadata you passively receive is treated differently from connecting to or probing networks. Read our plain-language is wardriving legal? breakdown first, and only ever scan passively.

Step 1 — Attach the board and prep the microSD

Seat the Scout Lite on your Flipper Zero's GPIO header the same way as any Wi-Fi devboard, and power the Flipper on. Because Scout Lite ships pre-flashed with ESP32 Marauder, there's nothing to install on the board itself.

Insert a microSD card formatted as FAT32. WarDrive logs are written to SD, and a card that's missing, unformatted, or in an unsupported format is the single most common reason a first wardrive produces no file. If you're not sure what to buy or how to format it, our microSD card guide for Marauder wardriving covers size, format, and the exact fixes.

Step 2 — Open Marauder and get a GPS fix first (go outside)

This is the step that decides whether your first run works. GPS needs a clear view of the sky — it will not get a fix indoors, under dense tree cover, or in a parking garage. Step outside into the open before you expect coordinates.

Open the ESP32 Marauder companion app on your Flipper and go to WiFi > Sniffers > Wardrive. The scan screen shows each network's ESSID/BSSID plus latitude and longitude when a fix is available — and shows "No Fix" when it isn't. A cold first fix outdoors can take anywhere from under a minute to several minutes while the L86 acquires satellites; give it time and don't start moving yet.

Rule of thumb: do not trust any data logged while the screen reads "No Fix." Marauder only writes a network row to the log while GPS has a valid fix, so scanning without one produces empty or coordinate-less results. If it stays on "No Fix" outdoors after several minutes, work through our GPS detected but no fix guide before continuing.

Step 3 — Start moving and let it log

Once the screen is showing real latitude/longitude instead of "No Fix", you're wardriving. Start driving — or walking; wardriving on foot works exactly the same — at a normal pace. Marauder continuously scans nearby Wi-Fi and appends each network, tagged with your current coordinates, to a log file on the SD card named with the wardrive_ prefix.

Keep the Flipper somewhere the GPS antenna still sees the sky (a dashboard beats a deep pocket). Watch that the coordinates keep updating as you move — if it flips back to "No Fix" for a stretch, those networks won't be logged, which is normal in tunnels or dense urban canyons.

One board, one SKU, first CSV the same day

Scout Lite is the PINGEQUA board built for exactly this: ESP32-C5 dual-band Wi-Fi 6 + onboard L86 GPS, pre-flashed with ESP32 Marauder — no soldering, no PC, no firmware install between you and WiGLE. $64.98.

Get Scout Lite for Flipper Zero →

Step 4 — Stop the scan and grab the CSV

When you're done, exit the WarDrive screen by tapping it (you may need a few taps, since it's mid-scan). Your run is saved to the microSD card as a wardrive_*.csv file. Pull the card and read it on a computer, or transfer the file off the Flipper — either way you're looking for the newest wardrive_ file.

Open it once to sanity-check before uploading: you want rows with actual latitude/longitude values, not blanks. An all-blank or empty file almost always means you scanned before getting a fix — back to Step 2.

Step 5 — Upload to WiGLE

WiGLE is the crowdsourced map your data feeds into, and uploads count toward your personal stats. Manual upload is straightforward:

  1. Sign in at wigle.net (create a free account first if you haven't).
  2. Open Uploads from the top toolbar.
  3. Press Upload a file, choose your wardrive_*.csv, and submit.

WiGLE processes the file and folds your networks into the global map, credited to your account. For the full walkthrough — including field-by-field notes and how the newer Marauder builds can push logs without a PC — see our upload wardrive data to WiGLE guide.

First-run problems, and where they come from

Almost every failed first wardrive traces back to one of three things:

  • No file on the SD card — missing, unformatted, or unsupported microSD. Reformat FAT32; see the microSD guide.
  • File exists but has no coordinates — you scanned while the screen read "No Fix." Get the fix first (Step 2).
  • "No Fix" that never clears — GPS can't see sky, or a wiring/UART issue on DIY boards. Start with GPS detected but no fix.

For a broader symptom-by-symptom list (crashes, memory, empty logs), our ESP32 Marauder wardrive not working — 8 fixes covers the rest. Once you've got a clean first run, the complete dual-band GPS wardriving guide goes deeper on getting the most out of 5 GHz coverage.

FAQ

How do I do my first wardrive with a Flipper Zero?
Attach a GPS-equipped Wi-Fi board, insert a FAT32 microSD, open ESP32 Marauder's WarDrive mode at WiFi > Sniffers > Wardrive, wait outdoors until the screen shows real latitude/longitude instead of "No Fix", then move at a normal pace. Marauder writes a wardrive_*.csv to the SD card, which you upload at wigle.net. With a pre-flashed, GPS-onboard board like Scout Lite, there's no soldering or firmware install first.
Do I need a PC or soldering to start wardriving?
Not with a pre-flashed, GPS-onboard board. PINGEQUA's Scout Lite ships with ESP32 Marauder already flashed and an L86 GPS hard-soldered on board, so you attach it to the Flipper and go. DIY setups — flashing your own firmware or wiring an external GPS — are where a PC and soldering come in; a single-SKU board skips that.
Why is my wardrive CSV empty or missing coordinates?
Marauder only saves a network row while GPS has a valid fix — anything scanned while the screen reads "No Fix" isn't logged with coordinates. An entirely missing file usually means the microSD is absent, unformatted, or an unsupported format. Get a GPS fix before you start moving, and format the card FAT32.
Where does Marauder save the wardrive file, and what's it called?
To the microSD card (onboard SD, or the Flipper's SD on serial firmware setups), as a file with the wardrive_ prefix — e.g. wardrive_0.csv. Read it on a computer or transfer it off the Flipper, then upload the newest one to WiGLE.
How long does it take to get a GPS fix on the first run?
A cold first fix outdoors typically takes from under a minute to several minutes while the receiver acquires satellites, and it needs a clear view of the sky — it won't fix indoors, in a garage, or under heavy tree cover. Later warm starts are usually quicker. Don't start scanning until the screen shows real latitude/longitude.
Can I wardrive on foot instead of in a car?
Yes — the process is identical whether you drive or walk; only your speed and coverage change. Keep the board positioned so its GPS antenna still sees the sky (a chest-height mount or dashboard beats a deep pocket), and watch that coordinates keep updating as you move.
Do I need 5 GHz for my first wardrive?
No — 2.4 GHz alone will log plenty of networks for a first run. Dual-band just catches 5 GHz-only access points a 2.4-only board would miss. Scout Lite's ESP32-C5 scans both natively, so you're not choosing. For where 5 GHz actually stands on C5 hardware in 2026, see our dedicated breakdown, Can the Flipper Zero wardrive on 5 GHz?
Is my first wardrive legal?
Passively logging Wi-Fi beacon metadata you receive is treated differently from connecting to or probing networks, and the law varies by country. Wardriving as described here is passive scanning only — no deauth, no attack features. Read our is wardriving legal? guide and stay within your local rules.

Related reading: New to the hardware side? Start with ESP32-C5 wardriving with no soldering, no PC and why the ESP32-C5 single chip enables dual-band wardriving. Choosing a board? See the best ESP32-C5 wardriving board for Flipper Zero (2026). Ready to go deeper? The complete dual-band GPS wardriving guide is the full reference.

Sources & further reading: WarDrive mode menu path, wardrive_ log prefix, GPS-fix requirement and WiGLE upload — ESP32 Marauder Wiki: Wardrive (justcallmekoko); ESP32-C5 as Espressif's first dual-band 2.4 & 5 GHz Wi-Fi 6 (802.11ax) MCU — Espressif ESP32-C5 product page; upload destination and stats crediting — WiGLE.net. Scout Lite specifications (ESP32-C5, onboard L86 GPS, microSD, pre-flashed ESP32 Marauder, $64.98) — PINGEQUA product data. Verified August 2026.

For authorized security testing and education only. Wardrive passively — scan and log only networks you are legally permitted to receive in your jurisdiction; never connect to, probe, or attack networks you do not own or have explicit written permission to test. You are responsible for compliance with local law and radio regulations. "Flipper Zero", "ESP32 Marauder", "WiGLE", "ESP32-C5" and other names are referenced for compatibility; PINGEQUA is independent and not affiliated with or endorsed by their owners.

Retour au blog