Now it is back to reconnecting every time when the AP is back in range after an hour of it being out of range. Here are the logs for when it is working with the latest debug patch. At 19:35:02 it failed to connect because I forgot to reattach the antenna, but it connected okay 30 seconds later when the antenna was connected.
Let me know what you would like to try next. -Matt > -----Original Message----- > From: Dan Williams [mailto:[email protected]] > Sent: Wednesday, May 31, 2017 11:23 AM > To: Matthew Starr; [email protected] > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues > > Another round, getting closer... > > Dan > > On Wed, 2017-05-31 at 14:10 +0000, Matthew Starr wrote: > > > -----Original Message----- > > > From: Dan Williams [mailto:[email protected]] > > > Sent: Tuesday, May 30, 2017 1:42 PM > > > To: Matthew Starr; [email protected] > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues > > > > > > Ok another patch attached. Same as last patch, but it comments out > > > a bunch of the debug logging. It should point us in the right > > > direction at least. > > > > > > Dan > > > > > > > Now the issue is occurring again and I was able to capture the > > attached log messages from syslog. You can see network manager > > detecting the network I want to connect to "HED.Inc.Wifi", it shows it > > as a compatible connection, it lists it under the autoactivate > > candidates, but then never connects. > > > > -Matt > > > > > On Tue, 2017-05-30 at 16:19 +0000, Matthew Starr wrote: > > > > > -----Original Message----- > > > > > From: Dan Williams [mailto:[email protected]] > > > > > Sent: Thursday, May 25, 2017 11:25 PM > > > > > To: Matthew Starr; [email protected] > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues > > > > > > > > > > On Thu, 2017-05-25 at 22:00 +0000, Matthew Starr wrote: > > > > > > > -----Original Message----- > > > > > > > From: Dan Williams [mailto:[email protected]] > > > > > > > Sent: Thursday, May 25, 2017 12:49 PM > > > > > > > To: Matthew Starr; [email protected] > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues > > > > > > > > > > > > > > On Thu, 2017-05-25 at 13:06 +0000, Matthew Starr wrote: > > > > > > > > > -----Original Message----- > > > > > > > > > From: Dan Williams [mailto:[email protected]] > > > > > > > > > Sent: Wednesday, May 24, 2017 3:26 PM > > > > > > > > > To: Matthew Starr; [email protected] > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect > > > > > > > > > Issues > > > > > > > > > > > > > > > > > > On Wed, 2017-05-24 at 18:22 +0000, Matthew Starr wrote: > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > From: Dan Williams [mailto:[email protected]] > > > > > > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM > > > > > > > > > > > To: Matthew Starr; [email protected] > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect > > > > > > > > > > > Issues > > > > > > > > > > > > > > > > > > > > > > On Thu, 2017-05-18 at 22:25 +0000, Matthew Starr > > > > > > > > > > > wrote: > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > > From: Dan Williams [mailto:[email protected]] > > > > > > > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM > > > > > > > > > > > > > To: Matthew Starr; [email protected] > > > > > > > > > > > > > g > > > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi > > > > > > > > > > > > > Autoconnect Issues > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 2017-05-18 at 20:23 +0000, Matthew Starr > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > > > > From: Dan Williams [mailto:[email protected]] > > > > > > > > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM > > > > > > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnom > > > > > > > > > > > > > > > e.or g > > > > > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi > > > > > > > > > > > > > > > Autoconnect Issues > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 2017-05-18 at 18:43 +0000, Matthew > > > > > > > > > > > > > > > Starr > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > > > > > > > > From: Dan Williams [mailto:dcbw@redhat. > > > > > > > > > > > > > > > > > com] > > > > > > > > > > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM > > > > > > > > > > > > > > > > > To: Matthew Starr; networkmanager-list@ > > > > > > > > > > > > > > > > > gnom e.or g > > > > > > > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi- > > > > > > > > > > > > > > > > > Fi Autoconnect Issues > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 2017-05-18 at 15:54 +0000, > > > > > > > > > > > > > > > > > Matthew Starr > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > I have tried using NetworkManager > > > > > > > > > > > > > > > > > > 1.0.0 > > > > > > > > > > > > > > > > > > and > > > > > > > > > > > > > > > > > > 1.0.12 on an embedded device built > > > > > > > > > > > > > > > > > > with buildroot that has Ethernet > > > > > > > > > > > > > > > > > > (eth0), Wi-Fi client (mlan0), Wi-Fi > > > > > > > > > > > > > > > > > > Access Point (uap0), and Cellular > > > > > > > > > > > > > > > > > > interfaces > > > > > > > > > > > > > > > > > > (ttyACM0 and ppp0). The Wi-Fi AP > > > > > > > > > > > > > > > > > > (uap0) interface is ignored by Network > > > > > > > > > > > > > > > > > > Manager based on my > > > > > > > > > > > > > > > > > > NetworkManager.conf file. > > > > > > > > > > > > > > > > > > I am > > > > > > > > > > > > > > > > > > able to boot the device and Network > > > > > > > > > > > > > > > > > > Manager will automatically configure > > > > > > > > > > > > > > > > > > and connect with Ethernet, Wi-Fi > > > > > > > > > > > > > > > > > > Client, and Cellular interfaces every > > > > > > > > > > > > > > > > > > time. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > If I move out of range of the Wi-Fi > > > > > > > > > > > > > > > > > > access point the device will > > > > > > > > > > > > > > > > > > disconnect and if I move back into > > > > > > > > > > > > > > > > > > range in under an hour, NetworkManager > > > > > > > > > > > > > > > > > > will reestablish the connection. If I > > > > > > > > > > > > > > > > > > wait multiple hours before moving back > > > > > > > > > > > > > > > > > > into range of the Wi-Fi access point, > > > > > > > > > > > > > > > > > > Network Manager will not reestablish a > > > > > > > > > > > > > > > > > > connection automatically with the > > > > > > > > > > > > > > > > > > access point (I waited hours with the > > > > > > > > > > > > > > > > > > AP within range and visible in Wi-Fi > > > > > > > > > > > > > > > > > > scan results). > > > > > > > > > > > > > > > > > > When Network Manager is not > > > > > > > > > > > > > > > > > > automatically reestablishing a > > > > > > > > > > > > > > > > > > connection to the access point I can > > > > > > > > > > > > > > > > > > use nmcli to bring up the profile > > > > > > > > > > > > > > > > > > associated with the access point and > > > > > > > > > > > > > > > > > > it connects immediately. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Why is Network Manager not able to > > > > > > > > > > > > > > > > > > auto connect to a > > > > > > > > > > > > > > > > > > Wi- > > > > > > > > > > > > > > > > > > Fi AP after a longer period of time of > > > > > > > > > > > > > > > > > > not seeing the AP? > > > > > > > > > > > > > > > > > > Is there a timeout within Network > > > > > > > > > > > > > > > > > > Manager? > > > > > > > > > > > > > > > > > > Is this a bug? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Like you say, it does look like NM is > > > > > > > > > > > > > > > > > trying to > > > > > > > > > > > > > > > > > auto- > > > > > > > > > > > > > > > > > activate the connection, but it's not > > > > > > > > > > > > > > > > > doing it correctly. > > > > > > > > > > > > > > > > > The most likely thing happening is that > > > > > > > > > > > > > > > > > it does try to activate, but it's not > > > > > > > > > > > > > > > > > able to find the "best" > > > > > > > > > > > > > > > > > connection for the device. > > > > > > > > > > > > > > > > > Somehow the existing WiFi connection > > > > > > > > > > > > > > > > > profile isn't matching. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Can you run 'nmcli con show <name of > > > > > > > > > > > > > > > > > connection you expect to > > > > > > > > > > > > > > > > > start>'? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dan, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This issue has occurred on several > > > > > > > > > > > > > > > > different access point I have attempted to > > > > > > > > > > > > > > > > connect to all from different vendors > > > > > > > > > > > > > > > > (Linksys, Ubiquiti, D- link). > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Ok, that doesn't ellucidate anything. Are > > > > > > > > > > > > > > > you able to apply a debugging patch to > > > > > > > > > > > > > > > NetworkManager and rebuild it? > > > > > > > > > > > > > > > Alternatively, you could use 'gdb' to step > > > > > > > > > > > > > > > through the code and see where it's not > > > > > > > > > > > > > > > proceeding with the activation in > > > > > > > > > > > > > > > nm-policy.c. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Some additional testing I just finished shows > > > > > > > > > > > > > > that version > > > > > > > > > > > > > > 1.6.2 > > > > > > > > > > > > > > exhibits the exact same behavior. > > > > > > > > > > > > > > > > > > > > > > > > > > > > I am able to apply patches easily and rebuild. > > > > > > > > > > > > > > I could run gdb but it is not quite as easy on > > > > > > > > > > > > > > my current setup. > > > > > > > > > > > > > > > > > > > > > > > > > > Which version do you prefer patches for? > > > > > > > > > > > > > > > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > > > > > My more immediate need is with the 1.0.12 version, > > > > > > > > > > > > but I plan to do a release within the next 6 > > > > > > > > > > > > months with the 1.6.X or 1.8.X version. > > > > > > > > > > > > > > > > > > > > > > Patch against upstream 1.0.12 attached. Hopefully > > > > > > > > > > > applies to your version. It should log the right > > > > > > > > > > > stuff without touching the logging level or domains. > > > > > > > > > > > Run with this patch, reproduce the issue, and lets > > > > > > > > > > > see what the logs say. > > > > > > > > > > > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > I was able to cleanly apply the patch, but shortly > > > > > > > > > > after starting Network Manager it seems to seg fault > > > > > > > > > > (verified by using the -n option to not run as a > > > > > > > > > > daemon). I don't see any error messages in the logs. > > > > > > > > > > Here is where the logs left off: > > > > > > > > > > > > > > > > > > You've probably got some hidden-SSID APs, and I didn't > > > > > > > > > account for that. Can you back out the previous patch, > > > > > > > > > and try the latest attached one? > > > > > > > > > > > > > > > > > > Dan > > > > > > > > > > > > > > > > With the new patch I was able to establish a connection, > > > > > > > > put the module running Network Manager in a faraday cage > > > > > > > > for an hour, and then on removing it from the cage Network > > > > > > > > Manager connected successfully. > > > > > > > > This usually is not the case after an hour of not seeing > > > > > > > > the APs. At this point I wanted to test again for a > > > > > > > > longer period so I put the module back in the cage for an > > > > > > > > overnight test and it appears as soon as the module was > > > > > > > > isolated from all the APs, Network Manager crashed again. > > > > > > > > See the attached log for what was going on when it crashed > > > > > > > > at May 24 22:00:24. > > > > > > > > > > > > > > > > I will try my setup again after a reboot to get Network > > > > > > > > Manager running again. Let me know if there is another > > > > > > > > patch you want me to apply to resolve the crashing issue. > > > > > > > > > > > > > > Again my fault. Any place you see: > > > > > > > > > > > > > > g_free (tmp); > > > > > > > > > > > > > > in the patch, replace that with: > > > > > > > > > > > > > > if (ssid) g_free (tmp); > > > > > > > > > > > > > > Or back out the previous patch, and apply the attached one. > > > > > > > > > > > > > > Dan > > > > > > > > > > > > It appears I cannot reproduce the issue with the patch you > > > > > > provided that includes the debug statements. The Wi-Fi > > > > > > reconnects within > > > > > > 1-2 > > > > > > minutes or less every time. I wonder if this is a timing > > > > > > issue that the debug statements are delaying just enough to > > > > > > not make the issue occur. > > > > > > > > > > > > Before the patch I could reproduce it almost every time on > > > > > > multiple devices running the same software after an hour of no > > > > > > Wi-Fi signal. The only change on the devices is the updated > > > > > > network manager with your patch. I will continue to test after > > > > > > memorial day. > > > > > > > > > > > > Is there anything else you want me to check with the unpatched > > > > > > version or any other patches you want me to try out? > > > > > > > > > > Could you rebuild without the patch and test that version? eg, > > > > > to determine whether it's the debug patch making it work, or > > > > > whether for some reason the rebuild is doing it. I can also > > > > > start removing log statements to reduce any potential timing > > > > > issue. > > > > > > > > > > Dan > > > > > > > > I rebuilt network manager without the debug patches and after 1 > > > > hour of no Wi-Fi signal, network manager is not attempting to > > > > reconnect when the Wi-FI AP is visible again (verified using "iw > > > > dev mlan0 scan"). > > > > > > > > If you have any other patches you want to try with log statements > > > > removed, I would be happy to test them. > > > > > > > > -Matt
May 31 19:35:00 canect2 user.alert kernel: [10486.940278] wlan: mlan0 START SCAN May 31 19:35:02 canect2 user.warn kernel: [10488.552818] wlan: SCAN COMPLETED: scanned AP count=7 May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '17107020874-Endurance' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '17107020874-Endurance' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] no compatible AP found May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] connection not available May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '17107020875-Endurance' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '17107020875-Endurance' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '17107020874-Endurance' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '17107020874-Endurance' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] no compatible AP found May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] connection not available May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED-Guest' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '17107020873-Endurance' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '17107020873-Endurance' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED-Guest' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'linksys-hed-test' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'linksys-hed-test' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) autoactivate attempt May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) autoactivate candidate 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'linksys-hed-test' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'linksys-hed-test' incompatible with connection May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi] (checking linksys-hed-test) May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi] (linksys-hed-test incompatible with connection) May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi] (checking HED.Inc.Wifi) May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) BEST May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Auto-activating connection 'HED.Inc.Wifi'. May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: starting connection 'HED.Inc.Wifi' (2d16f38e-37f9-4e2b-aeb9-324d1ffb55bf) May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> NetworkManager state is now CONNECTING May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: prepare -> config (reason 'none') [40 50 0] May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) access point 'HED.Inc.Wifi' has security, but secrets are required. May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: config -> need-auth (reason 'none') [50 60 0] May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (lo) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (sit0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (can0) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> #### (can1) [device] incompatible with device May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: prepare -> config (reason 'none') [40 50 0] May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) connection 'HED.Inc.Wifi' has security, and secrets exist. No new secrets needed. May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Config: added 'ssid' value 'HED.Inc.Wifi' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Config: added 'scan_ssid' value '1' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Config: added 'key_mgmt' value 'WPA-PSK' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Config: added 'auth_alg' value 'OPEN' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Config: added 'psk' value '<omitted>' May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> Config: set interface ap_scan to 1 May 31 19:35:02 canect2 user.warn kernel: [10488.885444] ASSOC_RESP: Association Failed, status code = 2, error = 0xfffc, a_id = 0xffff May 31 19:35:02 canect2 user.err kernel: [10488.893775] IOCTL failed: c23ff800 id=0x20000, sub_id=0x20001 action=1, status_code=0xfffc0002 May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: disconnected -> associating May 31 19:35:02 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associating -> disconnected May 31 19:35:03 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: disconnected -> scanning May 31 19:35:03 canect2 user.alert kernel: [10489.911754] wlan: mlan0 START SCAN May 31 19:35:03 canect2 user.warn kernel: [10490.117823] wlan: SCAN COMPLETED: scanned AP count=0 May 31 19:35:04 canect2 user.warn kernel: [10490.369078] wlan: SCAN COMPLETED: scanned AP count=0 May 31 19:35:04 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: scanning -> associating May 31 19:35:04 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associating -> disconnected May 31 19:35:05 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: disconnected -> scanning May 31 19:35:05 canect2 user.alert kernel: [10491.379836] wlan: mlan0 START SCAN May 31 19:35:06 canect2 user.warn kernel: [10492.583889] wlan: SCAN COMPLETED: scanned AP count=5 May 31 19:35:06 canect2 user.warn kernel: [10492.840349] wlan: SCAN COMPLETED: scanned AP count=0 May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: scanning -> associating May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:06 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associating -> disconnected May 31 19:35:16 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: disconnected -> scanning May 31 19:35:16 canect2 user.alert kernel: [10502.860685] wlan: mlan0 START SCAN May 31 19:35:16 canect2 user.warn kernel: [10503.066486] wlan: SCAN COMPLETED: scanned AP count=0 May 31 19:35:17 canect2 user.warn kernel: [10503.335292] wlan: SCAN COMPLETED: scanned AP count=0 May 31 19:35:17 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: scanning -> associating May 31 19:35:17 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associating -> disconnected May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: disconnected -> scanning May 31 19:35:27 canect2 user.alert kernel: [10513.349498] wlan: mlan0 START SCAN May 31 19:35:27 canect2 daemon.warn NetworkManager[251]: <warn> (mlan0): Activation: (wifi) association took too long May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: config -> need-auth (reason 'none') [50 60 0] May 31 19:35:27 canect2 daemon.warn NetworkManager[251]: <warn> (mlan0): Activation: (wifi) asking for new secrets May 31 19:35:27 canect2 daemon.warn NetworkManager[251]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. May 31 19:35:27 canect2 daemon.warn NetworkManager[251]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (lo) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (sit0) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (can0) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (can1) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (lo) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (sit0) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (can0) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> #### (can1) [device] incompatible with device May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: prepare -> config (reason 'none') [40 50 0] May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) connection 'HED.Inc.Wifi' has security, and secrets exist. No new secrets needed. May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> Config: added 'ssid' value 'HED.Inc.Wifi' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> Config: added 'scan_ssid' value '1' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> Config: added 'key_mgmt' value 'WPA-PSK' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> Config: added 'auth_alg' value 'OPEN' May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> Config: added 'psk' value '<omitted>' May 31 19:35:27 canect2 daemon.warn NetworkManager[251]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. May 31 19:35:27 canect2 daemon.info NetworkManager[251]: <info> Config: set interface ap_scan to 1 May 31 19:35:28 canect2 user.warn kernel: [10514.551400] wlan: SCAN COMPLETED: scanned AP count=12 May 31 19:35:28 canect2 user.alert kernel: [10514.637231] wlan: Connected to bssid 24:XX:XX:XX:76:60 successfully May 31 19:35:28 canect2 user.info kernel: [10514.653869] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: scanning -> associating May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '16307046638-Endurance' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '16307046638-Endurance' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associating -> associated May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'TP-LINK_728C' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'TP-LINK_728C' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '16307046638-Endurance' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '16307046638-Endurance' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '17107020876-Endurance' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '17107020876-Endurance' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'TP-LINK_728C' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'TP-LINK_728C' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '16307046638-Endurance' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '16307046638-Endurance' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED-Guest' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '17107020876-Endurance' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '17107020876-Endurance' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'TP-LINK_728C' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'TP-LINK_728C' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '16307046638-Endurance' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '16307046638-Endurance' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'hed-inc' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associated -> 4-way handshake May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: 4-way handshake -> completed May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'HED.Inc.Wifi'. May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: config -> ip-config (reason 'none') [50 70 0] May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> Activation (mlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) May 31 19:35:28 canect2 daemon.info NetworkManager[251]: <info> dhcpcd started with pid 1903 May 31 19:35:28 canect2 daemon.info dhcpcd[1903]: mlan0: adding address fe80::2b5c:bf02:680f:9d6b May 31 19:35:28 canect2 daemon.info dhcpcd[1903]: DUID 00:01:00:01:20:c1:ad:ee:00:06:c6:48:39:49 May 31 19:35:28 canect2 daemon.info dhcpcd[1903]: mlan0: IAID c6:48:39:49 May 31 19:35:28 canect2 daemon.info dhcpcd[1903]: mlan0: rebinding lease of 172.16.2.190 May 31 19:35:29 canect2 daemon.info dhcpcd[1903]: mlan0: soliciting an IPv6 router May 31 19:35:29 canect2 daemon.info dhcpcd[1903]: mlan0: leased 172.16.2.190 for 86400 seconds May 31 19:35:29 canect2 daemon.info dhcpcd[1903]: mlan0: adding route to 172.16.2.0/24 May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> address 172.16.2.190 May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> plen 24 (255.255.255.0) May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> gateway 172.16.2.254 May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> server identifier 172.16.2.254 May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> lease time 86400 May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> nameserver '192.168.1.2' May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> nameserver '192.168.1.4' May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> domain name 'hed.local' May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> (mlan0): DHCPv4 state changed unknown -> bound May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] May 31 19:35:29 canect2 daemon.notice dbus[200]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) May 31 19:35:29 canect2 daemon.notice dbus[200]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' May 31 19:35:29 canect2 daemon.notice nm-dispatcher: Dispatching action 'pre-up' for mlan0 May 31 19:35:29 canect2 user.notice root: Starting wifi_config_nm.sh May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: secondaries -> activated (reason 'none') [90 100 0] May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> NetworkManager state is now CONNECTED_LOCAL May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> (mlan0): roamed from BSSID 24:A4:3C:55:7B:20 (HED.Inc.Wifi) to 24:A4:3C:55:76:60 (HED.Inc.Wifi) May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> NetworkManager state is now CONNECTED_GLOBAL May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> Policy set 'HED.Inc.Wifi' (mlan0) as default for IPv4 routing and DNS. May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: successful, device activated. May 31 19:35:29 canect2 daemon.notice nm-dispatcher: Dispatching action 'up' for mlan0 May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> #### (lo) [device] incompatible with device May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> #### (sit0) [device] incompatible with device May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> #### (can0) [device] incompatible with device May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:35:29 canect2 daemon.info NetworkManager[251]: <info> #### (can1) [device] incompatible with device May 31 19:35:29 canect2 user.notice root: network_services_control started May 31 19:35:29 canect2 user.notice root: network_services_control IF=mlan0, STATUS=up, DEFAULT_ROUTE_IF=mlan0 May 31 19:35:42 canect2 daemon.warn dhcpcd[1903]: mlan0: no IPv6 Routers available May 31 19:35:56 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 IEEE 802.11: associated May 31 19:35:56 canect2 user.warn kernel: [10543.131778] wlan: EVENT: MICRO_AP_STA_ASSOC 9c:XX:XX:XX:80:10 May 31 19:35:56 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 WPA: pairwise key handshake completed (RSN) May 31 19:35:56 canect2 daemon.info dnsmasq-dhcp[234]: DHCPREQUEST(uap0) 192.168.0.53 9c:2a:70:7c:80:10 May 31 19:35:56 canect2 daemon.info dnsmasq-dhcp[234]: DHCPACK(uap0) 192.168.0.53 9c:2a:70:7c:80:10 hed-dpk9cw1 May 31 19:36:03 canect2 authpriv.info dropbear[1968]: Child connection from 192.168.0.53:37468 May 31 19:36:03 canect2 user.alert kernel: [10549.937767] wlan: mlan0 START SCAN May 31 19:36:05 canect2 user.warn kernel: [10551.527985] wlan: SCAN COMPLETED: scanned AP count=13 May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'BrettSalesDemo' May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'BrettSalesDemo' incompatible with connection May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:36:05 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:36:05 canect2 authpriv.notice dropbear[1968]: Password auth succeeded for 'root' from 192.168.0.53:37468 May 31 19:36:46 canect2 user.alert kernel: [10592.938662] wlan: mlan0 START SCAN May 31 19:36:48 canect2 user.warn kernel: [10594.525897] wlan: SCAN COMPLETED: scanned AP count=12 May 31 19:37:49 canect2 user.alert kernel: [10655.943377] wlan: mlan0 START SCAN May 31 19:37:51 canect2 user.warn kernel: [10657.539024] wlan: SCAN COMPLETED: scanned AP count=14 May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'BrettSalesDemo' May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'BrettSalesDemo' incompatible with connection May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:37:51 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:39:12 canect2 user.alert kernel: [10738.943120] wlan: mlan0 START SCAN May 31 19:39:14 canect2 user.warn kernel: [10740.537567] wlan: SCAN COMPLETED: scanned AP count=14 May 31 19:40:23 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 WPA: group key handshake completed (RSN) May 31 19:40:55 canect2 user.alert kernel: [10841.943477] wlan: mlan0 START SCAN May 31 19:40:57 canect2 user.warn kernel: [10843.543472] wlan: SCAN COMPLETED: scanned AP count=11 May 31 19:42:55 canect2 user.alert kernel: [10961.947427] wlan: mlan0 START SCAN May 31 19:42:57 canect2 user.warn kernel: [10963.550464] wlan: SCAN COMPLETED: scanned AP count=15 May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'CANect2-Mark' May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect2-Mark' incompatible with connection May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP '<none>' May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'BrettSalesDemo' May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'BrettSalesDemo' incompatible with connection May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] checking AP 'HED.Inc.Wifi' May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible May 31 19:42:57 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [device] incompatible with device May 31 19:44:55 canect2 user.alert kernel: [11081.947818] wlan: mlan0 START SCAN May 31 19:44:57 canect2 user.warn kernel: [11083.560908] wlan: SCAN COMPLETED: scanned AP count=13
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
