Normally when I run wpa_supplicant I'll get some output like this: Successfully initialized wpa_supplicant ioctl[SIOCSIWAP]: Operation not permitted ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument wlan3: Trying to associate with 9c:3d:cf:fb:95:96 (SSID='Bell420' freq=2462 MHz) wlan3: Association request to the driver failed wlan3: Associated with 9c:3d:cf:fb:95:96 wlan3: Authentication with 9c:3d:cf:fb:95:96 timed out. ioctl[SIOCSIWAP]: Operation not permitted wlan3: CTRL-EVENT-DISCONNECTED bssid=9c:3d:cf:fb:95:96 reason=3 locally_generated=1 wlan3: WPA: 4-Way Handshake failed - pre-shared key may be incorrect The problem is it just keeps trying over and over. Is there a way I can tell wpa_supplicant to quit as soon as it gets an obvious error like wrong key? *I'm on an older embedded device with wpa_supplicant v2.1.* ---------- I wrote a workaround for monitoring wpa_supplicant for incorrect keys. Using grep on wpa_supplicant (with stdbuf based on Stéphane Chazelas' comment here ): # Create conf file with ssid and password wpa_passphrase "$ssid" "$password" > /etc/wpa_supplicant/wpa_supplicant.conf # If wifi key is wrong kill subshell subshell=$BASHPID (sudo stdbuf -o0 wpa_supplicant -Dwext -iwlan1 -c/etc/wpa_supplicant/wpa_supplicant.conf 2>&1 \ | grep -m 1 "pre-shared key may be incorrect" \ && kill -s PIPE "$subshell") & *Note: the above block is inside a subshell in a script.* It seemed to work initially but over time I found sometimes it would cause the whole script to fail when the password was fine. Other times it would work as expected. There must be a better way to do this. ---------- *Edit: Maybe I should be using wpa_cli here instead?*

When connecting to a WPA Enterprise access point, operating systems like iOS and macOS display the server certificate to the user if it has not been seen before. However, on Linux, using wpa_supplicant, this prompt does not appear. I have configured wpa_supplicant using a .conf file, but I do not get the server certificate. Is there any way to obtain the certificate when connecting to the AP on linux? This is one of the configurations I have used: network={ ssid="ssid" key_mgmt=WPA-EAP eap=PEAP identity="your.username@example.com" password="yourpassword" phase1="peapver=0" phase2="auth=MSCHAPV2" ca_cert="/etc/ssl/certs/your_CA_cert.pem" } And the usage of wpa_supplicant: sudo wpa_supplicant -i wlan0 -c /etc/tmp/network.conf -D nl80211 -dd

I'm using Fedora 31 on my Notebook. Everything works well, except for Fedora dropping the wifi connection after a while, making it necessary to reconnect to the network. Every few minutes after reconnecting the behaviour repeats itself. I have no idea what the reasons are for that. It often happens when I download files (putting "load" on the network) but sometimes also without any obvious reason. The problem first appeared under Fedora 30 and stayed after the upgrade to Fedora 31. Output from journalctl -b -u NetworkManager: -- Logs begin at Sun 2019-07-14 01:05:47 CEST, end at Sat 2019-11-16 23:42:15 CET. -- Nov 16 23:35:19 localhost.localdomain systemd: Starting Network Manager... Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8189] NetworkManager (version 1.20.6-1.fc31) is starting... (after a restart) Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8191] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) Nov 16 23:35:19 localhost.localdomain systemd: Started Network Manager. Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8260] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Nov 16 23:35:19 localhost.localdomain NetworkManager: [1573943719.8355] manager[0x5559cd8e80f0]: monitoring kernel firmware directory '/lib/firmware'. Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3382] hostname: hostname: using hostnamed Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3385] hostname: hostname changed from (none) to "localhost.localdomain" Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3390] dns-mgr[0x5559cd8cd240]: init: dns=default,systemd-resolved rc-manager=symlink Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3401] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.3/0000:05:00.0/ieee80211/phy0/rfkill2) (driver ath10k_pci) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: Wi-Fi hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3403] manager[0x5559cd8e80f0]: rfkill: WWAN hardware radio set enabled Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3479] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wifi.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3486] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-adsl.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3511] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-team.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3553] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-bluetooth.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3559] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-device-plugin-wwan.so) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3561] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3563] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3565] manager: Networking is enabled by state file Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3567] dhcp-init: Using DHCP client 'internal' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.20.6-1.fc31/libnm-settings-plugin-ifcfg-rh.so") Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3644] settings: Loaded settings plugin: keyfile (internal) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3838] device (lo): carrier: link connected Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3845] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3886] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3951] settings: (enp4s0): created default wired connection 'Kabelgebundene Verbindung 1' Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.3986] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4067] device (wlp5s0): driver supports Access Point (AP) mode Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4079] manager: (wlp5s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.4127] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:20 localhost.localdomain NetworkManager: [1573943720.7252] device (wlp5s0): set-hw-addr: set MAC address to 96:1B:95:D7:6D:B2 (scanning) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0023] modem-manager: ModemManager available Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0103] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] supplicant: wpa_supplicant running Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0157] device (wlp5s0): supplicant interface state: init -> starting Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0323] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0446] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0458] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0583] sup-iface[0x5559cd8fe130,wlp5s0]: supports 5 scan SSIDs Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0596] device (wlp5s0): supplicant interface state: starting -> ready Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0597] Wi-Fi P2P device controlled by interface wlp5s0 created Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0599] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0602] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0610] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0613] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.0631] sup-iface: failed to cancel p2p connect: P2P cancel failed Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3859] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3906] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3924] device (virbr0): Activation: starting connection 'virbr0' (dc059138-81a5-4d0a-bb5e-725c891ae6bf) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3935] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3947] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3976] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (d3fd587b-3b1e-418f-9fa9-dc52709be3e1) Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3980] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.3991] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4045] device (virbr0-nic): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4060] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4066] device (virbr0-nic): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4073] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4083] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4108] device (virbr0): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4127] device (virbr0-nic): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0): bridge port virbr0-nic was attached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4203] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4214] device (virbr0-nic): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4270] device (virbr0-nic): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4274] device (virbr0-nic): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4291] device (virbr0-nic): Activation: successful, device activated. Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4363] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external') Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0): bridge port virbr0-nic was detached Nov 16 23:35:21 localhost.localdomain NetworkManager: [1573943721.4374] device (virbr0-nic): released from master device virbr0 Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7709] policy: auto-activating connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7722] device (wlp5s0): Activation: starting connection 'Wifi-SSID' (b11eeab9-1cd2-40cf-b02e-719ac7a2cbcb) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7731] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7741] manager: NetworkManager state is now CONNECTING Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7777] device (wlp5s0): set-hw-addr: reset MAC address to 58:00:E3:D0:B5:0F (preserve) Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7887] device (wlp5s0): supplicant interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7889] device (p2p-dev-wlp5s0): supplicant management interface state: ready -> disabled Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7892] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7897] device (wlp5s0): Activation: (wifi) access point 'Wifi-SSID' has security, but secrets are required. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7898] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7901] sup-iface[0x5559cd8fe130,wlp5s0]: wps: type pbc start... Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7939] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7946] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7950] device (wlp5s0): Activation: (wifi) connection 'Wifi-SSID' has security, and secrets exist. No new secrets needed. Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'ssid' value 'Wifi-SSID' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7952] Config: added 'scan_ssid' value '1' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7953] Config: added 'bssid' value '54:67:51:B8:29:2A' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7954] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7955] Config: added 'psk' value '' Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (wlp5s0): supplicant interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.7982] device (p2p-dev-wlp5s0): supplicant management interface state: disabled -> inactive Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8098] device (wlp5s0): supplicant interface state: inactive -> scanning Nov 16 23:35:25 localhost.localdomain NetworkManager: [1573943725.8099] device (p2p-dev-wlp5s0): supplicant management interface state: inactive -> scanning Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5410] device (wlp5s0): supplicant interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5412] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5617] device (wlp5s0): supplicant interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.5618] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (wlp5s0): supplicant interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6162] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> associated Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (wlp5s0): supplicant interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.6367] device (p2p-dev-wlp5s0): supplicant management interface state: associated -> 4-way handshake Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7563] device (wlp5s0): supplicant interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (wlp5s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Wifi-SSID" Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7564] device (p2p-dev-wlp5s0): supplicant management interface state: 4-way handshake -> completed Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7651] device (wlp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.7656] dhcp4 (wlp5s0): activation: beginning transaction (timeout in 45 seconds) Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8962] dhcp4 (wlp5s0): state changed unknown -> bound Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8970] device (wlp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8993] device (wlp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.8995] device (wlp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9002] manager: NetworkManager state is now CONNECTED_LOCAL Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9017] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9018] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv4 routing and DNS Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9062] device (wlp5s0): Activation: successful, device activated. Nov 16 23:35:30 localhost.localdomain NetworkManager: [1573943730.9069] manager: startup complete Nov 16 23:35:31 localhost.localdomain NetworkManager: [1573943731.0336] manager: NetworkManager state is now CONNECTED_GLOBAL Nov 16 23:35:32 localhost.localdomain NetworkManager: [1573943732.0747] policy: set 'Wifi-SSID' (wlp5s0) as default for IPv6 routing and DNS Nov 16 23:35:34 localhost.localdomain NetworkManager: [1573943734.5034] agent-manager: req[0x5559cd9eb540, :1.201/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE The general journal shows the following before dropping the connection: Nov 16 23:40:40 localhost.localdomain systemd: Starting Tracker metadata database store and lookup manager... Nov 16 23:40:40 localhost.localdomain systemd: Started Tracker metadata database store and lookup manager. Nov 16 23:40:47 localhost.localdomain NetworkManager: [1573944047.5176] manager: NetworkManager state is now CONNECTED_SITE Nov 16 23:40:47 localhost.localdomain systemd: Starting Network Manager Script Dispatcher Service... Nov 16 23:40:47 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:40:47 localhost.localdomain audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:40:57 localhost.localdomain systemd: NetworkManager-dispatcher.service: Succeeded. Nov 16 23:40:57 localhost.localdomain audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 16 23:41:11 localhost.localdomain tracker-store: OK Nov 16 23:41:11 localhost.localdomain systemd: tracker-store.service: Succeeded. I also get the following error during the creation phase of the connection: Nov 16 23:43:08 localhost.localdomain systemd: Started Network Manager Script Dispatcher Service. Nov 16 23:43:08 localhost.localdomain kernel: wlp5s0: deauthenticating from 54:67:51:b8:29:2a by local choice (Reason: 3=DEAUTH_LEAVING) Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=54:67:51:b8:29:2a reason=3 locally_generated=1 Nov 16 23:43:08 localhost.localdomain wpa_supplicant: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6104] sup-iface[0x5559cd8fe130,wlp5s0]: connection disconnected (reason -3) Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6110] device (wlp5s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): canceled DHCP transaction Nov 16 23:43:08 localhost.localdomain NetworkManager: [1573944188.6136] dhcp4 (wlp5s0): state changed bound -> done Nov 16 23:43:08 localhost.localdomain wpa_supplicant: wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=DE

I’m trying to manage my wireless LAN interface using wpa_supplicant on my i.MX8 running Yocto Scarthgap. I can scan for available networks and connect successfully using the wpa_cli utility. However, when I try to save the current network configuration to the .conf file to persist it, wpa_supplicant fails to start on reboot due to an incorrect file format. Steps I followed before reboot to connect to an AP

> add_network
0
CTRL-EVENT-NETWORK-ADDED 0

> > set_network 0 ssid "MyNetwork"
OK
> set_network 0 psk "MyPassPhrase"
OK
> enable_network 0
OK
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
Trying to associate with SSID 'MyNetwork'
.....
CTRL-EVENT-CONNECTED - Connection to xxxxxx completed [id=0 id_str=]

> > save_config
OK
> quit

This is what my .conf file in /etc/wpa_supplicant/wpa_supplicant-wlan0.conf looks like after I run save_config .

ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1
filter_ssids=1
ignore_old_scan_res=1

network={
	ssid="MyNetwork"
	psk=*
}

On reboot systemd failed to start wpa_supplicant service

root@imx8qxp:~# journalctl -xe -u wpa_supplicant@wlan0.service 
Jul 09 16:03:46 imx8qxp systemd: Started WPA supplicant daemon (interface-specific version). 
-- Subject: A start job for unit wpa_supplicant@wlan0.service has finished successfully 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- A start job for unit wpa_supplicant@wlan0.service has finished successfully. 
--  
-- The job identifier is 100. 
Jul 09 16:03:46 imx8qxp systemd: wpa_supplicant@wlan0.service: Main process exited, code=exited, status=255/EXCEPTION 
-- Subject: Unit process exited 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- An ExecStart= process belonging to unit wpa_supplicant@wlan0.service has exited. --  -- The process' exit code is 'exited' and its exit status is 255. 
Jul 09 16:03:46 imx8qxp systemd: wpa_supplicant@wlan0.service: Failed with result 'exit-code'. -- Subject: Unit failed 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- The unit wpa_supplicant@wlan0.service has entered the 'failed' state with result 'exit-code'.

On further investigation by trying to start wpa_supplicant manually

root@imx8qxp:~# wpa_supplicant -B -dd -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
Line 9: Invalid PSK '*'.
Line 9: failed to parse psk '*'.
Line 10: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant-wlan0.conf'.

I did try to manually generate the passphrase using the command wpa_passphrase SSID PASSWORD > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf and there were no issues with it after reboot. I get this error only when trying to save network config from wpa_cli. I also tried recreating it on an ubuntu 24 machine but could not successfully reproduce the issue. While the obvious solution is to use wpa_passphrase directly, I'm interested in understanding why this issue occurs in the first place. Despite searching online, I haven’t come across anyone experiencing this exact problem. Could it be that I’m missing a step when saving the network configuration using wpa_cli? What causes this behaviour, and is there a correct way to persist network settings without manually trying to write to the file? I don't prefer using the wpa_passphrase command because I ultimately want to use wpa_ctrl C APIs and would not prefer messing with the .conf files in the application layer.

I've suddenly realized wpa_supplicant is spamming my system logs with these messages:

Sep 02 08:07:17 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=648500
Sep 02 08:07:20 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=648500
Sep 02 08:07:23 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-58 noise=9999 txrate=648500
Sep 02 08:07:26 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=648500
Sep 02 08:07:29 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=432300
Sep 02 08:07:32 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=432300
Sep 02 08:07:35 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=576400
Sep 02 08:07:38 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=576400
Sep 02 08:07:41 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=576400
Sep 02 08:07:44 elite wpa_supplicant: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-63 noise=9999 txrate=576400

I want this to stop. My WiFi works perfectly but these seemingly debug messages drive me insane and generate over 2GB of disk writes daily. For the past three days:

journalctl | grep CTRL-EVENT-SIGNAL-CHANGE | wc -l
24500

I'm using fully updated Fedora 40 with NetworkManager.

**i'm using #*Void_linux*. Before i was using *Ethernet*. I've never used *wireless* before...** # ip link show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp12s0: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether d4:be:d9:71:98:bc brd ff:ff:ff:ff:ff:ff 3: wwp0s29u1u6i6: mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 06:0a:7e:d4:64:b6 brd ff:ff:ff:ff:ff:ff **so i created a config file here :** # touch /etc/wpa_supplicant/wpa_supplicant-wwp0s29u1u6i6.conf # vi /etc/wpa_supplicant/wpa_supplicant-wwp0s29u1u6i6.conf edition : 1. ctrl_interface=/run/wpa_supplicant 2. update_config=1 (save & exit) **and after done editing, i applied my wifi name and password into config file.** # wpa_passphrase >> /etc/wpa_supplicant/wpa_supplicant-wwp0s29u1u6i6.conf # vi /etc/wpa_supplicant/wpa_supplicant-wwp0s29u1u6i6.conf ctrl_interface=/run/wpa_supplicant update_config=1 network={ ssid="Wifi" #psk="01632413440" psk=84195e97272a26e42479c32d36e10eef82f347530aba8bd6ec2bc65dbe2fadd8 } **Here last cmnd,** # wpa_supplicant -B -i wwp0s29u1u6i6 -c /etc/wpa_supplicant/wpa_supplicant-wwp0s29u1u6i6.conf **and after that i got all this Errors output :** Successfully initialized wpa_supplicant nl80211: Driver does not support authentication/association or connect commands nl80211: deinit ifname=wwp0s29u1u6i6 disabled_11b_rates=0 wwp0s29u1u6i6: Failed to initialize driver interface **Here i don't know what to do ? Please give me instruction, ***Thank you* :)**

i have followed posts on Network Manager looping to connect to enterprise networks and coming back again and again asking for logon/password. the answer seems to be to use wpa_supplicant. i did a log file extract to confirm the process and got ...supplicant interface state: disconnected -> interface_disabled... there is a directory at /etc/wpa_supplicant, but there is no wpa_supplicant config file. the only files listed are action_wpa.sh functions.sh ifupdown.sh i guess that there are a few things i need to do? some perspective here: i am just trying to learn python, using an excellent on-line course from 'degreed' at work and doing the exercises on an old 32bit laptop running mx-linux and a compatible 32bit version of PyCharm Community Edition. my knowledge of network stuff can't fill the bottom of a thimble. so feel free to assume i haven't found the beginning of the string on this issue with logging in. any suggestions at starting points would be appreciated. thanks, ron ron@9-LPTOP:~ $ sudo journalctl -fu NetworkManager [sudo] password for ron: -- Journal begins at Tue 2023-01-24 14:43:06 EST. -- Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.0956] device (wlan0): supplicant interface state: disconnected -> interface_disabled Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.0957] modem-manager: ModemManager no longer available Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.1027] device (wlan0): supplicant interface state: interface_disabled -> disconnected Jan 24 14:55:54 9-LPTOP systemd: Stopping Network Manager... Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.5312] caught SIGTERM, shutting down normally. Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.5338] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed') Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.5468] device (wlan0): set-hw-addr: reset MAC address to 00:19:D2:05:A7:9D (unmanage) Jan 24 14:55:54 9-LPTOP NetworkManager: [1674590154.6549] exiting (success) Jan 24 14:55:54 9-LPTOP systemd: NetworkManager.service: Succeeded. Jan 24 14:55:54 9-LPTOP systemd: Stopped Network Manager.

