Lines Matching full:supplicant
27 // A WiFi device interacts with a real device through WPA Supplicant.
28 // Wifi::Start() creates a connection to WPA Supplicant, represented by
32 // WPA Supplicant, which identifies them by a "path". The WiFi object maintains
38 // Supplicant. It is the job of WPA Supplicant to select a BSS (aka
42 // 1. The WiFi device sends AddNetwork to WPA Supplicant, which returns a
46 // received in 1, to WPA Supplicant, which begins the process of associating
50 // 3. During association to an EAP-TLS network, WPA Supplicant can send
54 // 4. When association is complete, WPA Supplicant sends a PropertiesChanged
59 // Some key things to notice are 1) WPA Supplicant does the work of selecting
71 // WPA Supplicant's PropertiesChanged signal communicates changes in the state
72 // of WPA Supplicant's current service. This state is stored in
73 // |supplicant_state_| and reflects WPA Supplicant's view of the state of the
76 // Supplicant signals the new state to be "completed", then the WiFiService
78 // reliable because WPA Supplicant may coalesce state changes in quick
84 // shill/dbus_proxies/supplicant-interface.xml, and the WPA Supplicant's
110 #include "shill/supplicant/supplicant_event_delegate_interface.h"
243 // Remove all networks from WPA supplicant.
355 // Delay between scans when supplicant finds "No suitable network".
377 // supplicant and a default.
435 // result from a scan. This works because supplicant sends all BSSAdded
513 // Suppresses manager auto-connects and flushes supplicant BSS cache, then
515 // ensure that shill and supplicant do not use stale information to launch
628 // Endpoint (BSS, in supplicant parlance).
645 // Indicates that we should flush supplicant's BSS cache after the
660 // Executes when WPA supplicant reports that a scan has failed via a ScanDone
666 // to supplicant.
