Wireless Architecture
802.11 Frame Format
802.11 wireless frames are more complex than 802.3 Ethernet frames. Depending on the 802.11 version and message type, some fields may be omitted.
- Frame Control: 2 bytes (16 bits). Indicates message type and subtype.
- Duration/ID: 2 bytes. Indicates the time in microseconds the channel is dedicated for transmission, OR acts as an identifier for the client-AP association.
- Addresses: Up to 4 addresses can be present depending on the message type:
- DA (Destination Address): Final recipient of the frame.
- SA (Source Address): Original sender of the frame.
- RA (Receiver Address): Immediate recipient (not necessarily final destination).
- TA (Transmitter Address): Immediate sender (not necessarily original source).
- Sequence Control: Used to reassemble fragments and eliminate duplicate frames.
- QoS Control: Used to prioritize certain traffic.
- HT (High Throughput) Control: Added in 802.11n (Wi-Fi 4) to enable high-throughput operations. (Note: 802.11ac / Wi-Fi 5 is known as Very High Throughput or VHT).
- Frame Body: The encapsulated packet (payload).
- FCS (Frame Check Sequence): Located in the trailer; used for error checking.
802.11 Association Process & Message Types
Before a wireless station (client) can send traffic through an Access Point (AP), it must form a connection.
Connection States
- State 1: Not authenticated and not associated.
- State 2: Authenticated but not associated.
- State 3: Authenticated and associated (Can now send data).
Scanning Methods
- Active Scanning: Station sends a Probe Request and listens for a Probe Response from the AP.
- Passive Scanning: Station listens for periodic Beacon messages advertised by the AP.
graph TD
A[State 1: Not Auth/Assoc] -->|Active: Probe Req/Resp OR Passive: Beacon| B[Discover AP/BSS]
B -->|Auth Exchange e.g., Password| C[State 2: Authenticated]
C -->|Association Req/Resp| D[State 3: Auth & Assoc]
D -->|Can now send Data| E[Traffic Flow]
802.11 Message Types
| Type | Purpose | Examples |
|---|---|---|
| Management | Manage the Basic Service Set (BSS). | Beacon, Probe, Authentication, Association |
| Control | Control access to the radio frequency medium. Assists delivery of management/data frames. | RTS (Request to Send), CTS (Clear to Send), ACK |
| Data | Send actual data packets. | Encapsulated payload |
Wireless AP Deployment Architectures
There are three primary ways to deploy wireless access points.
1. Autonomous APs (Local-MAC Architecture)
- Concept: Self-contained, independent systems. No Wireless LAN Controller (WLC) required.
- Management: Configured individually via Console, Telnet, SSH, or HTTP/HTTPS GUI. IP address required for remote management.
- Configuration: RF parameters (power, channel), security (ACLs), and QoS are configured manually per AP. No central monitoring.
- Switch Connection: Must connect to the switch via a Trunk Link.
- Requires a VLAN for each SSID.
- Requires a separate Management VLAN (Best Practice).
- Traffic Flow: Very direct path. Client $\rightarrow$ AP $\rightarrow$ Switch $\rightarrow$ Default Gateway. Local wireless traffic does not enter the wired network.
- Drawbacks: Unscalable for large networks. Requires stretching VLANs across the entire network, which creates large broadcast domains, triggers Spanning Tree Protocol (STP) link disabling, and is labor-intensive to manage.
- Modes: Can function as Repeater, Outdoor Bridge, or Workgroup Bridge.
2. Lightweight APs (Split-MAC Architecture)
- Concept: Functions are split between the AP and a central Wireless LAN Controller (WLC).
- AP Responsibilities: Real-time RF operations, encryption/decryption, sending beacons/probes.
- WLC Responsibilities: RF management, security/QoS policies, client authentication, roaming, and central configuration.
- Security: AP and WLC authenticate each other using X.509 digital certificates.
- Protocol: Uses CAPWAP (Control and Provisioning of Wireless Access Points), based on the older LWAPP protocol.
- Tunnels: Two CAPWAP tunnels are established between AP and WLC:
- Control Tunnel: UDP Port 5246. Used for config/management. Encrypted by default.
- Data Tunnel: UDP Port 5247. Carries client traffic. Unencrypted by default (can be encrypted using DTLS - Datagram Transport Layer Security, which uses UDP unlike standard TLS).
- Switch Connection: Connects to the switch via an Access Link (no trunk needed). The WLC connects to the network via a Trunk Link.
- Traffic Flow: All traffic (even local client-to-client) is tunneled to the WLC first, then forwarded to the wired network.
graph LR
subgraph Autonomous Local-MAC
C1[Client] -->|802.11| AP1[Autonomous AP]
AP1 -->|Trunk: VLAN 10,20,99| SW1[Switch]
SW1 -->|Routed| GW1[Default Gateway]
end
subgraph Lightweight Split-MAC
C2[Client] -->|802.11| AP2[Lightweight AP]
AP2 -->|Access Link| SW2[Switch]
SW2 -->|CAPWAP UDP 5246/5247| WLC[WLC]
WLC -->|Trunk| SW3[Switch]
SW3 -->|Routed| GW2[Default Gateway]
end
Split-MAC Benefits: High scalability, dynamic channel assignment, automatic transmit power adjustment, self-healing coverage, seamless roaming, client load balancing, and centralized security/QoS.
3. Cloud-Based APs
- Concept: Autonomous APs that are centrally managed in the cloud (e.g., Cisco Meraki).
- Management: Configured/monitored via a cloud dashboard (e.g., Meraki Dashboard). The cloud dictates RF channels and power.
- Traffic Flow: Only management/control traffic is sent to the cloud. Regular data traffic flows directly to the wired network (like Autonomous APs).
- Note: This is a hybrid approach, sitting between Autonomous and Split-MAC architectures.
Lightweight AP Modes
Lightweight APs can operate in several specialized modes depending on their function.
| Mode | Offers BSS? | Primary Function |
|---|---|---|
| Local | Yes | Default mode. Standard AP operation serving clients. |
| FlexConnect | Yes | Locally switches/forwards traffic between wired/wireless if the CAPWAP tunnel to the WLC goes down. |
| Sniffer | No | Captures 802.11 frames and sends them to packet capture software (e.g., Wireshark) for analysis. |
| Monitor | No | Listens to 802.11 frames to detect rogue devices. Can send de-authentication messages to disassociate rogues. |
| Rogue Detector | No | Does not use its radio. Listens to wired network traffic (ARP messages) and correlates it with a WLC-provided list of suspected rogue MAC addresses. |
| SE-Connect | No | Dedicated to RF spectrum analysis on all channels. Sends data to software like Cisco Spectrum Expert to find interference. |
| Bridge/Mesh | No | Acts as a dedicated bridge between sites (like outdoor bridge) or forms a wireless mesh. |
| Flex+Bridge | No | Combines Bridge/Mesh mode with FlexConnect (locally forwards traffic if WLC connection is lost). |
WLC Deployment Models
Applies only to Split-MAC (Lightweight AP) architectures.
| Deployment Model | Description | AP Capacity | Use Case |
|---|---|---|---|
| Unified WLC | Dedicated hardware appliance deployed in a central network location. | ~6,000 APs | Large enterprise campuses. |
| Cloud-based WLC | VM running on a server, typically in a private cloud/data center. (Note: APs are still lightweight, not cloud-based APs). | ~3,000 APs | Medium/Large networks needing virtualized control. |
| Embedded WLC | WLC software integrated directly into a network switch. | ~200 APs | Smaller campuses. |
| Cisco Mobility Express | WLC functionality integrated within one of the APs itself. Other APs build internal CAPWAP tunnels to it. | ~100 APs | Small branch offices. |
Things to note:
- Common Misconception: Do not confuse Cloud-based APs (Meraki, where data bypasses the cloud) with a Cloud-based WLC (where lightweight APs tunnel data to a VM in a private cloud).
- Port Trunking: Autonomous APs require trunk ports on the switch because they map SSIDs to VLANs locally. Lightweight APs require access ports because all traffic is encapsulated in CAPWAP tunnels to the WLC (which handles the VLAN mapping via a trunk).
- DTLS vs TLS: DTLS (used for CAPWAP data encryption) operates over UDP, whereas standard TLS operates over TCP.
Commands Summary
No specific IOS CLI commands were provided in this transcript.