WLAN forwarding, roaming and application architecture
Trace the client’s actual path
A wireless service includes the client, AP radio, local switching or tunnel path, authentication, IP services and destination application. Controller-based, distributed and cloud-managed architectures divide management/control and forwarding responsibilities differently. Cloud management does not universally mean every client packet crosses the public cloud. Local forwarding can preserve some service during a management outage, but actual identity, addressing and policy dependencies still matter. Treat supported behavior as a design condition rather than a blanket brand promise.
Separate connection stages
Discovery, association, authentication, key establishment, authorization, address assignment and application access are distinct stages. A client seeing an SSID does not establish any later success. An SSID name is not an encryption algorithm or a security boundary by itself. VLAN and role mappings must align with actual upstream provisioning and effective policy. A successful DHCP lease does not prove that DNS, a required application or the return route is healthy.
Model roaming and application continuity
Roaming decisions depend on client and network behavior. Neighbor information, transition suggestions and fast-transition mechanisms have different roles; they do not guarantee every client roams at one signal threshold or interruption duration.802.11r supports relevant fast BSS transition, while802.11k and802.11v supply different assistance/information functions. Supported security methods and client capabilities must align. Preserving a radio association is different from preserving an application session across a changed IP or service path.
Handle competing traffic intentionally
WMM access categories provide differentiated contention behavior rather than a deterministic promise that voice always wins every transmission. Wired markings, mapping and queues also affect the end-to-end application. Multicast, broadcast and power-saving behavior can consume airtime or introduce delivery delay under the actual configuration. A good design checks both representative client experience and the infrastructure dependencies. These chapters share genuine conceptual foundations across levels while making no claim of full expert difficulty or a complete official blueprint. No association, roaming test, forwarding change or application transaction is performed by the written exercise.