> Am 09.11.2016 um 12:20 schrieb Brüns, Stefan <[email protected]>: > >> On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote: >> Hi Stefan, >> >> The results: >> >> - journalctl -b -u NetworkManager >> (there is much more output, but I take it this is what you mean:) >> >> nov 09 17:04:11 nohostname NetworkManager[548]: <info> >> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to >> 8E:07:9D:1E:8C:93 (scanning) >> nov 09 17:04:11 nohostname NetworkManager[548]: <info> >> [1478707451.8066] device (wlan0): supplicant interface state: completed >> -> disabled >> nov 09 17:04:11 nohostname NetworkManager[548]: <info> >> [1478707451.8078] device (wlan0): supplicant interface state: disabled >> -> scanning >> nov 09 17:04:12 nohostname NetworkManager[548]: <info> >> [1478707452.3294] device (wlan0): supplicant interface state: scanning >> -> associating >> nov 09 17:04:12 nohostname NetworkManager[548]: <info> >> [1478707452.4836] device (wlan0): supplicant interface state: >> associating -> associated >> nov 09 17:04:13 nohostname NetworkManager[548]: <info> >> [1478707453.3429] device (wlan0): supplicant interface state: associated >> -> 4-way handshake >> nov 09 17:04:13 nohostname NetworkManager[548]: <info> >> [1478707453.3706] device (wlan0): supplicant interface state: 4-way >> handshake -> completed >> nov 09 17:09:27 nohostname NetworkManager[548]: <info> >> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to >> 56:74:0F:44:0E:15 (scanning) > > This is odd. Obviously it has connected to the network successfully. The > scanning actions may be background scans, but it should re-set the mac > address > to the one successfully used with the access point previously. > > You may try disabling mac randomization temporarily. > > Anyway, I think this is worth an upstream bug report.
Could you please try again with a really strong power supply first? Thanks, Alex -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
