I have noticed one more disturbing behaviour. In nmconnection configuration file there is this key-mgmt. It's value is set on wpa-psk but NetworkManager sets its value to WPA-PSK WPA-PSK-SHA256 FT-PSK for which the connection isn't working for me even with wpa_supplicant. How may i change it to be only WPA-PSK?
BR Piotr ________________________________ Od: Piotr Lobacz <[email protected]> Wysłane: czwartek, 28 stycznia 2021 19:30 Do: Beniamino Galvani <[email protected]> DW: [email protected] <[email protected]> Temat: ODP: cannot connect rtl8192fs to wireless network using NetworkManager with wpa_supplicant Hi again Beniamino, i have verified these parameters as you asked. These are the parameters which i can see in NEtworkManager: Jan 28 18:12:48 px30-64 NetworkManager[365]: <info> [1611857568.4335] Config: added 'ssid' value 'beherith' Jan 28 18:12:48 px30-64 NetworkManager[365]: <info> [1611857568.4337] Config: added 'scan_ssid' value '1' Jan 28 18:12:48 px30-64 NetworkManager[365]: <info> [1611857568.4338] Config: added 'bgscan' value 'simple:30:-70:86400' Jan 28 18:12:48 px30-64 NetworkManager[365]: <info> [1611857568.4340] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Jan 28 18:12:48 px30-64 NetworkManager[365]: <info> [1611857568.4341] Config: added 'psk' value '<hidden>' I have made a wpa_supplicant.conf file which looks like this: root@px30-64:~# cat /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ap_scan=1 update_config=1 network={ ssid="my_wifi" scan_ssid=1 bgscan="simple:30:-70:86400" psk="my_secret_password" key_mgmt="WPA-PSK WPA-PSK-SHA256 FT-PSK" } And wpa_supplicant returned me this: root@px30-64:~# wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf & [1] 529 root@px30-64:~# Successfully initialized wpa_supplicant wlan0: Trying to associate with ec:08:6b:e7:f3:40 (SSID='my_wifi' freq=2462 MHz) Failed to add supported operating classes IE wlan0: Association request to the driver failed wlan0: Associated with ec:08:6b:e7:f3:40 wlan0: WPA: Key negotiation completed with ec:08:6b:e7:f3:40 [PTK=CCMP GTK=CCMP] wlan0: CTRL-EVENT-CONNECTED - Connection to ec:08:6b:e7:f3:40 completed [id=0 id_str=] bgscan simple: Failed to enable signal strength monitoring WEXT: SIOCGIWSTATS: Operation not supported So i commented it and started again wifi, which has worked for me. Now the question is how can i turn bgscan off using NetworkManager ? Od: networkmanager-list <[email protected]> w imieniu użytkownika Piotr Lobacz <[email protected]> Wysłane: wtorek, 26 stycznia 2021 20:49 Do: Beniamino Galvani <[email protected]> DW: [email protected] <[email protected]> Temat: ODP: cannot connect rtl8192fs to wireless network using NetworkManager with wpa_supplicant Hi Beniamino, thx for your quick response, I'll try to pass these NM parameters, as you suggested and see if it works. Btw. they do differ than these from wpa_supplicant, so maybe there is the problem. I will keep you inform. Best regards Piotr ________________________________ Od: Beniamino Galvani Wysłano: Wtorek, 26 Styczeń 2021 14:03 Do: Piotr Lobacz DW: [email protected] Temat: Re: cannot connect rtl8192fs to wireless network using NetworkManager with wpa_supplicant On Sun, Jan 24, 2021 at 02:32:01PM +0000, Piotr Lobacz wrote: > i am struggling for a week to connect via NM together with > wpa_supplicant using systemd on buildroot. I have compiled > wpa_supplicant with dbus support. Before that i tried to use only > NM, but the nmcli was saying that the wlan0 interface was > unavailable. I was unable even to scan network using nmcli, but > iwlist wlan0 scan command was working just great. More over if i use > only wpa_supplicant configuration file with this command: > [...] > There is one more thing. This rtl8192fs driver needs private > parameters to work. Before i call wpa_supplicant command i need to > call this 4 commands: > [...] > But the connection isn't being established. I have attached logs > from wpa_supplicant and NetworkManager. > Btw. i have also tried to establish connection setting this iwpriv > parameters on wlan0 interface but for some reason these are not > working for wpa_supplicant/NetworkManager. I was wondering if NM > somehow passes it's own configuration to the interface? If yes how > can make some modifications? Yes, NetworkManager passes its own configuration to wpa_supplicant via D-Bus. You should be able to see the configuration in NM logs; on my machine for example I see: NetworkManager[1645]: <info> [1611663864.0215] Config: added 'ssid' value 'home' NetworkManager[1645]: <info> [1611663864.0215] Config: added 'scan_ssid' value '1' NetworkManager[1645]: <info> [1611663864.0215] Config: added 'bgscan' value 'simple:30:-70:86400' NetworkManager[1645]: <info> [1611663864.0215] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' NetworkManager[1645]: <info> [1611663864.0215] Config: added 'auth_alg' value 'OPEN' NetworkManager[1645]: <info> [1611663864.0215] Config: added 'psk' value '<hidden>' You could try to see if the same configuration works with wpa_supplicant alone. Regarding iwpriv parameters, NM doesn't support them. But if you set them manually before connecting with NM, I guess they should work. Beniamino [https://softgent.com/wp-content/uploads/2020/01/Zasob-14.png]<https://www.softgent.com> Softgent Sp. z o.o., Budowlanych 31d, 80-298 Gdansk, POLAND KRS: 0000674406, NIP: 9581679801, REGON: 367090912 www.softgent.com Sąd Rejonowy Gdańsk-Północ w Gdańsku, VII Wydział Gospodarczy Krajowego Rejestru Sądowego KRS 0000674406, Kapitał zakładowy: 25 000,00 zł wpłacony w całości.
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
