Deauth Detection & Defense: Testing Your Own Network
What You're Actually Testing
Deauthentication frames are a legitimate part of the 802.11 WiFi standard (used for normal disconnect handling), but they're unauthenticated in older WiFi security models — meaning anyone in range can forge one and force a client off your network. Testing your own network's resilience to this is legitimate security validation; using it against networks you don't own is not (see the Marauder setup guide's legal section).
Why This Matters
A network vulnerable to deauth attacks can be knocked offline trivially, and — more seriously — deauth is sometimes used as a precursor to capturing a WPA handshake for offline password cracking (forcing a client to reconnect gives an attacker a fresh handshake to capture). Testing your own network's resistance to this tells you whether you're exposed to that follow-on attack.
The Real Fix: Protected Management Frames (PMF/802.11w)
Modern WiFi security (WPA3, and WPA2 with PMF enabled) cryptographically signs management frames including deauth — a forged deauth frame without the correct signature is simply ignored by PMF-aware clients and access points. This is the actual solution, not something you can bolt on after the fact at the client level.
Checking If Your Network Has PMF Enabled
- WPA3 networks have PMF mandatory by the standard — if you're on WPA3, you're already protected against basic deauth.
- WPA2 networks: check your router's wireless security settings for "PMF," "802.11w," or "Management Frame Protection" — many routers support it on WPA2 but don't enable it by default for backward compatibility with very old client devices.
Testing With the WiFi Dev Board
With Marauder (see setup guide), run the Deauth function targeting your own network's AP/clients specifically (select your own SSID from the scan list, never a network you don't own). On a PMF-protected network, connected clients should show no disruption — that's the test passing. On a network without PMF, you'll see genuine disconnects, confirming the exposure.
Practical Steps If Your Network Fails This Test
- Enable PMF/802.11w in your router's wireless security settings if it's supported but currently off.
- If your router doesn't support PMF at all, this is a genuine argument for a router upgrade — it's become a fairly standard feature on hardware from the last several years.
- Move to WPA3 if all your client devices support it — this makes PMF mandatory rather than optional and closes the gap entirely.
What This Doesn't Protect Against
PMF stops forged deauth frames specifically — it doesn't address other WiFi attack surfaces (WPS vulnerabilities, weak passwords enabling dictionary attacks on captured handshakes, rogue AP/evil twin attacks). Deauth resistance is one piece of a broader WiFi security posture, not the whole picture.
Related Guides
- How to Hack Wi-Fi and Bluetooth with the Flipper Zero and Wi-Fi Marauder
- Build a Standalone ESP32 WiFi Security Testing Tool with Marauder
- How to Install Custom Firmware and Develop Apps for the Flipper Zero
- How to Use Bluetooth HID on the Flipper Zero for Wireless BadUSB Attacks
- How to Analyze EMV Payment Cards with the Flipper Zero: NFC, APDU Commands, and Security Architecture
- How to Use the Flipper Zero GPIO for Hardware Hacking: UART, SPI, I2C, and Debugging
- How to Build Advanced BadUSB Payloads on the Flipper Zero: UAC Bypass, EDR Evasion, and Anti-Forensics
- How to Hack Infrared Protocols with the Flipper Zero: NEC, RC5, Sony, and Raw Analysis