Wireless › Module 4 › Lesson 4
Adapter Lab
Prove $LAB_IFACE sees $LAB_SSID on expected channel — optional brief monitor enter/exit, no neighbor capture file.
Visual · wireless_adapter_lab
Adapter lab: $LAB_IFACE + $LAB_SSID. Original Cyberlium.
Opening
If $LAB_IFACE cannot see $LAB_SSID, fix the lab — do not borrow a neighbor BSSID.
Lab chain: identify $LAB_IFACE → confirm driver → associate or observe $LAB_SSID on documented channel → optional monitor enter/exit per brief → return to managed. If brief allows short capture, filter analysis to $LAB_SSID BSSID only — delete if neighbors leaked in. No airodump wardrive. No deauth. Next: Quiz — Adapter and Monitor Mode.
1. Lab steps
Document each step: iface name, driver, channel of $LAB_SSID, proof of visibility (scan line or capture filter showing lab BSSID only).
Command guide
Try these commands — Lab steps
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Adapter lab — https://www.aircrack-ng.org/doku.php?id=compatible_cards iw manual — https://wireless.wiki.kernel.org/en/users/documentation/iw
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install iw sudo apt install network-manager sudo apt install aircrack-ng
macOS: Prefer Linux lab VM for iw Use airport / System Settings Prefer Kali VM — aircrack-ng needs supported adapter
Windows: Use Kali VM / WSL with iw Use netsh wlan (built-in) Use Kali VM with USB passthrough adapter
═══ LINUX / macOS ═══
Command — copy this
iw dev 2>/dev/null; nmcli device status 2>/dev/null sudo airmon-ng check 2>/dev/null || echo 'Run airmon-ng check on YOUR lab adapter only'
Primary tools to practice this lesson: iw, nmcli, airmon-ng. Reference sites: Adapter lab (https://www.aircrack-ng.org/doku.php?id=compatible_cards); iw manual (https://wireless.wiki.kernel.org/en/users/documentation/iw). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Leak handling
If neighbor SSIDs appear in scan output, do not copy them into shipped notes — redact. Narrow channel to lab AP.
3. Close
Return managed mode. chmod 600. Quiz next — then aircrack-ng Suite Literacy.
4. What you ship: adapter lab transcript for $LAB_SSID
$LAB_IFACE proof on $LAB_SSID channel. Monitor enter/exit if brief allows. No neighbor capture files. chmod 600.
5. What you record before the next lesson
Date. $LAB_IFACE lab transcript. $LAB_SSID only. File t15-m04-l04-adapter-lab.txt chmod 600.
6. Wrong vs right: stranger SSIDs vs YOUR lab AP
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Save full building scan as lab proof. Stay in monitor at coffee shop.
Right
Adapter lab on $LAB_SSID only. Next: Quiz — Adapter and Monitor Mode.
Mission: adapter lab on YOUR radio
1) Document $LAB_IFACE and driver. 2) Prove $LAB_SSID visible on documented channel. 3) Optional monitor enter/exit per brief. 4) chmod 600. Never wardrive.
Stuck? Ask Cyberlium AI Mentor
Deleting accidental neighbor lines from notes is part of scope hygiene.
Knowledge Check
APPLY: Adapter lab capture analysis filters to:
Multiple choice
Knowledge Check
APPLY: True or False: Neighbor SSIDs in scan output should be copied into shipped lab notes.
True or False
Knowledge Check
APPLY: After monitor lab:
Multiple choice