Programmatically Identifying Rogue Access Points with Scapy and Spectrum Analysis
This advanced guide details how to use Linux, Python, and the Scapy library in conjunction with specialized hardware (like an SDR) to programmatically detect and characterize unauthorized or rogue Wi-Fi access points.
Direct Diagnostic & Remediation Summary
- Prerequisite Check: Ensure you have root privileges and necessary drivers installed for your wireless card/SDR.
- Execution Command: Run the Python script with elevated permissions:
sudo python3 rogue_scanner.py.
Objective Summary
This tutorial guides the user through setting up a Python environment to sniff Wi-Fi traffic using Scapy. The goal is to move beyond simple SSID detection by analyzing raw 802.11 frames to identify unauthorized (rogue) APs broadcasting on the network segment.
Warning: Unauthorized scanning of networks can be illegal. Only perform these tests on networks where you have explicit, written permission from the owner.
Symptoms of Rogue APs
A rogue AP is an unauthorized wireless access point connected to a wired network backbone that mimics a legitimate one (Evil Twin) or simply operates without authorization. Symptoms include:
- Detecting SSIDs that match known corporate names but originate from unknown MAC addresses.
- High volume of Beacon frames originating from unexpected physical locations.
- Interference patterns that do not correlate with known authorized hardware sources.
The primary symptom we address is the inability to reliably distinguish legitimate APs from unauthorized ones using standard GUI tools.
Standard network scanners often rely on association requests or visible SSIDs, which can be easily spoofed. True rogue detection requires analyzing the raw 802.11 management frames (Beacons and Probe Responses). Scapy allows crafting and parsing these low-level packets directly from the wireless interface in monitor mode. The root cause is insufficient visibility into the physical layer signaling; the solution involves deep packet inspection at Layer 2.
Environment Preparation & Interface Setup
Before writing code, the wireless interface must be in monitor mode to capture raw 802.11 frames.
- Check Hardware Support: Verify your adapter supports monitor mode (e.g., many Atheros or Ralink chipsets do).
- List Interfaces: Use the following command to see available network interfaces:
ip a. - Set Monitor Mode: Replace
wlan0with your actual wireless interface name.sudo airmon-ng check killsudo airmon-ng start wlan0 - Verify New Interface: A new interface (e.g.,
wlan0mon) should appear and be ready for sniffing.
Python Scripting with Scapy
We will write a Python script (rogue_scanner.py) to capture packets on the monitor interface and parse the BSSID, SSID, and signal strength.
# rogue_scanner.py
from scapy.all import sniff, Dot11, Ether
import time
INTERFACE = "wlan0mon" # Must match your output from Step 1
def packet_callback(packet):
if packet.haslayer(Dot11):
# Extract key information from the 802.11 frame header
bssid = packet[Dot11].src
ssid = "N/A"
try:
# Check for beacon frames which contain SSID in management frames
if packet[Dot11].llcp_type == 0: # Beacon frame type (simplified check)
info = packet[Dot11].info.decode('utf-8', 'ignore')
ssid = info.split("SSID:")[-1].strip().split('\
')[0]
except Exception:
pass
print(f"[+] Detected AP | BSSID: {bssid} | SSID: {ssid}")
# Sniff continuously, processing packets every 5 seconds to prevent overwhelming the terminal
print("[*] Starting rogue AP scan. Press Ctrl+C to stop.")
try:
sniff(iface=INTERFACE, prn=packet_callback, store=0, filter="802.11")
except PermissionError:
print("[!] ERROR: Permission denied. Run the script with sudo.")
except KeyboardInterrupt:
print("\
[+] Scan stopped by user.")
Remember to replace wlan0mon in the script above if your interface name differs.
Filtering and Analysis Logic
The raw output lists every detected AP. To identify rogue ones, you must correlate BSSIDs/SSIDs against a known baseline (your authorized list).
- Baseline Creation: Manually compile a list of all MAC addresses and SSIDs belonging to your organization's legitimate infrastructure.
- Script Enhancement: Modify the
packet_callbackfunction to check if the detected BSSID/SSID exists in your authorized dictionary. If not found, flag it as suspicious or rogue. - Spectrum Integration (Advanced): For definitive proof, use SDR software (like GQRX) alongside this script. The Python output tells you what is transmitting; the SDR confirms how much energy is present at that frequency band, helping rule out mere noise vs. intentional transmission.
For quick analysis after running the script multiple times, pipe the output to grep or awk for repeated BSSIDs.
Common Pitfalls & Advanced Diagnostics
- Issue: No packets are detected.
Diagnosis: The interface might not be in monitor mode, or the card is blocked.
Fix: Re-runsudo airmon-ng start wlan0and check the output carefully. - Issue: Scapy throws Layer 2 errors.
Diagnosis: You may lack necessary kernel modules or drivers for raw packet capture.
Fix: Install required dependencies (e.g.,sudo apt install tcpdump libpcap-dev). - Issue: Only sees "my_home_wifi" but nothing else.
Diagnosis: You might be filtering too aggressively, or the APs are using non-standard beacon intervals.
Fix: Temporarily remove anyfilter="802.11"from the sniff function to capture all possible management frames. - Issue: High CPU usage during scan.
Diagnosis: The script is processing every single packet, including noise.
Fix: Implement rate limiting or add more rigorous filtering logic based on expected beacon intervals (e.g., check only for packets within a 1-second window).
Verification, Results & Long-Term Stability Validation
After running the script and compiling suspicious BSSIDs/SSIDs, verification involves triangulation and confirmation.
- Cross-Reference: Check the flagged rogue MAC addresses against known manufacturer OUI databases. A random or unknown vendor is highly suspect.
- Physical Sweep: If a suspicious AP is identified (e.g., BSSID: AA:BB:CC:DD:EE:F1, SSID: CorpGuest), physically walk the area while monitoring the scanner to see if the signal strength drops off abruptly at certain points, indicating a hidden source.
- System Hardening: Configure your OS firewall (iptables/ufw) to log all wireless interface activity and flag any unexpected MAC addresses attempting to bridge onto the wired network backbone.
For long-term stability, schedule automated cron jobs to run this scanner script nightly during low-traffic periods.
Frequently Asked Questions
Q: Can this detect a Man-in-the-Middle (MITM) attack?
A: This script detects the existence of rogue APs. Detecting an active MITM requires analyzing traffic payloads (e.g., sniffing for unencrypted credentials or unexpected DHCP responses), which is significantly more complex and often requires specialized payload decryption keys.
Q: Is my Wi-Fi card compatible with this?
A: Not all cards support monitor mode; check documentation or use airmon-ng man. Cards designed for enterprise environments (like those used in dedicated security hardware) are usually best suited.
Q: What is the difference between a rogue AP and an adjacent channel interference?
A: Rogue APs broadcast specific, identifiable SSIDs/BSSIDs. Interference appears as generalized high noise floor readings across multiple frequencies without coherent management frame patterns.
sudo airmon-ng check kill
sudo airmon-ng start wlan0
python3 rogue_scanner.py
Frequently Asked Questions
What is the primary difference between using Scapy and Wireshark for this task?
Wireshark provides a GUI visualization of captured packets, which is excellent for initial inspection. Scapy allows programmatic control, filtering, and automated analysis (like comparing against a known list) directly within Python code, making it scalable for unattended scanning.
Must I use an SDR to detect all rogue APs?
No, not always. If the rogue AP is broadcasting standard 802.11 signals, Scapy on a monitor-mode card will capture its management frames. An SDR is only strictly necessary if the attacker is using non-standard or highly encrypted physical layer signaling.
How often should I run this scan?
For critical environments, automated scans should run at least every 4 to 8 hours, especially after changes in network topology or personnel access.
Need help implementing this solution?
Our cybersecurity and infrastructure engineers can audit, harden, or configure your systems directly.
Community Discussion & Confirmations (0)
Technical questions, hardware findings, and verified fix reports.
No reader questions posted yet. Have you tried this solution or experienced an edge case? Post below.