Hi Florin,
nice to have wpa_supplicant logs.
As a first step I would give a try disabling MAC address randomization
in NM. In you NetworkManager.conf:
[device]
wifi.scan-rand-mac-address=no
wifi.cloned-mac-address=permanent
then restart NM.
Maybe would be better to open a bugzilla for this to trace and attach
all related logs (https://bugzilla.gnome.org/). TRACE level logs for
NetworkManager could be of help too:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/ plain/contrib/fedora/rpm/ NetworkManager.conf?id=master
Thanks
Francesco
On 31/03/2017 06:59, Florin wrote:
> Observed the same behavior with NM 1.6.2
>
> On Thu, Mar 30, 2017 at 8:29 AM, Florin <florin resin io
> <mailto:florin resin io>> wrote:> <mailto:florin resin io>> wrote:
>
> And here are the wpa_supplicant logs:
>
> Mar 27 14:20:30 cdeeb95 systemd[1]: Starting WPA supplicant...
> Mar 27 14:20:31 cdeeb95 wpa_supplicant[859]: Successfully
> initialized wpa_supplicant
> Mar 27 14:20:31 cdeeb95 systemd[1]: Started WPA supplicant.
> Mar 27 14:20:31 cdeeb95 wpa_supplicant[859]: Libgcrypt warning:
> missing initialization - please fix the application
> Mar 27 14:20:34 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:21:51 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:21:51 cdeeb95 wpa_supplicant[859]: wlan0: Failed to
> initiate AP scan
> Mar 27 14:21:52 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:21:52 cdeeb95 wpa_supplicant[859]: wlan0: Failed to
> initiate AP scan
> Mar 27 14:21:53 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:21:53 cdeeb95 wpa_supplicant[859]: wlan0: Failed to
> initiate AP scan
> Mar 27 14:21:54 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:21:54 cdeeb95 wpa_supplicant[859]: wlan0: Failed to
> initiate AP scan
> Mar 27 14:21:55 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:21:55 cdeeb95 wpa_supplicant[859]: wlan0: Failed to
> initiate AP scan
> Mar 27 14:22:44 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:23:47 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:24:50 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
> Mar 27 14:25:54 cdeeb95 wpa_supplicant[859]: wlan0: Reject scan
> trigger since one is already pending
>
>
> On Thu, Mar 30, 2017 at 8:23 AM, Florin <florin resin io
>
> Some more details:
>
> # rfkill list
> 0: phy0: wlan
> Soft blocked: no
> Hard blocked: no
>
> # nmcli radio
> WIFI-HW WIFI WWAN-HW WWAN
> enabled enabled enabled enabled
>
> On Thu, Mar 30, 2017 at 7:57 AM, Florin <florin resin io
> <mailto:florin resin io>> wrote:
>
> Here is also how my system-connections file looks like:
>
> [connection]
> id=conn
> type=wifi
> autoconnect=true
>
> [wifi]
> hidden=false
> mode=infrastructure
> ssid=mywifi
>
> [wifi-security]
> auth-alg=open
> key-mgmt=wpa-psk
> psk=mypass
>
> [ipv4]
> method=auto
>
> [ipv6]
> addr-gen-mode=stable-privacy
> method=auto
>
>
> On Wed, Mar 29, 2017 at 1:54 PM, Florin <florin resin io
> ______________________________> <mailto:florin resin io>> wrote:
>
> Hi all,
> I have a strange issue with NetworkManager 1.4.2 with a
> wifi chipset using the wl18xx kernel module.
> I have the system-connections set-up but NM won't
> automatically connect. It will only connect if I use
> "nmcli con up <conenction name>".
> On the other hand, using a wifi usb dongle, such as the
> raspberry pi official dongle, which uses a BCM43143
> chipset, autoconnect to the same network works as expected.
>
> logs are these:
>
> Mar 27 14:20:31 29bc430 NetworkManager[709]: <info>
> [1490624431.3859] device (wlan0): state change:
> unavailable -> disconnected (reason
> 'supplicant-available') [20 30 42]
> Mar 27 14:20:35 29bc430 NetworkManager[709]: <info>
> [1490624435.4733] device (wlan0): supplicant interface
> state: ready -> inactive
> Mar 27 14:21:13 29bc430 NetworkManager[709]: <info>
> [1490624473.0366] device (wlan0): supplicant interface
> state: inactive -> scanning
> Mar 27 14:22:44 29bc430 NetworkManager[709]: <info>
> [1490624564.9449] device (wlan0): supplicant interface
> state: scanning -> inactive
> Mar 27 14:22:49 29bc430 NetworkManager[709]: <info>
> [1490624569.0186] device (wlan0): supplicant interface
> state: inactive -> scanning
> Mar 27 14:23:47 29bc430 NetworkManager[709]: <info>
> [1490624627.9367] device (wlan0): supplicant interface
> state: scanning -> inactive
> Mar 27 14:23:52 29bc430 NetworkManager[709]: <info>
> [1490624632.0417] device (wlan0): supplicant interface
> state: inactive -> scanning
> Mar 27 14:24:50 29bc430 NetworkManager[709]: <info>
> [1490624690.9474] device (wlan0): supplicant interface
> state: scanning -> inactive
> Mar 27 14:24:55 29bc430 NetworkManager[709]: <info>
> [1490624695.0190] device (wlan0): supplicant interface
> state: inactive -> scanning
> Mar 27 14:25:53 29bc430 NetworkManager[709]: <info>
> [1490624753.9617] device (wlan0): set-hw-addr: set MAC
> address to 1E:2D:A8:4C:19:94 (scanning)
> Mar 27 14:25:54 29bc430 NetworkManager[709]: <info>
> [1490624754.4841] device (wlan0): supplicant interface
> state: scanning -> disabled
> Mar 27 14:25:54 29bc430 NetworkManager[709]: <info>
> [1490624754.5031] device (wlan0): supplicant interface
> state: disabled -> inactive
> Mar 27 14:28:05 29bc430 NetworkManager[709]: <info>
> [1490624885.0367] device (wlan0): supplicant interface
> state: inactive -> scanning
> Mar 27 14:29:03 29bc430 NetworkManager[709]: <info>
> [1490624943.9366] device (wlan0): supplicant interface
> state: scanning -> inactive
>
> Any clue?
> Thank you
>
>
>
>
>
>
>
_________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> https://mail.gnome.org/mailman/listinfo/ networkmanager-list
>