7.1 Stations, BSS, ESS and the Distribution System

Harborline Logistics runs a 200,000-square-foot warehouse. Handheld scanners, forklift tablets, label printers, and a few supervisor laptops all join a network named HL-Warehouse. Walk the floor and it feels like one Wi-Fi network. Capture frames and a different picture appears: every access point uses a different BSSID, and the Ethernet switches behind those APs are doing the work IEEE 802.11 calls the Distribution System (DS).

This section teaches the service-set vocabulary that Domain 3 expects you to use without mixing up names. The identifiers people see (SSID) are not the identifiers radios use (BSSID). The device people call a “client” is only one kind of station. Independent OpenExamPrep material here is study teaching from OpenExamPrep, not a claim of sponsorship by CWNP or IEEE.

Station (STA)

In 802.11, a station (STA) is any device that implements an 802.11 MAC and an 802.11 PHY. That definition includes access points and clients. An AP is an AP STA. A scanner, phone, or laptop is a non-AP STA. If an exam stem says “STA,” do not translate it as “client only.”

STAs share the wireless medium, run CSMA/CA, and exchange 802.11 frames. A STA does not have to be a user endpoint. A wireless bridge, a mesh node, and Harborline’s aisle AP are STAs in the IEEE sense. The AP is special because it also offers DS services: it is the wireless edge that can move MSDUs into and out of the Distribution System.

Harborline’s floor scanners are non-AP STAs. Each aisle AP is an AP STA that creates a BSS, beacons a BSSID, and accepts association. Until you can name both roles as STAs, later MAC-address questions will feel arbitrary.

Infrastructure BSS

The Basic Service Set (BSS) is the atomic 802.11 topology. In infrastructure mode, one AP plus the non-AP STAs associated to it form an infrastructure BSS. The AP is the hub. Client-to-client traffic typically goes to the AP and then onward, rather than STA-to-STA on the air. Direct-link extras exist in the wider standard; CWNA-depth infrastructure BSS still centers on the AP.

The geographic coverage of that BSS is the Basic Service Area (BSA). In an empty field the BSA looks like a circle. Inside Harborline’s steel racking it looks like a lumpy blob shaped by metal, pallets, people, and forklifts. Two BSAs should overlap enough for a roam, not so much that co-channel airtime collapses—that design work lives in later domains. Here, remember that a BSS is a membership set, and a BSA is the RF footprint of that set.

A non-AP STA becomes a member of an infrastructure BSS by authenticating and associating with the AP (the frame exchange is the next chapter). Until association succeeds, the STA can hear beacons but does not have data service through that BSS.

One physical AP radio can host several virtual APs (VAPs). Each VAP is a distinct BSS with its own BSSID, even when they share one radio and one channel. Harborline might advertise HL-Warehouse for scanners and HL-Guest for visitors from the same AP hardware: two BSSIDs, two BSSs, two membership lists.

SSID versus BSSID

The SSID (Service Set Identifier) is what users pick. It is not a Layer-2 address. Two buildings can reuse a name; the name does not identify a specific radio.

The BSSID (Basic Service Set Identifier) does. In infrastructure mode, the BSSID is typically the MAC address of the AP radio that operates that BSS. Beacons, Probe Responses, and data frames carry that BSSID so a STA can tell “this AP” from “the AP two aisles over,” even when both strings say HL-Warehouse.

Exam trap: SSID and BSSID are not interchangeable. Same SSID with different BSSIDs is the normal multi-AP ESS. The same BSSID on two APs would be a misconfiguration or a spoof. In an IBSS, there is no AP radio to donate a MAC, so the BSSID is randomly generated (locally administered) by the STA that starts the ad hoc set.

Extended Service Set (ESS)

An Extended Service Set (ESS) is one or more infrastructure BSSs interconnected by a Distribution System so they appear as a single network to LLC. In practice: multiple APs, same SSID, different BSSIDs, one roaming domain.

Harborline’s aisle APs all beacon HL-Warehouse. A forklift tablet associated to AP-Aisle-1 (BSSID …:01) can roam to AP-Aisle-12 (BSSID …:0C) without changing the name the user selected. From the IP stack’s view it is still “the warehouse WLAN.” From 802.11’s view the STA left one BSS and joined another.

Roaming is not automatic magic. The STA must reassociate (or use a fast-roam method taught later). The ESS is the architecture that makes that move possible while keeping one network identity. A single-AP home router is still an ESS of one BSS. “ESS” does not require a dozen APs; it requires infrastructure BSS(s) plus a DS. The interesting exam case is the multi-AP ESS Harborline runs.

If Harborline gave every AP a unique SSID (HL-Aisle-1, HL-Aisle-12), users would see many networks and roaming would break. If every AP cloned one BSSID, STAs could not tell which radio they were talking to. Correct ESS design: one SSID, many BSSIDs, one DS.

Independent BSS (IBSS)

An IBSS is ad hoc 802.11: STAs communicate directly with no AP and no DS. Two engineers at Harborline’s loading dock who form a temporary laptop-to-laptop link are in an IBSS. There is no infrastructure BSS, no AP-donated BSSID, and no Ethernet DS carrying 802.11 distribution service.

IBSS is useful for a pop-up peer network. It is a poor fit for a warehouse that needs roaming, centralized policy, and wired servers. Do not call an infrastructure BSS an IBSS. The letter I means Independent, not Infrastructure.

Distribution System (DS) and DSM

The Distribution System (DS) interconnects BSSs and moves frames between STAs that are not in the same BSS—including frames that must reach a wired server. The AP is the STA’s portal into the DS.

The Distribution System Medium (DSM) is the medium the DS uses. At Harborline, the DSM is Ethernet: each AP uplink hits an access switch, those switches hit distribution, and scanners reach WMS servers on the wired LAN. That wired fabric is the DS/DSM the 802.11 architecture assumes in a classic ESS.

The DS can also be wireless (WDS / wireless bridging / some mesh backhauls). Then the DSM is radio, and four-address frames appear in section 7.3. Harborline’s design choice is the common enterprise one: wired Ethernet DS, wireless only for the last hop to STAs.

What the DS does on this floor:

1. Delivers a frame from a scanner in aisle 1 to a wired WMS host.
2. Delivers a frame from that host back to the scanner through the correct AP.
3. After a roam, delivers the next frames through AP-Aisle-12 instead of AP-Aisle-1.

The DS is not “the SSID.” It is the interconnection system behind the APs. Integration with a non-802.11 LAN happens at a portal function—in a simple warehouse AP, that is the AP’s wired side bridging 802.11 MSDUs onto 802.3.

Harborline three-AP walkthrough

All three uplinks are 802.3 into the warehouse switching fabric (DSM). Together they are one ESS named HL-Warehouse. A scanner associated to AP-Aisle-1 has a wireless hop to that AP’s BSSID. When the frame is destined to the WMS server, the AP forwards it onto the Ethernet DS. When the scanner drives toward aisle 12, it hears a different BSSID, roams, and the DS now uses AP-Aisle-12 as the wireless edge.

Topology comparison

Keep the exam vocabulary as roles, not product names. Controller, cloud AP, and CAPWAP tunnel are implementation choices that still sit on this IEEE model: STAs, BSSs identified by BSSIDs, an SSID shared across an ESS, and a DS/DSM that ties the APs together.