Dot11 Lab
Document band, BSSID, ESSID, and auth mode for $LAB_SSID — observe only, no neighbor capture.
Visual · wireless_dot11_lab
802.11 inventory lab on $LAB_SSID. Original Cyberlium.
Defenders inventory before they alert — write YOUR lab AP row before any monitor mode.
Combine Module 2 lessons into one lab artifact: band, channel, width, ESSID $LAB_SSID, BSSID, auth mode, and expected client count on YOUR AP. Optional: note beacon interval or supported rates from YOUR lab client scan filtered to $LAB_SSID only. No airodump on neighbor lists. No deauth. Next: Quiz — 802.11 Literacy.
1. Lab steps
Create inventory table for $LAB_SSID: band, channel, BSSID, auth mode. Source data from YOUR AP admin UI or client scan filtered to lab SSID.
Command guide
Try these commands — Lab steps
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
802.11 lab — https://www.wi-fi.org/discover-wi-fi/security Wireshark — https://www.wireshark.org/
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install network-manager sudo apt install tcpdump
macOS: Use airport / System Settings
Windows: Use netsh wlan (built-in) Use Wireshark or install via WSL
═══ LINUX / macOS ═══
Command — copy this
nmcli device wifi list 2>/dev/null | head -15 sudo tcpdump -i any -c 5 -n 2>/dev/null || tcpdump -i any -c 3 -n 2>/dev/null || echo 'Capture 5 frames on YOUR machine only'
Primary tools to practice this lesson: nmcli, tcpdump. Reference sites: 802.11 lab (https://www.wi-fi.org/discover-wi-fi/security); Wireshark (https://www.wireshark.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Filter discipline
If your scan UI shows neighbor SSIDs, do not log them — record $LAB_SSID row only. Redact any accidental neighbor names from notes.
3. Close
chmod 600. Quiz next — then WEP WPA WPA2 WPA3.
4. What you ship: 802.11 inventory for $LAB_SSID
One table row: band, channel, BSSID, auth mode for YOUR lab AP. No neighbor SSIDs. chmod 600.
5. What you record before the next lesson
Date. $LAB_SSID inventory table. File t15-m02-l04-dot11-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: Paste full wardrive SSID list into lab notes. Capture café beacons 'for comparison.'
- Right: Inventory $LAB_SSID only. Next: Quiz — 802.11 Literacy.
Mission: 802.11 inventory lab
1) Fill inventory row for $LAB_SSID. 2) State auth mode. 3) chmod 600. 4) No neighbor SSID logging. Never deauth or clone ESSIDs.
Stuck? Ask Cyberlium AI Mentor
This table becomes your filter checklist before every capture lab.
APPLY: Dot11 lab records:
APPLY: True or False: Neighbor SSIDs may be logged 'for extra credit.'
APPLY: Inventory before capture helps you: