Wireless LAN Fundamentals: Standards, Architecture, and Basic Configuration

Wireless networking introduces an entirely different physical medium than the cabled Ethernet covered earlier in this series, along with its own terminology, architecture, and security considerations. This article explains the evolution of 802.11 wireless standards, covers the centralized wireless architecture built around wireless LAN controllers, and walks through configuring a basic wireless network with proper security.

Wireless LANWLC ArchitectureWPA3 Security

~5 دقیقه مطالعه · آخرین به‌روزرسانی ۱۹ شهریور ۱۴۰۵

Why Wireless Networking Requires Different Thinking

Everything covered earlier in this series about Ethernet, discussed in detail regarding cabling and switching, assumed a physical, shared or point-to-point medium. Wireless networking transmits over open radio frequency space instead, introducing challenges that wired networks never face: signal interference, coverage limitations, shared airtime contention among all nearby devices, and the inherent security risk of a medium anyone within range can potentially intercept.

The Evolution of 802.11 Standards

802.11a (1999):  5 GHz, up to 54 Mbps
802.11b (1999):  2.4 GHz, up to 11 Mbps
802.11g (2003):  2.4 GHz, up to 54 Mbps
802.11n (2009):  2.4/5 GHz, up to 600 Mbps (Wi-Fi 4)
802.11ac (2013): 5 GHz, up to several Gbps (Wi-Fi 5)
802.11ax (2019): 2.4/5/6 GHz, higher efficiency,
                 particularly in dense environments (Wi-Fi 6)

The two available frequency bands offer a fundamental trade-off: 2.4 GHz travels farther and penetrates walls better, but has fewer non-overlapping channels and suffers more interference from other common devices; 5 GHz (and newer 6 GHz) offers more channels and less interference, but covers a shorter range with the same transmit power due to how higher frequencies attenuate over distance.

Autonomous Versus Centralized Wireless Architecture

Early wireless deployments used Autonomous Access Points, each independently configured and managed as a standalone device — functional for a handful of access points, but unmanageable at enterprise scale where dozens or hundreds of access points need consistent configuration and coordinated radio management.

Modern centralized architecture:

Wireless LAN Controller (WLC): centrally manages
  configuration, security policy, and radio
  frequency coordination for all connected APs

Lightweight Access Points (LAPs): receive their
  configuration entirely from the WLC, handling
  only the actual radio transmission and reception,
  with minimal independent intelligence

CAPWAP (Control and Provisioning of Wireless
Access Points): the protocol tunneling both control
  traffic and (often) client data traffic between
  each LAP and the central WLC

This centralized model, using lightweight access points controlled by a WLC, is the standard architecture in virtually all enterprise wireless deployments today, since it allows an administrator to manage hundreds of access points through a single management interface rather than individually configuring each one.

Key Wireless Terminology

SSID (Service Set Identifier): the network name
  broadcast by an access point, what users see
  when selecting a wireless network to join

BSS (Basic Service Set): one access point and
  all the clients associated with it

ESS (Extended Service Set): multiple access points
  sharing the same SSID, allowing a client to
  roam between them while remaining on the
  same logical wireless network

Roaming: a client transitioning its association
  from one access point to another as it physically
  moves, ideally without any noticeable interruption

Basic WLC Configuration Concepts

-- Conceptual WLC configuration workflow
-- (exact syntax varies by controller platform)

1. Configure a Dynamic Interface, mapping to
   a specific VLAN on the wired network

2. Create a WLAN, associating an SSID with:
   - the dynamic interface (which VLAN clients
     land on)
   - the security policy (WPA3, discussed below)
   - the radio bands the SSID is broadcast on

3. Apply an AP group or site-specific policy,
   determining which physical access points
   broadcast this particular SSID

This layered configuration model reflects the centralized architecture described above: rather than configuring each access point individually, an administrator defines the WLAN once on the controller, and it automatically propagates to every access point the policy applies to.

Wireless Security: From WEP to WPA3

Wireless security has evolved considerably since early standards, and using outdated security remains a common and serious vulnerability in networks that have not been updated.

WEP (Wired Equivalent Privacy): the original
  standard, now considered completely broken —
  crackable within minutes using widely available
  tools, should never be used under any circumstances

WPA (Wi-Fi Protected Access): an interim
  improvement over WEP, also now considered outdated

WPA2: introduced AES encryption, a genuine
  cryptographic improvement, widely deployed
  for over a decade, but vulnerable to certain
  known attacks against its handshake process

