Users on one floor report a dead WLAN while the access points stay up; how do you tell RF jamming or interference from a deauthentication flood, and what can you do?
answer
- radio energy, not forged frames
- no cipher gets a vote
- noise floor and retry rate
- session terminations against airtime
- find the source before changing the design
basics
~20 sJamming and non-Wi-Fi interference deny service at the radio level, so no cipher or PMF helps; they show as a raised noise floor and heavy retries, whereas a deauthentication flood shows as many session terminations. Locate the source, then work around or remove it.
solid answer
~40 sNIST SP 800-97 describes **jamming** as a device that emits energy on the WLAN's frequencies so they become unusable, deliberately or as an unintentional non-WLAN source, and states that the 802.11 standard offers no defence against jamming or flooding. So the diagnosis is about evidence, not cipher settings. Raised noise, high retry and channel-busy rates across **all** clients on a channel point to RF energy; many terminated sessions with signal levels that look healthy point to a **deauthentication flood**, which PMF would have neutralised for PMF clients. Several sensors can estimate where a transmitter is from signal strength (NIST SP 800-153), so staff can go and look. Meanwhile move clients to another channel or band and keep critical devices on a wire.
go deeper
Recall that jamming and interference are availability problems that no WLAN cipher defends against.
Explain jamming against flooding, why 802.11 security offers no defence, and what PMF does and does not cover.
Diagnose from several signals, noise floor, retries, termination counts and PMF status, locate the source from sensors and keep service up meanwhile.
Set the response ownership for deliberate jamming and for neighbours' equipment, and fund resilience such as multi-band design and wired fallback.
## The two failures look alike to a user A user sees one symptom, "the WLAN is dead", from two different causes. One acts on the radio channel; the other acts on the management plane. | | Jamming or interference | Deauthentication flood | |---|---|---| | Layer | Radio energy on the WLAN's frequencies | Forged management frames | | Source | Intentional, or an unintentional non-WLAN device | A transmitter sending frames that claim a legitimate sender | | Typical evidence | Raised noise floor, high retry and channel-busy rates, packet loss for every client on the channel | Many terminated sessions, clients re-associating, normal signal levels | | Does PMF help? | No | Yes, for clients that negotiated PMF | | Does a cipher help? | No | No, unless PMF is also in force | NIST SP 800-97 describes jamming as a device that emits electromagnetic energy on the WLAN's frequencies, making them unusable, and says it may be intentional or an unintentional non-WLAN device transmitting on the same frequency. It also describes flooding and states that the 802.11 standard does not provide any defence against jamming or flooding. ## Diagnosing from evidence None of the signals proves a cause alone, so compare several: 1. **Scope.** Does it hit one channel, one band, one floor, or every AP? Interference follows the radio environment, not the SSID. 2. **Retry and airtime counters.** High retries and busy airtime with healthy association counts point to RF trouble. 3. **Session terminations.** NIST SP 800-153 section 3.3 says a large number of events involving the termination of WLAN sessions, counted against a threshold, can indicate a DoS attack. 4. **PMF status.** If the SSID requires PMF, forged deauthentication frames should not be acted on, so a persisting outage there points back to RF. 5. **Timing.** A recurring pattern (the same hour each day) points to equipment on a schedule; a one-off to a deliberate act or a faulty device. A reason code in a termination is only what the frame claims; do not treat it as evidence of origin. ## A worked reading Suppose the third floor loses service every afternoon while the access points report themselves healthy. Three combinations of evidence are typical: | Evidence | Likely reading | Next step | |---|---|---| | Noise floor raised, retries high, few terminations, repeats at the same hour | An unintentional emitter on a schedule | Locate it and speak to facilities | | Noise normal, many terminations, clients re-associate at once, SSID without PMF | Forged deauthentication or disassociation | Require PMF where clients allow it and watch counts | | Noise raised, no pattern, appears and disappears | Possibly deliberate jamming, or a faulty device | Collect evidence from several sensors and involve physical security | The middle row is the only one PMF changes. The other two need the radio problem solved. ## What you can do - **Locate.** NIST SP 800-153 expects the capability to identify the physical location of a detected threat by estimating its distance from several sensors by received signal strength, so that appropriate personnel such as physical security staff can go to the place. - **Work around.** Move affected clients to another channel or band, and keep critical devices on a wired connection while you investigate. - **Remove.** An unintentional emitter is a facilities problem: find the device and fix or relocate it. - **Escalate.** If it looks deliberate, preserve the evidence and treat it as a security incident with physical security; do not answer with a countermeasure of your own. ## What the design can and cannot do You cannot encrypt your way out of an RF problem. Resilience comes from design: a channel plan that spreads load, spare capacity on more than one band, wired fallback for essential devices, and monitoring that watches noise and DoS conditions. NIST SP 800-153 lists interference among the DoS conditions that continuous monitoring should detect. ## Decision checklist 1. Which signals do we collect: noise floor, retries, airtime, termination counts? 2. Who owns the response when the source is a neighbouring tenant's equipment? 3. Which devices have a wired or secondary-band fallback?
- Would requiring PMF on the SSID have prevented this outage?Only if the cause was forged deauthentication or disassociation. PMF protects management frames and does nothing for energy on the channel. NIST SP 800-97 states the 802.11 standard offers no defence against jamming or flooding, so first establish from retries, noise and termination counts which one you have.
- How does monitoring raise an alert on a DoS condition?NIST SP 800-153 describes counting events in a period and alerting when a threshold is exceeded, for example many session terminations. Interference is listed among the DoS conditions to monitor. Tune thresholds per AP and per time of day so ordinary roaming does not alert.
- Who do you send once sensors have narrowed down where the transmitter is?NIST SP 800-153 says the location lets an organisation send appropriate personnel, such as physical security staff. If the emitter turns out to be a neighbour's or a legitimate device, the owner or facilities handle it; do not try to disrupt it yourself.
- Says WPA3 or AES encryption protects a WLAN from jamming
- Expects PMF to fix an outage caused by RF interference
- Treats every outage as a deauthentication attack without checking noise and retries
- Treats a reason code in a flood as proof of which device sent it
- Proposes answering a suspected jammer with a countermeasure of your own