Difference between revisions of "Wpa supplicant"
Jump to navigation
Jump to search
(→Logs) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* https://linux.die.net/man/5/wpa_supplicant.conf | * https://linux.die.net/man/5/wpa_supplicant.conf | ||
| − | * [[wpa_supplicant.conf]]: https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf | + | * <code>[[wpa_supplicant.conf]]</code>: https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf |
* <code>[[journalctl -u]] wpa_supplicant</code> | * <code>[[journalctl -u]] wpa_supplicant</code> | ||
| − | + | * <code>[[git clone]] git://w1.fi/srv/git/hostap.git</code> | |
| + | |||
| + | == Logs == | ||
Nov 30 08:58:32 SERVER [[wpa]]_supplicant[511]: wlp6s0: [[AP-STA-DISCONNECTED]] 56:a4:72:cc:b2:xx | Nov 30 08:58:32 SERVER [[wpa]]_supplicant[511]: wlp6s0: [[AP-STA-DISCONNECTED]] 56:a4:72:cc:b2:xx | ||
| − | |||
Nov 30 05:58:45 SERVER wpa_supplicant[511]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures | Nov 30 05:58:45 SERVER wpa_supplicant[511]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures | ||
| Line 15: | Line 16: | ||
Dec 01 11:10:25 SERVER wpa_supplicant[504]: wlp6s0: AP-STA-POSSIBLE-PSK-MISMATCH t0:32:99:99:d2:5c | Dec 01 11:10:25 SERVER wpa_supplicant[504]: wlp6s0: AP-STA-POSSIBLE-PSK-MISMATCH t0:32:99:99:d2:5c | ||
| − | + | [[AP-STA-CONNECTED]] | |
| − | AP-STA-CONNECTED | ||
== Related terms == | == Related terms == | ||
Latest revision as of 09:54, 21 April 2021
wpa_supplicant included in wpasupplicant package.
- https://linux.die.net/man/5/wpa_supplicant.conf
wpa_supplicant.conf: https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf
journalctl -u wpa_supplicant
Logs[edit]
Nov 30 08:58:32 SERVER wpa_supplicant[511]: wlp6s0: AP-STA-DISCONNECTED 56:a4:72:cc:b2:xx
Nov 30 05:58:45 SERVER wpa_supplicant[511]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures
Dec 01 11:10:25 SERVER wpa_supplicant[504]: wlp6s0: AP-STA-POSSIBLE-PSK-MISMATCH t0:32:99:99:d2:5c
AP-STA-CONNECTED
Related terms[edit]
See also[edit]
wpa_supplicant,wpa_supplicant.conf, Wpa supplicant authentication logs- Wi-Fi Protected Access (WPA), WPA Pairwise Transient Key (WPA PTK), wpa_supplicant, AP-STA-CONNECTED, WPA2, WPA3, wpa_cli, PTK
iw,iw list,iw event,iw wlan0 info,wpa_cli status|xxx|dump,wpa_supplicant, WPS, Wpa supplicant authentication logs, AP-STA-CONNECTED- Wi-Fi, WiFi 7, WiFi 6 (ax), WiFi 5 (ac), Wifi scanning,
iw, Wireless Network Hacking,airodump-ng,aireplay-ng, WPA, WPA2, WPA3,rfkill, iwlwifi, hostapd, Spatial Multiplexing Power Save (SMPS),wpa_cli, AirWatch, Wireless LAN controller, Wi-Fi 6, Mobile Hotspot, Wireless routers, 802.11ax, MIMO, aircrack-ng,netsh wlan
Advertising:
