software layer provides a support framework for drivers that includes
handling beacon miss events in station mode.
Drivers can dispatch beacon miss events that are recognized in hardware or
can detect beacon miss if the driver dispatches received beacon frames
through the normal receive path.
Software beacon miss support is especially useful when multiple vaps
are operating and any hardware beacon miss support is not available
(e.g. operating as an access point together with one or more station
Drivers should dispatch beacon miss events recognized in the driver with
This causes some number of ProbeRequest frames to be sent to the
access point to check if the association is still alive.
If no response is received and roaming mode is set to
will try to re-associate and if that fails
trigger a scan to look for the access point or another suitable AP.
state machine is being operated manually, e.g. by
then applications are notified of the state change and are responsible
for handling the work of scanning for a new access point.
The number of beacon miss events (without a ProbeResponse) is user
settable with the
Software beacon miss detection is enabled per-vap by setting the
Typically this is done when a vap is setup
option is supplied to the clone operation.
But drivers may also force this when they know they need help detecting
When beacon miss is detected in software the event is dispatched without
Note that software beacon miss handling is not limited to station mode;
it can be used in any operating mode where beacons from a peer station