nmcli output (among other items):

p2p-dev-wlp1s0: disconnected
        "p2p-dev-wlp1s0"
        wifi-p2p, hw

How can I remove this p2p-dev-wlp1s0 device? It's used for wireless peer-to-peer connections but I don't need it. I tried through wpa_supplicant.conf but no difference. I think it's created by network-manager. ___ The system runs on Debian 12 bookworm. Perhaps on other distros with different options on the compilation of Network Manager, there may be other behaviours.

I'm hosting a hotspot from my PC, which has a wired internet connection and a wifi adapter. The OS is Fedora 40, using Network Manager and wpa_supplicant. I have 3 wifi devices which are able to connect to this hotspot and use the internet. I want to know what "mode" each device chose to connect using (by which I mean cipher suites/encryption techniques = WPA/WPA2 & TKIP/AES/CCMP). How do I query this information? My router seems to know this information just fine and shows it up in its web pages, now I want to be able to pull up the same info on my Linux PC. hostapd does not seem to be installed, so I'm wary of installing it to use hostapd_cli because it might disrupt whatever is currently running. wpa_cli refuses to run because it can't connect to the running instance [wpa_cli is now running after enabling its control socket](https://www.jfcarter.net/~jimc/documents/bugfix/34-wpa_cli.html) , but I can't tell how to ask it for this information. Background: I'm trying to debug some wifi connection issues with an IoT device, which is happily connecting to a hotspot hosted by my PC but not to my network hosted from the router device. I suspect an encryption issue.

