Wireless › Module 4 › Lesson 3
Driver Caveats
Kernel versions, firmware, and VM passthrough — troubleshoot YOUR $LAB_IFACE setup.
Visual · wireless_driver_caveats
Driver caveats literacy. $LAB_IFACE stability. Original Cyberlium.
Opening
When monitor fails, fix YOUR lab stack — do not drive to the neighbor's AP for 'better signal.'
Common issues: missing firmware, wrong driver (brcmfmac vs rtw88), USB power save, VM not passing device, regulatory domain blocking channels. Document fixes that worked on YOUR hardware for $LAB_IFACE. Troubleshooting is not an excuse to capture stranger SSIDs while 'testing.' Next: Adapter Lab.
1. Firmware and kernel coupling
Upgrading kernel may break monitor until driver catches up — pin notes on working combos for YOUR lab machine.
Corporate defenders track driver CVEs; you track lab stability.
Command guide
Try these commands — Firmware and kernel coupling
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Monitor mode — https://www.aircrack-ng.org/doku.php?id=compatible_cards Linux wireless — https://wireless.wiki.kernel.org/ (driver literacy)
═══ 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 list 2>/dev/null | grep -A5 'Supported interface modes' | head -20 || echo 'Not all chipsets support monitor/injection' dmesg 2>/dev/null | grep -iE 'wlan|80211|firmware' | tail -5 || journalctl -k -n 5 --no-pager 2>/dev/null | grep -i wlan
Primary tools to practice this lesson: iw, dmesg. Reference sites: Monitor mode (https://www.aircrack-ng.org/doku.php?id=compatible_cards); Linux wireless (https://wireless.wiki.kernel.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. VM and USB passthrough
Pass $LAB_IFACE to Kali VM exclusively; verify lsusb sees device. Host sleep can detach USB mid-lab — snapshot notes.
Never passthrough into cloud VMs targeting stranger nets — scope stays local lab.
3. Regulatory domain
iw reg get/set affects allowed channels — match YOUR lab country. Wrong domain causes AP invisible on expected channel.
Ship: working driver/firmware/kernel row for $LAB_IFACE. Next: Adapter Lab.
4. What you ship: driver stability row
Kernel, driver, firmware versions that work for $LAB_IFACE. Troubleshoot on $LAB_SSID only. chmod 600.
5. What you record before the next lesson
Date. $LAB_IFACE driver stack. File t15-m04-l03-driver-caveats.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
Switch to neighbor channel because lab AP 'hard to see.' Install random kernel modules from crack forums.
Right
Document stable stack for YOUR adapter. Next: Adapter Lab.
Mission: driver caveat notes
1) Record kernel/driver/firmware for $LAB_IFACE. 2) Note one fix if monitor failed before. 3) Test visibility of $LAB_SSID only. Never use driver debug as excuse to capture strangers.
Stuck? Ask Cyberlium AI Mentor
dmesg after plug-in often shows firmware load failures — check before blaming the AP.
Knowledge Check
APPLY: Monitor fails on $LAB_IFACE — first scope-safe step:
Multiple choice
Knowledge Check
APPLY: True or False: VM USB passthrough can affect $LAB_IFACE stability.
True or False
Knowledge Check
APPLY: Regulatory domain affects:
Multiple choice