Wardriving isn’t about breaking in—it’s about keeping attackers out.
From Dial-Up to WiFi: A Personal Journey
Back in the late ’90s, armed with an IBM 386 and a 36kbps modem, I embarked on a quest driven by sheer curiosity. Without access to books, mentors, or the internet as we know it today, I delved into the world of dial-up modems and bulletin board systems (BBS).
I wrote a BASIC program to sequentially dial phone numbers, logging those that responded with a fax tone. Manually, I would then attempt to connect to these numbers, hoping to stumble upon a BBS. This rudimentary form of exploration laid the foundation for my understanding of networks.
Fast forward to the present, and the landscape has evolved dramatically. The analog tones of modems have been replaced by the silent signals of WiFi. Yet, the essence of exploration remains.
Today, this practice is known as wardriving.
⚠️ Important: These tools are intended for ethical hacking, security research, and education. Use them only on systems and networks you own or have permission to test. Unauthorized use can lead to serious legal consequences.
What is Wardriving? The Basics and Ethics
Wardriving involves moving through areas—by car, bike, or on foot—with equipment designed to detect and log wireless networks. It’s a method used by cybersecurity professionals to map out WiFi networks, identify potential vulnerabilities, and ensure network security.
The Ethical Line
Engaging in wardriving comes with responsibilities:
- Permission: Always have explicit permission before scanning or testing networks.
- Privacy: Do not attempt to access or intercept data from networks that aren’t yours.
- Legality: Ensure your activities comply with local laws and regulations.
Ethical wardriving is about strengthening network defenses, not exploiting weaknesses.
· · ─ ·𖥸· ─ · ·
Why Ethical Reconnaissance Matters
Wireless networks are ubiquitous, but not all are secure. Misconfigurations, outdated encryption, and weak passwords can leave networks vulnerable.
Real-World Risks
- Data Breaches: Unauthorized access can lead to sensitive information being compromised.
- Network Hijacking: Attackers can exploit weak networks to launch further attacks.
- Service Disruption: Malicious entities can disrupt services, leading to downtime and loss.
By proactively identifying these vulnerabilities, organizations can address them before malicious actors exploit them.
· · ─ ·𖥸· ─ · ·
Building Your Wardriving Toolkit
Embarking on a wardriving mission requires the right set of tools:
Hardware
- Laptop: Preferably running Kali Linux or a similar penetration testing distribution.
- Raspberry Pi: A compact alternative, suitable for portable setups.
- Smartphone: With applications like Termux, though limited compared to dedicated devices.
WiFi Adapters
Not all WiFi adapters are created equal. For effective wardriving, your adapter must support:
- Monitor Mode: Allows the device to capture all wireless traffic.
- Packet Injection: Enables the device to send packets to networks.
Recommended Adapter: TP-Link Archer T2U Plus (Realtek RTL8821AU chipset)
GPS Module
Integrating a GPS module allows for geotagging of detected networks, aiding in mapping and analysis.
Software
Wireshark: A network protocol analyzer for in-depth packet analysis.
Kismet: A wireless network detector, sniffer, and intrusion detection system.
Aircrack-ng: A suite of tools for assessing WiFi network security.
· · ─ ·𖥸· ─ · ·
Setting Up the TP-Link Archer T2U Plus on Kali Linux
To harness the full capabilities of the TP-Link Archer T2U Plus, follow these steps:
0. Identify Your Device
lsusb
# Sample Output
Bus 002 Device 006: ID 05ac:0252 Apple, Inc. Internal Keyboard/Trackpad (ANSI)
Bus 002 Device 005: ID 05ac:8242 Apple, Inc. Built-in IR Receiver
Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller
Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 003: ID 0424:2513 Microchip Technology, Inc. (formerly SMSC) 2.0 Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05ac:8509 Apple, Inc. FaceTime HD Camera
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 2357:0120 TP-Link Archer T2U PLUS [RTL8821AU] <---- This is your device
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
1. Install Dependencies
sudo apt update
sudo apt install -y dkms git build-essential libelf-dev linux-headers-$(uname -r)
2. Clone the Driver Repository
git clone https://github.com/aircrack-ng/rtl8812au.git
cd rtl8812au
3. Compile and Install the Driver
make
sudo make install
sudo modprobe 8821au
4. Enable Monitor Mode
sudo ip link set wlan0 down
sudo iwconfig wlan0 mode monitor
sudo ip link set wlan0 up
Replace wlan0
with your adapter’s interface name if different.
· · ─ ·𖥸· ─ · ·
Scanning and Discovering WiFi Networks
With your setup ready, begin scanning:
Using nmcli
nmcli dev wifi list
Using iwlist
sudo iwlist wlan0 scanning
Using airodump-ng
sudo airodump-ng wlan0
These tools provide information such as:
- SSID: Network name
- BSSID: MAC address of the access point
- Channel: Frequency channel used
- Encryption: Security protocol in place
- Signal Strength: Proximity indicator
· · ─ ·𖥸· ─ · ·
Logging Scan Results for Future Analysis
For practical analysis and repeat scans, it’s helpful to log scan data to a file at fixed intervals.
Using watch
and nmcli
for Logging
watch -n 5 "nmcli -f SSID,BSSID,SIGNAL,CHAN,SECURITY dev wifi list >> wifi_log.txt"
This command will:
- Run every 5 seconds (
-n 5
) - Append (
>>
) a fresh scan result towifi_log.txt
- Log SSID, BSSID, signal strength, channel, and security type
Continuous logging allows for comprehensive analysis over time.
Logging Every 5 Seconds with Timestamps
Create a Bash script:
#!/bin/bash
while true; do
echo "$(date):" >> wifi_log.txt
nmcli -f SSID,BSSID,SIGNAL,CHAN,SECURITY dev wifi list >> wifi_log.txt
echo "---" >> wifi_log.txt
sleep 5
done
Make the script executable:
chmod +x wifi_logger.sh
Run the script:
./wifi_logger.sh
This script logs the current WiFi environment every 5 seconds, appending the data to wifi_log.txt
with timestamps for each entry.
· · ─ ·𖥸· ─ · ·
Wrapping Up Wardriving: Master the Airwaves, Secure Your Space
Wardriving isn’t just a nostalgic nod to early network exploration—it’s a critical skill for today’s cybersecurity defenders. By understanding your wireless environment, spotting vulnerable networks, and using the right tools in monitor mode, you take control of your airspace before attackers do.
Quick Recap:
- Wardriving is ethical wireless reconnaissance, never unauthorized access.
- A compatible WiFi adapter with monitor mode is your essential sidekick.
- Tools like
airodump-ng
andkismet
turn raw signals into actionable intelligence. - Logging your data frequently unlocks deeper analysis and better network security insights.
Ready to elevate your wireless security skills? Stay ahead with practical guides, open-source tools, and real-world recon strategies tailored for developers and security pros like you.
👉 Subscribe now to my newsletter for exclusive updates and step-by-step tutorials:
https://www.samgalope.dev/newsletter/
Don’t just scan the airwaves—own them.
⚠️ Important: These tools are intended for ethical hacking, security research, and education. Use them only on systems and networks you own or have permission to test. Unauthorized use can lead to serious legal consequences.
Leave a Reply