After a reinstall of Fedora Linux Asahi Remix 41, I am unable to connect to my school network (essentially EDUROAM but with different a username format, and it only supports TLS v1.0). wpa_supplicant says:

OpenSSL: Certificate Policy 2.16.840.1.114413.1.7.23.1
OpenSSL: Certificate Policy 2.23.140.1.2.1
wlp1s0f0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/CN=*.ykpaoschool.cn' hash=50cf9ba1cb6ecb72b702a01c4a4cb44118d552c12c50fd973214e75404eec0ec
wlp1s0f0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:*.ykpaoschool.cn
wlp1s0f0: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:ykpaoschool.cn
TLS: tls_verify_cb - preverify_ok=1 err=20 (unable to get local issuer certificate) ca_cert_verify=0 depth=0 buf='/CN=*.ykpaoschool.cn'
EAP: Status notification: remote certificate verification (param=success)
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3/TLS read server certificate
OpenSSL: RX ver=0x301 content_type=22 (handshake/server key exchange)
OpenSSL: TX ver=0x301 content_type=256 (TLS header info/)
OpenSSL: TX ver=0x301 content_type=21 (alert/)
SSL: (where=0x4008 ret=0x250)
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error
EAP: Status notification: local TLS alert (param=internal error)
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in error
OpenSSL: openssl_handshake - SSL_connect error:03000098:digital envelope routines::invalid digest
OpenSSL: pending error: error:0A080006:SSL routines::EVP lib
SSL: 7 bytes pending from ssl_out
SSL: Using TLS version TLSv1
SSL: Failed - tls_out available to report error (len=7)
SSL: 7 bytes left to be sent out (of total 7 bytes)
EAP-PEAP: TLS processing failed
EAP: method process -> ignore=FALSE methodState=DONE decision=FAIL eapRespData=0xaaab3fef3eb0
EAP: EAP entering state SEND_RESPONSE
EAP: EAP entering state IDLE
EAPOL: SUPP_BE entering state RESPONSE
EAPOL: txSuppRsp
TX EAPOL: dst=94:9b:2c:f1:34:b1
EAPOL: SUPP_BE entering state RECEIVE
l2_packet_receive: src=94:9b:2c:f1:34:b1 len=8
wlp1s0f0: RX EAPOL from 94:9b:2c:f1:34:b1 (encrypted=-1)
EAPOL: Received EAP-Packet frame
EAPOL: SUPP_BE entering state REQUEST
EAPOL: getSuppRsp
EAP: EAP entering state RECEIVED
EAP: Received EAP-Failure
EAP: Status notification: completion (param=failure)
EAP: EAP entering state FAILURE
wlp1s0f0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
EAPOL: SUPP_PAE entering state HELD
EAPOL: Supplicant port status: Unauthorized
nl80211: Set supplicant port unauthorized for 94:9b:2c:f1:34:b1
EAPOL: SUPP_BE entering state RECEIVE
EAPOL: SUPP_BE entering state FAIL
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed - result=FAILURE
wlp1s0f0: Setting authentication timeout: 2 sec 0 usec
nl80211: Drv Event 48 (NL80211_CMD_DISCONNECT) received for wlp1s0f0
nl80211: Disconnect event
wlp1s0f0: Event DEAUTH (11) received
wlp1s0f0: Deauthentication notification
wlp1s0f0:  * reason 23 (IEEE_802_1X_AUTH_FAILED)
Deauthentication frame IE(s) - hexdump(len=0): [NULL]
wlp1s0f0: CTRL-EVENT-DISCONNECTED bssid=94:9b:2c:f1:34:b1 reason=23
wlp1s0f0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="STUWIRELESS" auth_failures=1 duration=10 reason=AUTH_FAILED
wlp1s0f0: Auto connect enabled: try to reconnect (wps=0/0 wpa_state=6)

