Adapters
USB Wi-Fi adapters vary in chipset, driver, and monitor support — pick YOUR $LAB_IFACE deliberately.
Visual · wireless_adapters
Adapter literacy. $LAB_IFACE placeholder. YOUR hardware only. Original Cyberlium.
Not every dongle can listen — adapter choice is a lab design decision, not a shopping list for jamming strangers.
Wireless labs often need a separate adapter for monitor mode while built-in Wi-Fi stays managed for association to $LAB_SSID. Chipsets (MediaTek, Realtek, Atheros) differ in driver support across Linux. Defenders care about inventory; attackers misuse any adapter on stranger air — you won't. Document YOUR adapter model mapped to $LAB_IFACE. Never buy gear to attack neighbors. Next: Monitor Mode.
1. Managed vs monitor-capable
Managed mode joins networks normally. Monitor mode passes raw 802.11 frames to userspace tools. Some adapters cannot monitor; some need patched drivers.
Lab design: one iface associated to $LAB_SSID (managed), optional $LAB_IFACE for observe-only labs per brief.
Command guide
Try these commands — Managed vs monitor-capable
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Compatible adapters — https://www.aircrack-ng.org/doku.php?id=compatible_cards Linux wireless wiki — https://wireless.wiki.kernel.org/
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install iw
macOS: Prefer Linux lab VM for iw
Windows: Use Kali VM / WSL with iw
═══ LINUX / macOS ═══
Command — copy this
iw dev 2>/dev/null || echo 'No wireless — use USB adapter in lab VM' lsusb 2>/dev/null | grep -iE 'wireless|wifi|802.11|realtek|atheros|ralink' || lsusb 2>/dev/null | head -10
Primary tools to practice this lesson: iw, lsusb. Reference sites: Compatible adapters (https://www.aircrack-ng.org/doku.php?id=compatible_cards); Linux wireless wiki (https://wireless.wiki.kernel.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Driver and firmware
Kernel drivers, usb modeswitch, and firmware files determine stability. Keep notes on versions that work on YOUR laptop — not forum threads about cracking neighbor APs.
Defender parallel: asset inventory includes wireless adapters on corporate laptops.
3. Scope
Adapter on desk ≠ permission on air. RoE still limits to $LAB_SSID. Ship: model, driver, $LAB_IFACE mapping. Next: Monitor Mode.
4. What you ship: adapter inventory row
Model, chipset, driver, $LAB_IFACE name, monitor-capable Y/N. For YOUR lab only. chmod 600.
5. What you record before the next lesson
Date. Adapter model and $LAB_IFACE. File t15-m04-l01-adapters.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: Buy high-gain antenna to reach neighbor APs. Use unknown AliExpress dongle on café without RoE.
- Right: Document YOUR adapter for lab. Next: Monitor Mode.
Mission: inventory YOUR wireless adapter
1) Record adapter model and driver. 2) Map to $LAB_IFACE. 3) Note monitor support status. Never target neighbor radios.
Stuck? Ask Cyberlium AI Mentor
Virtual machines pass USB adapters through — document if $LAB_IFACE lives in VM.
APPLY: Monitor mode primarily allows:
APPLY: True or False: Any USB Wi-Fi dongle supports monitor mode equally.
APPLY: $LAB_IFACE in Cyberlium is: