Skip to content

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.

AreaLevelNotes
WLAN profilesBehaviour modelSSID/security/profile configuration.
AP/controller stateBehaviour modelAP joins controller and receives profile intent.
CAPWAPBehaviour modelControl-plane state and selected wire representation.
EAPPartialSelected EAP authentication outcomes.
RF physicsNot modelledNo signal propagation or channel interference simulation.
StandardCoverageNotes
CAPWAP RFC 5415PartialAP/controller control concepts.
IEEE 802.11MinimalWLAN/client association concepts, not RF/MAC fidelity.
IEEE 802.1X/EAPPartialAuth outcomes for selected scenarios.
FeatureStatusNotes
WLAN/SSID configSupportedProfile and SSID state.
AP joinBehaviour modelAP/controller association.
Client associationBehaviour modelClient attaches to WLAN when policy permits.
EAP outcomePartialDeterministic auth result.
MobilityPartialLimited scenario support.
RF planningNot modelledNo channel/signal/roaming physics.

| 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. |

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.

Canonical example
configure terminal
wlan USERS 10 USERS
security wpa psk set-key ascii labpass
no shutdown
end
show ap summary
show wireless client summary

Vendor styles

IOS-style
wlan USERS 10 USERS
security wpa psk set-key ascii labpass
no shutdown
WLC-style
wlan USERS 10 USERS
security wpa psk set-key ascii labpass
policy profile USERS-POLICY
no shutdown
Junos / VyOS note

Wireless controller syntax is vendor-specific and not mapped to Junos or VyOS as primary targets in the current model.

RF propagation, roaming algorithms, 802.11 frame-level exchanges, spectrum contention, advanced EAP methods, and vendor-controller feature parity are not complete.