dmesg:

[ 1533.442699] net_ratelimit: 125 callbacks suppressed
[ 1533.442708] ieee80211 phy0: brcmf_p2p_set_firmware: failed to update device address ret -52
[ 1533.443311] ieee80211 phy0: brcmf_p2p_create_p2pdev: set p2p_disc error
[ 1533.443316] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp1s0f type 10 failed: err=-52
[ 1533.538847] brcmfmac: brcmf_msgbuf_delete_flowring: timed out waiting for txstatus
[ 1534.525047] ieee80211 phy0: brcmf_set_key_mgmt: get okc_enable failed (-52)
[ 1543.347249] brcmfmac: brcmf_msgbuf_delete_flowring: timed out waiting for txstatus
[ 1543.445268] brcmfmac: brcmf_msgbuf_delete_flowring: timed out waiting for txstatus
[ 1547.071226] ieee80211 phy0: brcmf_fweh_call_event_handler: no interface object
[ 1547.074547] ieee80211 phy0: brcmf_p2p_set_firmware: failed to update device address ret -52
[ 1547.074832] ieee80211 phy0: brcmf_p2p_create_p2pdev: set p2p_disc error
[ 1547.074835] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp1s0f type 10 failed: err=-52
[ 1548.111938] ieee80211 phy0: brcmf_set_key_mgmt: get okc_enable failed (-52)
[ 1548.411429] brcmfmac: brcmf_msgbuf_delete_flowring: timed out waiting for txstatus
[ 1559.760149] ieee80211 phy0: brcmf_set_key_mgmt: get okc_enable failed (-52)
[ 1596.969459] ieee80211 phy0: brcmf_set_key_mgmt: get okc_enable failed (-52)

