> -----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]
> > > > > 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; [email protected]
> > > > > > > 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:[email protected]]
> > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > To: Matthew Starr; [email protected]
> > > > > > > > > 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.
-Matt
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
autoactivate attempt
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
autoactivate candidate 'HED.Inc.Wifi'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP '17107020874-Endurance'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP '17107020874-Endurance' incompatible with connection
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED-Guest'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED-Guest' incompatible with connection
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (checking 17107020874-Endurance)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (17107020874-Endurance incompatible with connection)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (checking HED-Guest)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (HED-Guest incompatible with connection)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (checking HED.Inc.Wifi)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
BEST
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info>
Auto-activating connection 'HED.Inc.Wifi'.
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
Activation: starting connection 'HED.Inc.Wifi'
(50d8d011-2764-43a4-ba9a-0eaf9acba7d6)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> NetworkManager
state is now CONNECTING
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: prepare -> config (reason 'none') [40 50 0]
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
Activation: (wifi) access point 'HED.Inc.Wifi' has security, but secrets are
required.
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: config -> need-auth (reason 'none') [50 60 0]
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (uap0)
[device] < unavailable
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (eth0)
[device] < disconnected
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (lo)
[device] incompatible with device
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (sit0)
[device] incompatible with device
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (can0)
[device] incompatible with device
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (can1)
[device] incompatible with device
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> #### (ttyACM0)
[device] < disconnected
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: need-auth -> prepare (reason 'none') [60 40 0]
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: prepare -> config (reason 'none') [40 50 0]
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
Activation: (wifi) connection 'HED.Inc.Wifi' has security, and secrets exist.
No new secrets needed.
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Config: added
'ssid' value 'HED.Inc.Wifi'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Config: added
'scan_ssid' value '1'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Config: added
'key_mgmt' value 'WPA-PSK'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Config: added
'auth_alg' value 'OPEN'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Config: added
'psk' value '<omitted>'
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Config: set
interface ap_scan to 1
May 24 21:55:37 canect2 user.alert kernel: [ 4417.103947] wlan: Connected to
bssid 24:XX:XX:XX:7b:20 successfully
May 24 21:55:37 canect2 user.info kernel: [ 4417.112195] IPv6:
ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: disconnected -> associating
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: associating -> associated
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: associated -> 4-way handshake
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: 4-way handshake -> completed
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to
wireless network 'HED.Inc.Wifi'.
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: config -> ip-config (reason 'none') [50 70 0]
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> Activation
(mlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 24 21:55:37 canect2 daemon.info NetworkManager[251]: <info> dhcpcd started
with pid 1031
May 24 21:55:38 canect2 daemon.info dhcpcd[1031]: DUID
00:01:00:01:20:b8:ac:05:00:06:c6:48:39:49
May 24 21:55:38 canect2 daemon.info dhcpcd[1031]: mlan0: IAID c6:48:39:49
May 24 21:55:38 canect2 daemon.info dhcpcd[1031]: mlan0: soliciting an IPv6
router
May 24 21:55:38 canect2 daemon.info dhcpcd[1031]: mlan0: rebinding lease of
172.16.2.190
May 24 21:55:39 canect2 daemon.info dhcpcd[1031]: mlan0: leased 172.16.2.190
for 86400 seconds
May 24 21:55:39 canect2 daemon.info dhcpcd[1031]: mlan0: adding route to
172.16.2.0/24
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> address
172.16.2.190
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> plen 24
(255.255.255.0)
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> gateway
172.16.2.254
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> server
identifier 172.16.2.254
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> lease time
86400
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> nameserver
'192.168.1.2'
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> nameserver
'192.168.1.4'
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> domain name
'hed.local'
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
DHCPv4 state changed unknown -> bound
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: ip-config -> ip-check (reason 'none') [70 80 0]
May 24 21:55:39 canect2 daemon.notice dbus[200]: [system] Activating service
name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 24 21:55:39 canect2 daemon.notice dbus[200]: [system] Successfully
activated service 'org.freedesktop.nm_dispatcher'
May 24 21:55:39 canect2 daemon.notice nm-dispatcher: Dispatching action
'pre-up' for mlan0
May 24 21:55:39 canect2 user.notice root: Starting wifi_config_nm.sh
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: ip-check -> secondaries (reason 'none') [80 90 0]
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: secondaries -> activated (reason 'none') [90 100 0]
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> NetworkManager
state is now CONNECTED_LOCAL
May 24 21:55:39 canect2 user.info kernel: [ 4418.719388] cfg80211: Regulatory
domain changed to country: US
May 24 21:55:39 canect2 user.info kernel: [ 4418.725297] cfg80211: DFS Master
region: FCC
May 24 21:55:39 canect2 user.info kernel: [ 4418.729488] cfg80211:
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp),
(dfs_cac_time)
May 24 21:55:39 canect2 user.info kernel: [ 4418.739271] cfg80211: (2402000
KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
May 24 21:55:39 canect2 user.info kernel: [ 4418.747305] cfg80211: (5170000
KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
May 24 21:55:39 canect2 user.info kernel: [ 4418.756819] cfg80211: (5250000
KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
May 24 21:55:39 canect2 user.info kernel: [ 4418.766333] cfg80211: (5490000
KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
May 24 21:55:39 canect2 user.info kernel: [ 4418.774443] cfg80211: (5735000
KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
May 24 21:55:39 canect2 user.info kernel: [ 4418.782471] cfg80211: (57240000
KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
roamed from BSSID 24:A4:3C:55:76:60 (HED.Inc.Wifi) to 24:A4:3C:55:7B:20
(HED.Inc.Wifi)
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> NetworkManager
state is now CONNECTED_GLOBAL
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> Policy set
'HED.Inc.Wifi' (mlan0) as default for IPv4 routing and DNS.
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
Activation: successful, device activated.
May 24 21:55:39 canect2 daemon.notice nm-dispatcher: Dispatching action 'up'
for mlan0
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (uap0)
[device] < unavailable
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (eth0)
[device] < disconnected
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (lo)
[device] incompatible with device
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (sit0)
[device] incompatible with device
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (can0)
[device] incompatible with device
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (can1)
[device] incompatible with device
May 24 21:55:39 canect2 daemon.info NetworkManager[251]: <info> #### (ttyACM0)
[device] < disconnected
May 24 21:55:39 canect2 user.notice root: network_services_control started
May 24 21:55:39 canect2 user.notice root: network_services_control IF=mlan0,
STATUS=up, DEFAULT_ROUTE_IF=mlan0
May 24 21:55:42 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 IEEE
802.11: associated
May 24 21:55:42 canect2 user.warn kernel: [ 4421.389390] wlan: EVENT:
MICRO_AP_STA_ASSOC 9c:XX:XX:XX:80:10
May 24 21:55:42 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 WPA:
pairwise key handshake completed (RSN)
May 24 21:55:42 canect2 daemon.info dnsmasq-dhcp[234]: DHCPREQUEST(uap0)
192.168.0.53 9c:2a:70:7c:80:10
May 24 21:55:42 canect2 daemon.info dnsmasq-dhcp[234]: DHCPACK(uap0)
192.168.0.53 9c:2a:70:7c:80:10 hed-dpk9cw1
May 24 21:55:51 canect2 daemon.warn dhcpcd[1031]: mlan0: no IPv6 Routers
available
May 24 21:55:57 canect2 authpriv.info dropbear[1094]: Child connection from
192.168.0.53:44918
May 24 21:55:59 canect2 authpriv.notice dropbear[1094]: Password auth succeeded
for 'root' from 192.168.0.53:44918
May 24 21:56:38 canect2 user.alert kernel: [ 4477.989717] wlan: mlan0 START SCAN
May 24 21:56:40 canect2 user.warn kernel: [ 4479.599849] wlan: SCAN COMPLETED:
scanned AP count=13
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] not wifi
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] parent fail
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] not wifi
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] not wifi
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'BrettSalesDemo'
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'BrettSalesDemo' incompatible with connection
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 21:56:40 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 21:57:21 canect2 user.alert kernel: [ 4520.987732] wlan: mlan0 START SCAN
May 24 21:57:23 canect2 user.warn kernel: [ 4522.574637] wlan: SCAN COMPLETED:
scanned AP count=16
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] not wifi
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] parent fail
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] not wifi
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] not wifi
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[device] incompatible with device
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP '<none>'
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP '<none>' incompatible with connection
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'BrettSalesDemo'
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'BrettSalesDemo' incompatible with connection
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 21:57:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 21:58:24 canect2 user.alert kernel: [ 4583.989634] wlan: mlan0 START SCAN
May 24 21:58:26 canect2 user.warn kernel: [ 4585.597695] wlan: SCAN COMPLETED:
scanned AP count=15
May 24 21:59:24 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 IEEE
802.11: disassociated
May 24 21:59:24 canect2 user.warn kernel: [ 4643.302710] wlan: EVENT:
MICRO_AP_STA_DEAUTH 9c:XX:XX:XX:80:10
May 24 21:59:24 canect2 daemon.info hostapd: uap0: STA 9c:2a:70:7c:80:10 IEEE
802.11: disassociated
May 24 21:59:47 canect2 user.alert kernel: [ 4666.987762] wlan: mlan0 START SCAN
May 24 21:59:49 canect2 user.warn kernel: [ 4668.576642] wlan: SCAN COMPLETED:
scanned AP count=16
May 24 22:00:08 canect2 user.warn kernel: [ 4687.631016] wlan: EVENT: Link lost
(reason 0x0)
May 24 22:00:08 canect2 user.alert kernel: [ 4687.635662] wlan: Disconnected
from 24:XX:XX:XX:7b:20: Reason code 3
May 24 22:00:08 canect2 daemon.warn NetworkManager[251]: <warn> Connection
disconnected (reason 3)
May 24 22:00:08 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: completed -> disconnected
May 24 22:00:08 canect2 user.info kernel: [ 4687.681134] cfg80211: World
regulatory domain updated:
May 24 22:00:08 canect2 user.info kernel: [ 4687.686305] cfg80211: DFS Master
region: unset
May 24 22:00:08 canect2 user.info kernel: [ 4687.690737] cfg80211:
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp),
(dfs_cac_time)
May 24 22:00:08 canect2 user.info kernel: [ 4687.700521] cfg80211: (2402000
KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4687.708532] cfg80211: (2457000
KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4687.716560] cfg80211: (2474000
KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4687.724591] cfg80211: (5170000
KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4687.734096] cfg80211: (5250000
KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
May 24 22:00:08 canect2 user.info kernel: [ 4687.743607] cfg80211: (5490000
KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
May 24 22:00:08 canect2 user.info kernel: [ 4687.751721] cfg80211: (5735000
KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4687.759730] cfg80211: (57240000
KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
May 24 22:00:08 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: disconnected -> scanning
May 24 22:00:08 canect2 user.alert kernel: [ 4687.769747] wlan: mlan0 START SCAN
May 24 22:00:08 canect2 user.warn kernel: [ 4687.976053] wlan: SCAN COMPLETED:
scanned AP count=1
May 24 22:00:08 canect2 user.info kernel: [ 4687.981720] cfg80211: Regulatory
domain changed to country: US
May 24 22:00:08 canect2 user.info kernel: [ 4687.987577] cfg80211: DFS Master
region: FCC
May 24 22:00:08 canect2 user.info kernel: [ 4687.991825] cfg80211:
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp),
(dfs_cac_time)
May 24 22:00:08 canect2 user.info kernel: [ 4688.001608] cfg80211: (2402000
KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4688.009625] cfg80211: (5170000
KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4688.019134] cfg80211: (5250000
KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)
May 24 22:00:08 canect2 user.info kernel: [ 4688.028635] cfg80211: (5490000
KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)
May 24 22:00:08 canect2 user.info kernel: [ 4688.036748] cfg80211: (5735000
KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
May 24 22:00:08 canect2 user.info kernel: [ 4688.044781] cfg80211: (57240000
KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
May 24 22:00:09 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: scanning -> associating
May 24 22:00:09 canect2 user.warn kernel: [ 4688.326063] wlan: SCAN COMPLETED:
scanned AP count=0
May 24 22:00:09 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: associating -> disconnected
May 24 22:00:09 canect2 user.alert kernel: [ 4688.436032] wlan: mlan0 START SCAN
May 24 22:00:09 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: disconnected -> scanning
May 24 22:00:10 canect2 user.warn kernel: [ 4689.638632] wlan: SCAN COMPLETED:
scanned AP count=1
May 24 22:00:10 canect2 user.warn kernel: [ 4689.861131] wlan: SCAN COMPLETED:
scanned AP count=0
May 24 22:00:10 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: scanning -> associating
May 24 22:00:10 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: associating -> disconnected
May 24 22:00:11 canect2 user.alert kernel: [ 4690.884089] wlan: mlan0 START SCAN
May 24 22:00:11 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: disconnected -> scanning
May 24 22:00:11 canect2 user.warn kernel: [ 4691.089885] wlan: SCAN COMPLETED:
scanned AP count=1
May 24 22:00:12 canect2 user.warn kernel: [ 4691.317320] wlan: SCAN COMPLETED:
scanned AP count=0
May 24 22:00:12 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: scanning -> associating
May 24 22:00:12 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: associating -> disconnected
May 24 22:00:13 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: disconnected -> scanning
May 24 22:00:13 canect2 user.alert kernel: [ 4692.356688] wlan: mlan0 START SCAN
May 24 22:00:14 canect2 user.warn kernel: [ 4693.559965] wlan: SCAN COMPLETED:
scanned AP count=2
May 24 22:00:14 canect2 user.warn kernel: [ 4693.839873] wlan: SCAN COMPLETED:
scanned AP count=0
May 24 22:00:14 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: scanning -> associating
May 24 22:00:14 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
supplicant interface state: associating -> disconnected
May 24 22:00:23 canect2 daemon.warn NetworkManager[251]: <warn> (mlan0): link
timed out.
May 24 22:00:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: activated -> failed (reason 'supplicant-timeout') [100 120
11]
May 24 22:00:23 canect2 daemon.info NetworkManager[251]: <info> NetworkManager
state is now CONNECTED_LOCAL
May 24 22:00:23 canect2 daemon.info NetworkManager[251]: <info> NetworkManager
state is now DISCONNECTED
May 24 22:00:23 canect2 daemon.warn NetworkManager[251]: <warn> (mlan0):
Activation: failed for connection 'HED.Inc.Wifi'
May 24 22:00:23 canect2 daemon.notice dbus[200]: [system] Activating service
name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 24 22:00:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
device state change: failed -> disconnected (reason 'none') [120 30 0]
May 24 22:00:23 canect2 daemon.info dhcpcd[1031]: received SIGTERM, stopping
May 24 22:00:23 canect2 daemon.info dhcpcd[1031]: mlan0: removing interface
May 24 22:00:23 canect2 user.info kernel: [ 4703.039982] IPv6:
ADDRCONF(NETDEV_UP): mlan0: link is not ready
May 24 22:00:23 canect2 daemon.notice dbus[200]: [system] Successfully
activated service 'org.freedesktop.nm_dispatcher'
May 24 22:00:23 canect2 daemon.notice nm-dispatcher: Dispatching action 'down'
for mlan0
May 24 22:00:23 canect2 user.notice root: network_services_control started
May 24 22:00:23 canect2 user.notice root: network_services_control IF=mlan0,
STATUS=down, DEFAULT_ROUTE_IF=mlan0
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
canceled DHCP transaction, DHCP client pid 1031
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0):
DHCPv4 state changed bound -> done
May 24 22:00:24 canect2 user.alert kernel: [ 4703.574574] wlan: mlan0 START SCAN
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
autoactivate attempt
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
autoactivate candidate 'HED.Inc.Wifi'
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP '<none>'
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP '<none>' incompatible with connection
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'BrettSalesDemo'
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'BrettSalesDemo' incompatible with connection
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] checking AP 'HED.Inc.Wifi'
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi compat] AP 'HED.Inc.Wifi' compatible
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (checking <none>)
May 24 22:00:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0)
[wifi] (<none> incompatible with connection)
_______________________________________________
networkmanager-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/networkmanager-list
