> -----Original Message----- > From: Dan Williams [mailto:[email protected]] > Sent: Wednesday, June 28, 2017 11:16 AM > To: Matthew Starr; [email protected] > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues > > On Tue, 2017-06-13 at 16:13 +0000, Matthew Starr wrote: > > > -----Original Message----- > > > From: Dan Williams [mailto:[email protected]] > > > Sent: Tuesday, June 06, 2017 10:10 AM > > > To: Matthew Starr; [email protected] > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues > > > > > > On Wed, 2017-05-31 at 19:50 +0000, Matthew Starr wrote: > > > > 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. > > > > > > FYI I haven't forgotten about this, I hope to send a new test patch > > > today. > > > > > > Dan > > > > > > > Dan, > > > > Thanks for all your help so far. Have you got a chance to generate a > > new patch? > > Attached... same drill. > > Thanks! > Dan
It appears to work every time again with debug, resulting in the AP reconnecting with no issue after an hour of not being within range. Attached is the syslog output. Best regards, Matthew Starr
Jun 28 21:55:18 canect2 user.alert kernel: [ 5041.036013] wlan: mlan0 START SCAN Jun 28 21:55:20 canect2 user.warn kernel: [ 5042.648063] wlan: SCAN COMPLETED: scanned AP count=2 Jun 28 21:56:21 canect2 user.alert kernel: [ 5104.046083] wlan: mlan0 START SCAN Jun 28 21:56:23 canect2 user.warn kernel: [ 5105.658004] wlan: SCAN COMPLETED: scanned AP count=7 Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect-16281043325' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect-16281043325' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect-16281043325' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'BrettSalesDemo' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect-16281043325' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'BrettSalesDemo' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect-16281043325' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) autoactivate attempt Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP '<none>' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'BrettSalesDemo' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'hed-inc' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED-Guest' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'CANect-16281043325' incompatible with connection Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) BEST 'HED.Inc.Wifi' Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Auto-activating connection 'HED.Inc.Wifi'. Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: starting connection 'HED.Inc.Wifi' (f34c0555-5ad1-49d0-bd2f-b74dc06c19f6) Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> NetworkManager state is now CONNECTING Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) access point 'HED.Inc.Wifi' has security, but secrets are required. Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) connection 'HED.Inc.Wifi' has security, and secrets exist. No new secrets needed. Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Config: added 'ssid' value 'HED.Inc.Wifi' Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Config: added 'scan_ssid' value '1' Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Config: added 'auth_alg' value 'OPEN' Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Config: added 'psk' value '<omitted>' Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Config: set interface ap_scan to 1 Jun 28 21:56:23 canect2 user.alert kernel: [ 5105.971138] wlan: Connected to bssid 24:XX:XX:XX:76:60 successfully Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: disconnected -> associating Jun 28 21:56:23 canect2 user.info kernel: [ 5105.982345] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associating -> associated Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: associated -> 4-way handshake Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): supplicant interface state: 4-way handshake -> completed Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'HED.Inc.Wifi'. Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: config -> ip-config (reason 'none') [50 70 0] Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> Activation (mlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]: <info> dhcpcd started with pid 1051 Jun 28 21:56:24 canect2 daemon.info dhcpcd[1051]: DUID 00:01:00:01:20:e6:ce:3a:00:06:c6:48:39:49 Jun 28 21:56:24 canect2 daemon.info dhcpcd[1051]: mlan0: IAID c6:48:39:49 Jun 28 21:56:24 canect2 daemon.info dhcpcd[1051]: mlan0: rebinding lease of 172.16.2.190 Jun 28 21:56:24 canect2 daemon.info dhcpcd[1051]: mlan0: soliciting an IPv6 router Jun 28 21:56:24 canect2 daemon.info dhcpcd[1051]: mlan0: leased 172.16.2.190 for 86400 seconds Jun 28 21:56:24 canect2 daemon.info dhcpcd[1051]: mlan0: adding route to 172.16.2.0/24 Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> address 172.16.2.190 Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> plen 24 (255.255.255.0) Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> gateway 172.16.2.254 Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> server identifier 172.16.2.254 Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> lease time 86400 Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> nameserver '192.168.1.2' Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> nameserver '192.168.1.4' Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> domain name 'hed.local' Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0): DHCPv4 state changed unknown -> bound Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Jun 28 21:56:24 canect2 daemon.notice dbus[200]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Jun 28 21:56:24 canect2 daemon.notice dbus[200]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jun 28 21:56:24 canect2 daemon.notice nm-dispatcher: Dispatching action 'pre-up' for mlan0 Jun 28 21:56:24 canect2 user.notice root: Starting wifi_config_nm.sh Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> NetworkManager state is now CONNECTED_LOCAL Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> NetworkManager state is now CONNECTED_GLOBAL Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> Policy set 'HED.Inc.Wifi' (mlan0) as default for IPv4 routing and DNS. Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> (mlan0): Activation: successful, device activated. Jun 28 21:56:24 canect2 user.info kernel: [ 5106.963477] cfg80211: Regulatory domain changed to country: US Jun 28 21:56:24 canect2 user.info kernel: [ 5106.969340] cfg80211: DFS Master region: FCC Jun 28 21:56:24 canect2 user.info kernel: [ 5106.973581] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Jun 28 21:56:24 canect2 user.info kernel: [ 5106.983370] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A) Jun 28 21:56:24 canect2 user.info kernel: [ 5106.991385] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A) Jun 28 21:56:24 canect2 user.info kernel: [ 5107.000897] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s) Jun 28 21:56:24 canect2 user.info kernel: [ 5107.010420] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s) Jun 28 21:56:24 canect2 user.info kernel: [ 5107.018536] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A) Jun 28 21:56:24 canect2 user.info kernel: [ 5107.026562] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) Jun 28 21:56:24 canect2 daemon.notice nm-dispatcher: Dispatching action 'up' for mlan0 Jun 28 21:56:24 canect2 daemon.info NetworkManager[251]: <info> #### (mlan0) [wifi avail] AP 'HED.Inc.Wifi' compatible
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