WPA3: the current standard, addressing WPA2's
  known weaknesses with a more robust handshake
  process (SAE) and mandatory stronger encryption,
  the recommended standard for any new deployment

Configuring WPA3 Security on a WLAN

-- Conceptual security configuration
WLAN Security Settings:
  Layer 2 Security: WPA3
  Authentication Key Management: SAE
  Encryption: AES (GCMP-256 for WPA3)

SAE (Simultaneous Authentication of Equals) replaces WPA2's vulnerable four-way handshake with a fundamentally more secure key exchange method, specifically designed to resist offline password-guessing attacks that were practical against WPA2's older handshake mechanism.

Verifying Wireless Client and Access Point Status

-- Conceptual verification commands
WLC# show ap summary

AP Name    Status    Radio Slots   Clients
AP-Floor1  Registered  2            14
AP-Floor2  Registered  2            9

WLC# show client summary

Client MAC          AP Name     SSID        Status
0050.56aa.1122       AP-Floor1   Corp-WiFi   Associated

These verification commands confirm the two most fundamental questions when troubleshooting wireless connectivity: are the access points themselves properly registered with the controller, and are specific clients successfully associating with the network — the wireless equivalent of confirming physical connectivity and MAC address table entries in wired troubleshooting, discussed earlier in this series.

Why Wireless Fluency Is Increasingly Essential

Wireless has become the primary access method for end-user devices in most modern enterprise environments, making the fundamentals covered in this article — frequency band trade-offs, the centralized WLC architecture, and modern WPA3 security — essential baseline knowledge for any network professional, not a specialized sideline separate from the wired networking concepts covered throughout the rest of this series.

نوشته و پژوهش‌شده توسط دکتر شاهین صیامی

مقالات مرتبط

Systematic Network Troubleshooting: A Methodology Tying Everything Together

Every protocol and technology covered throughout this series is only useful if a problem involving it can actually be diagnosed and fixed efficiently under real-world pressure. This article presents a systematic troubleshooting methodology built around the OSI layers, walks through applying it to a realistic connectivity problem, and shows how the specific verification commands covered throughout this entire series fit into a structured diagnostic process.

ادامه

NETCONF, YANG, and Python: Programmatic Network Configuration at Scale

The REST APIs and JSON/YAML formats covered earlier in this series represent one approach to network automation, but NETCONF and YANG provide a more structured, standards-based alternative purpose-built for network device configuration. This article explains what distinguishes NETCONF from a simple REST API, covers how YANG models define exactly what configuration data looks like, and walks through using Python to programmatically interact with network devices.

ادامه

IPsec VPN Fundamentals: Securing Traffic Across Untrusted Networks

Connecting two sites across the public internet exposes traffic to interception unless it is properly encrypted, and IPsec provides the standard framework for building secure, authenticated tunnels between sites. This article explains the two-phase IKE negotiation process, covers the distinction between AH and ESP protocols, walks through configuring a basic site-to-site IPsec VPN, and covers essential verification commands.

ادامه

MPLS Fundamentals: Label Switching Explained

Traditional IP routing requires every router along a path to perform a full routing table lookup on every packet, but MPLS takes a fundamentally different approach by making that forwarding decision once and attaching a simple label that every subsequent router can use instead. This article explains the core label-switching concept, walks through how the Label Distribution Protocol builds the label forwarding tables that make this possible, and covers the practical benefits MPLS provides in real provider networks.

ادامه

BGP Route Reflectors and Confederations: Scaling iBGP Beyond Full Mesh

The iBGP full-mesh requirement, briefly mentioned earlier in this series, becomes a serious scaling problem as an autonomous system grows, requiring a number of sessions that increases quadratically with router count. This article explains exactly why full mesh does not scale, walks through how route reflectors solve this by relaxing BGP's normal route-propagation rules, and covers confederations as an alternative approach that divides a single AS into smaller sub-autonomous systems.

ادامه

OSPF Area Types Deep Dive: Stub, Totally Stubby, and NSSA

Multi-area OSPF, covered earlier in this series, already reduces database size by separating a network into areas, but OSPF offers further specialized area types that reduce routing table size even more aggressively by filtering out unnecessary external routes entirely. This article explains the LSA types that must be suppressed to create each specialized area type, walks through configuring stub, totally stubby, and not-so-stubby areas, and covers the specific trade-offs each design choice involves.

ادامه