Wireless and CAPWAP
Wireless support gives netverdict enough controller/AP behaviour for campus training scenarios: WLAN profiles, AP registration, client attachment, selected EAP flows, and CAPWAP-style control-plane state.
Support level
Section titled “Support level”| Area | Level | Notes |
|---|---|---|
| WLAN profiles | Behaviour model | SSID/security/profile configuration. |
| AP/controller state | Behaviour model | AP joins controller and receives profile intent. |
| CAPWAP | Behaviour model | Control-plane state and selected wire representation. |
| EAP | Partial | Selected EAP authentication outcomes. |
| RF physics | Not modelled | No signal propagation or channel interference simulation. |
Standards coverage
Section titled “Standards coverage”| Standard | Coverage | Notes |
|---|---|---|
| CAPWAP RFC 5415 | Partial | AP/controller control concepts. |
| IEEE 802.11 | Minimal | WLAN/client association concepts, not RF/MAC fidelity. |
| IEEE 802.1X/EAP | Partial | Auth outcomes for selected scenarios. |
Feature matrix
Section titled “Feature matrix”| Feature | Status | Notes |
|---|---|---|
| WLAN/SSID config | Supported | Profile and SSID state. |
| AP join | Behaviour model | AP/controller association. |
| Client association | Behaviour model | Client attaches to WLAN when policy permits. |
| EAP outcome | Partial | Deterministic auth result. |
| Mobility | Partial | Limited scenario support. |
| RF planning | Not modelled | No channel/signal/roaming physics. |
Vendor command matrix
Section titled “Vendor command matrix”| Command | IOS-style | WLC-style | Notes |
| --- | --- | --- |
| wlan NAME 1 SSID | Partial | Supported | WLAN profile. |
| ap name AP1 | Partial | Supported | AP identity. |
| show wireless client summary | Partial | Supported | Client state. |
| show ap summary | Partial | Supported | AP/controller state. |
Behaviour notes
Section titled “Behaviour notes”Wireless is intentionally a controller and policy model. It helps answer whether a configured WLAN should be available and whether a client is permitted to attach; it does not model RF airtime.
Examples
Section titled “Examples”Canonical example
configure terminalwlan USERS 10 USERS security wpa psk set-key ascii labpass no shutdownendshow ap summaryshow wireless client summaryVendor styles
IOS-style
wlan USERS 10 USERS security wpa psk set-key ascii labpass no shutdownWLC-style
wlan USERS 10 USERS security wpa psk set-key ascii labpass policy profile USERS-POLICY no shutdownJunos / VyOS note
Wireless controller syntax is vendor-specific and not mapped to Junos or VyOS as primary targets in the current model.
Known limits
Section titled “Known limits”RF propagation, roaming algorithms, 802.11 frame-level exchanges, spectrum contention, advanced EAP methods, and vendor-controller feature parity are not complete.