> On May 15, 2019, at 4:04 PM, Dan Williams <dcbw@xxxxxxxxxx> wrote: > > On Wed, 2019-05-15 at 21:54 +0200, Wiktor Drewniak wrote: >> Can you provide your wpa_supplicant config? Or way how you configure >> it? > > Looks like the problem is likely on the NetworkManager side. Note that > a Network object is registered via D-Bus and then unregistered after > the association timeout. NM reads the scan results from the supplicant > and when it matches an SSID from its configuration to one from the scan > results, will create a Network object (representing a 'network' block > in the supplicant config) and ask the supplicant to use it. When NM > thinks it shouldn't be connected anymore, it will remove that network > object. > > So you'd want to enable NetworkManager debug info to figure out why NM > is deciding not to connect to the SSID: > > nmcli g log level debug > <try again> > journalctl -b -u NetworkManager (or if not using the systemd journal, > wherever your syslog config puts NetworkManager output) > Thanks! Actually, this was using connman rather than networkmanager, but presumably the same theory applies. I'll see if I can reproduce the issue again (it's transient, requiring some as-yet mysterious RF situation). I'm happy to report that it doesn't seem to happen with wpa_supplicant v2.8, for what that's worth. Best, Jonah _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