wpa_supplicant config:

ap_scan=1
mac_addr=0
# means use permanent mac address, as my school requires us to not use random mac addresses

network={
        ssid="STUWIRELESS"
        scan_ssid=1
        key_mgmt=WPA-EAP
        eap=PEAP
        anonymous_identity="s22537"
        identity="s22537"
        password="redacted"
        phase1="tls_disable_tlsv1_0=0 tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1 tls_disable_tlsv1_3=1"
        # because they only support tls v1.0
        phase2="auth=MSCHAPV2"
        priority=10
}

I got a Wifi7 card running on Debian per my Q&A , the card is based on Intel's BE200NGW chip. Despite Multi Link Operation being enabled on the Wifi7 router, the Debian machine running kernel 6.12.12 connects to the router only on one band (2.4 or 5GHz). For comparison, Windows 11 uses this card in Wifi7 mode. Modules loaded:

$ lsmod | grep iwlwifi
iwlwifi               581632  1 iwlmvm
cfg80211             1392640  6 ath9k_common,iwlmvm,ath9k,ath,iwlwifi,mac80211

I've looked into iw settings but am yet to fully understand them. However, I also looked at NetworkManager 802.11 wireless specs . I've found nothing in there confirming that NetworkManager is Wifi7 ready, i.e. that it supports simultaneous connections to the same SSID on different bands. Should I just wait until Wifi 7 features are fully supported across network stack, or is there anything I can change in settings or modules loaded? Update 2025-02-23 ----------------- Prompted by *grawity*'s comments, I have: - checked wpa_supplicant version - it's 2.10 (I'm on Debian testing) - checked authentication protocol used by NetworkManager: it was WPA2. Recalling that WPA3 is required for 6GHz, I've changed this setting to WPA3 Personal. Result: the card now uses 6GHz band with link rate approx 1.4Gbps, which is already an improvement over my home's gigabit Ethernet. I wonder why NM required a manual intervention to use WPA3. - in pursuit of MLO, I modified wpa_supplicant.service unit by adding -Dnl80211 to its startup options. The original setup did not use any -D directives. I wanted to ensure the Wireless Extensions driver was not used as is doesn't support Wifi7. However, this did not enable MLO, so I must have been on nl80211 already before.

OS: Ubuntu 24.04 Kernel: 6.11.0-17-generic CPU: AMD Ryzen 7 7700 8-Core Processor I have a TP-Link TX20U plus that is able to detect my network after I have loaded it with the driver taken from https://github.com/lwfinger/rtl8852au . However, I am stuck in a loop in which NetworkManager just constantly prompts me for the WiFi password. Trying to connect by using nmcli just gives me this vague message. Error: Connection activation failed: Secrets were required, but not provided. Here's the NetworkManager log https://pastebin.com/BBxXicEy , which shows that the adapter tried to establish connection but failed. Since the adapter can detect the WiFi, I would think that it's unlikely an issue with the hardware nor the driver. Which makes me suspect that something is wrong with the wifi backend. By default, wpa-supplicant is used. Switching the backend to iwd did not fix the situation either https://pastebin.com/dJZa7mDG .

I have not used wpa_supplicant before, so am confused as to whether a valid connection is being made. I used wpa_passphrase to get a psk and made that output my wpa_supplicant.conf. I then connect with: wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf and this is the output: rfkill: Cannot open RFKILL control device ioctl[SIOCSIWAP]: Operation not permitted wlan0: Trying to associate with e8:04:62:23:57:d0 (SSID='Guest' freq=2412 MHz) wlan0: Associated with e8:04:62:23:57:d0 wlan0: WPA: Key negotiation completed with e8:04:62:23:57:d0 [PTK=CCMP GTK=CCMP] wlan0: CTRL-EVENT-CONNECTED - Connection to e8:04:62:23:57:d0 completed (auth) [id=0 id_str=] It seems to connect but there are errors at the start, what do they mean? Do they affect the connection or does this look like I am connected correctly? I ask this as I try to give wlan0 an address with dhcp pr udhcpc and it does not get one, any idea why? I have tried these two wpa_supplicant.conf's network={ ssid="Guest" #psk="xxxxxxxx" psk= } and update_config=1 network={ ssid="Guest" proto=RSN key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk= } Both give the same thing

After two years and countless hours of trying to fix this issue, I was finally able to connect to eduroam (Enterprise WPA) from Arch. I was able to do this by ignoring NetworkManager entirely and using wpa_supplicant explicitly. Today I have learned of the existence of systemd-networkd and it allows me to connect to the internet. As I use NetworkManager on other machines for home WiFi connections, VPNs, etc., I would like to also get eduroam working with my original NetworkManager setup. Here is my current (working) setup:

> cat /etc/wpa_supplicant/wpa_supplicant-wlan0.conf`
network={
        ssid="eduroam"
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="username@domain"
        password="********"
        phase2="auth=MSCHAPV2"
}

> systemctl stop NetworkManager.service 
> systemctl start wpa_supplicant@wlan0.service systemd-networkd.service systemd-resolved.service dhcpcd.service

I have the (to my eyes) equivalent NetworkManager config, which doesn't work:

> cat /etc/NetworkManager/system-connections/eduroam.nmconnection
[connection]
id=eduroam
uuid=95580564-0352-438d-9804-364636618a28
type=wifi

[wifi]
mode=infrastructure
ssid=eduroam

[wifi-security]
key-mgmt=wpa-eap

[802-1x]
eap=peap;
identity=username@domain
password=********
phase2-auth=mschapv2

[ipv4]
method=auto

[ipv6]
method=auto

[proxy]

> nmcli con up eduroam
Error: Connection activation failed: The Wi-Fi network could not be found
Hint: use 'journalctl -xe NM_CONNECTION=95580564-0352-438d-9804-364636618a28 + NM_DEVICE=wlan0' to get more details.

> journalctl -xe NM_CONNECTION=95580564-0352-438d-9804-364636618a28 + NM_DEVICE=wlan0
Jun 18 16:15:03 kim-xps13-9343 NetworkManager:   [1718720103.7090] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 18 16:15:08 kim-xps13-9343 NetworkManager:   [1718720108.2210] device (wlan0): supplicant interface state: scanning -> disconnected
Jun 18 16:15:18 kim-xps13-9343 NetworkManager:   [1718720118.2758] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 18 16:15:22 kim-xps13-9343 NetworkManager:   [1718720122.7869] device (wlan0): supplicant interface state: scanning -> disconnected
Jun 18 16:15:25 kim-xps13-9343 NetworkManager:   [1718720125.1830] device (wlan0): Activation: (wifi) association took too long, failing activation
Jun 18 16:15:25 kim-xps13-9343 NetworkManager:   [1718720125.1831] device (wlan0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 18 16:15:25 kim-xps13-9343 NetworkManager:   [1718720125.1843] device (wlan0): Activation: failed for connection 'eduroam'
Jun 18 16:15:25 kim-xps13-9343 NetworkManager:   [1718720125.1845] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 18 16:15:44 kim-xps13-9343 NetworkManager:   [1718720144.8036] device (wlan0): supplicant interface state: disconnected -> inactive
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7364] device (wlan0): Activation: starting connection 'eduroam' (95580564-0352-438d-9804-364636618a28)
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7364] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7369] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7372] device (wlan0): Activation: (wifi) access point 'eduroam' has security, but secrets are required.
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7372] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7382] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7385] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7387] device (wlan0): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No new secrets needed.
Jun 18 16:17:03 kim-xps13-9343 NetworkManager:   [1718720223.7461] device (wlan0): supplicant interface state: inactive -> disconnected
Jun 18 16:17:13 kim-xps13-9343 NetworkManager:   [1718720233.7945] device (wlan0): supplicant interface state: disconnected -> scanning
Jun 18 16:17:18 kim-xps13-9343 NetworkManager:   [1718720238.3069] device (wlan0): supplicant interface state: scanning -> disconnected
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2291] device (wlan0): state change: config -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2300] device (wlan0): disconnecting for new activation request.
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2312] device (wlan0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2323] device (wlan0): Activation: starting connection 'eduroam' (95580564-0352-438d-9804-364636618a28)
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2330] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2335] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2338] device (wlan0): Activation: (wifi) access point 'eduroam' has security, but secrets are required.
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2338] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2350] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2353] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 18 16:17:23 kim-xps13-9343 NetworkManager:   [1718720243.2355] device (wlan0): Activation: (wifi) connection 'eduroam' has security, and secrets exist.  No new secrets needed.

What could be happening here?

Not sure how wpa_supplicant is using the "dbus_connection_read_write_dispatch" API while it communicate with NetworkManager? Should I use "dbus_connection_read_write_dispatch" API driven from timer or the thread for my RPI system which would be better option in terms of overall performance point of view? Please guide. Thanks, Vikas

I've my own process for instance named as VikProcess which inherited with possible code of wps_supplicant (dport, systemd, events.c, scan.c etc..) in order to get essential code features of wps_supplicant. Now, can someone please guide me to replace all possible services of wps_supplicant and use VikPropcess to communicate with Debian OS (RPI-3) NetworkManager services? Any lead would be helpful and appreciated.

In my distro, wpa_supplicant is used by NetworkManager, but it is fully configured via DBus. As a result, I cannot specify the bgscan option as described here: https://wiki.archlinux.org/title/Wpa_supplicant . In other words, I cannot use wpa_supplicant.conf, as it is ignored. However, I need to customize the rules for how the client switches between access points with the same SSID. I assume that switching is currently based on *connection* speed, which is not ideal because it doesn’t reflect the actual speed. I would prefer to use RSSI for this purpose. I have not found any settings in NetworkManager config for connection.

I have an Active Directory domain with Windows computers: when I join computer to AD, it gets computer account (computername$) and 802.1x group policy which says > Connect to SSID mySSID
> validate AAA server issuer certificate and it's FQDN,
> use PEAP\MSCHAPv2,
> use **computer** account for authentication Works good. How can I configure Ubuntu Linux Desktop computer, joined with sssd to same AD Domain, to authenticate to Wi-Fi same way?

I wanted to disable systemd unwanted attempts to automatically start wpa_supplicant. I thougth I could simply run a sudo systemctl disable wpa_supplicant.service --global and I would not be seeing a wpa_supplicant in ps -ef output anymore. Anyway this did not work. How can I make it work? My problem at hand might be best described by the output of $>systemctl status wpa_supplicant* ● wpa_supplicant.service - WPA supplicant Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled) Active: active (running) since Sun 2016-08-28 20:57:37 CEST; 14min ago where as you can see the disabled service is anyway loaded and active, thanks to systemd completely helping me do the simpletest thing ;) **Update** I seem to have had some luck by brutely removing these files: wpa_supplicant-nl80211@.service wpa_supplicant.service wpa_supplicant@.service wpa_supplicant-wired@.service from /usr/lib/systemd/system folder. Guess what? After restart wpa is finally not started by systemd anymore. It strikes me though there must have been a more *peaceful* / *conciliatory* way to get systemd to have the service not being started.

Trying to connect to a remote host, however I am receiving an error message shown below:

EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED

My connection config file is shown below:

p2p_disabled=1
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
    ssid="VERY"
    scan_ssid=1
    key_mgmt=WPA-EAP
    eap=PEAP
    identity="my\admin"
    password="admin"
    ca_cert="/etc/cert/ca.pem"
    phase1="peaplabel=0"
    phase2="auth=MSCHAPV2"
}

This is how I connect to interface

wpa_supplicant -B -i  -c

I have found that it hints to a driver issue.. Is there any alternative to using wpa_supplicant native to kali.