RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-06-28 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Wednesday, June 28, 2017 11:16 AM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Tue, 2017-06-13 at 16:13 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Tuesday, June 06, 2017 10:10 AM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Wed, 2017-05-31 at 19:50 +, 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]:    (mlan0)   
  [wifi avail]AP 'HED.Inc.Wifi' compatible
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'CANect-16281043325' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED.Inc.Wifi' compatible
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED-Guest' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'CANect-16281043325' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED.Inc.Wifi' compatible
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'hed-inc' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED-Guest' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'CANect-16281043325' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED.Inc.Wifi' compatible
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'BrettSalesDemo' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'hed-inc' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED-Guest' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'CANect-16281043325' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED.Inc.Wifi' compatible
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP '' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'BrettSalesDemo' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'hed-inc' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP 'HED-Guest' incompatible with connection
Jun 28 21:56:23 canect2 daemon.info NetworkManager[251]:    (mlan0)   
  [wifi avail]AP &#

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-06-28 Thread Dan Williams 
On Tue, 2017-06-13 at 16:13 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Tuesday, June 06, 2017 10:10 AM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Wed, 2017-05-31 at 19:50 +, 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!
Dandiff --git a/src/devices/nm-device.c b/src/devices/nm-device.c
index bc7ebcb..423cc74 100644
--- a/src/devices/nm-device.c
+++ b/src/devices/nm-device.c
@@ -2150,7 +2150,10 @@ can_auto_connect (NMDevice *self,
 
 	s_con = nm_connection_get_setting_connection (connection);
 	if (!nm_setting_connection_get_autoconnect (s_con))
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [device] not autoconnect", nm_device_get_iface (self));
 		return FALSE;
+}
 
 	return nm_device_check_connection_available (self, connection, NM_DEVICE_CHECK_CON_AVAILABLE_NONE, NULL);
 }
@@ -7765,24 +7768,40 @@ nm_device_check_connection_available (NMDevice *self,
   const char *specific_object)
 {
 	NMDeviceState state;
+	gboolean avail;
 
 	state = nm_device_get_state (self);
 	if (state < NM_DEVICE_STATE_UNMANAGED)
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [device] < unmanaged", nm_device_get_iface (self));
 		return FALSE;
+}
 	if (   state < NM_DEVICE_STATE_UNAVAILABLE
 	&& nm_device_get_unmanaged_flag (self, NM_UNMANAGED_ALL & ~NM_UNMANAGED_DEFAULT))
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [device] < unavailable", nm_device_get_iface (self));
 		return FALSE;
+}
 	if (   state < NM_DEVICE_STATE_DISCONNECTED
 	&& (   (   !NM_FLAGS_HAS (flags, _NM_DEVICE_CHECK_CON_AVAILABLE_FOR_USER_REQUEST_WAITING_CARRIER)
 	&& !nm_device_is_available (self, NM_DEVICE_CHECK_DEV_AVAILABLE_NONE))
 	|| (NM_FLAGS_HAS (flags, _NM_DEVICE_CHECK_CON_AVAILABLE_FOR_USER_REQUEST_WAITING_CARRIER)
 	&& !nm_device_is_available (self, NM_DEVICE_CHECK_DEV_AVAILABLE_IGNORE_CARRIER
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [device] < disconnected", nm_device_get_iface (self));
 		return FALSE;
+}
 
 	if (!nm_device_check_connection_compatible (self, connection))
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [device] incompatible with device", nm_device_get_iface (self));
 		return FALSE;
+}
 
-	return NM_DEVICE_GET_CLASS (self)->check_connection_available (self, connection, flags, specific_object);
+	avail = NM_DEVICE_GET_CLASS (self)->check_connection_available (self, connection, flags, specific_object);
+	if (!avail)
+	nm_log_info (LOGD_DEVICE, " (%s) [device] connection not available", nm_device_get_iface (self));
+	return avail;
 }
 
 static void
diff --git a/src/devices/wifi/nm-device-wifi.c b/src/devices/wifi/nm-device-wifi.c
index 0f7fb6e..0dc53b9 100644
--- a/src/devices/wifi/nm-device-wifi.c
+++ b/src/devices/wifi/nm-device-wifi.c
@@ -777,53 +777,84 @@ check_connection_compatible (NMDevice *device, NMConnection *connection)
 	const char *perm_hw_addr;
 
 	if (!NM_DEVICE_CLASS (nm_device_wifi_parent_class)->check_connection_compatible (device, connection))
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [wifi compat] parent fail", nm_device_get_iface (device));
 		return FALSE;
+}
 
 	s_con = nm_connection_get_setting_connection (connection);
 	g_assert (s_con);
 
 	if (strcmp (nm_setting_connection_get_connection_type (s_con), NM_SETTING_WIRELESS_SETTING_NAME))
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [wifi compat] not wifi", nm_device_get_iface (device));
 		return FALSE;
+}
 
 	s_wireless = nm_connection_get_setting_wireless (connection);
 	if (!s_wireless)
+{
+//	nm_log_info (LOGD_DEVICE, " (%s) [wifi compat] no wireless setting", nm_device_get_iface (device));
 		return FALSE;
+}
 
 	perm_hw_addr = nm_device_get_permanent_hw_address (device);
 	mac = nm_setting_wireless_get_mac_address (s_wireless);
 	if (perm_hw_addr) {
 		if (mac && !nm_utils_hwaddr_matches (

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-06-13 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Tuesday, June 06, 2017 10:10 AM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Wed, 2017-05-31 at 19:50 +, 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?

-Matt
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-06-06 Thread Dan Williams 
On Wed, 2017-05-31 at 19:50 +, 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

> -Matt
> 
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Wednesday, May 31, 2017 11:23 AM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > Another round, getting closer...
> > 
> > Dan
> > 
> > On Wed, 2017-05-31 at 14:10 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Tuesday, May 30, 2017 1:42 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > 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 +, Matthew Starr wrote:
> > > > > > -Original Message-
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Thursday, May 25, 2017 11:25 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > 
> > > > > > On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > > > > > > > -Original Message-
> > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > Sent: Thursday, May 25, 2017 12:49 PM
> > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > Issues
> > > > > > > > 
> > > > > > > > On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > > > > > > > > -Original Message-
> > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > Autoconnect
> > > > > > > > > > Issues
> > > > > > > > > > 
> > > > > > > > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr
> > > > > > > > > > wrote:
> > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > g
> > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > Autoconnect
> > > > > > > > > > > > Issues
> > > > > > > > > > > > 
> > > > > > > > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew
> > > > > > > > > > > > Starr
> > > >

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-31 Thread Matthew Starr 
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:d...@redhat.com]
> Sent: Wednesday, May 31, 2017 11:23 AM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> Another round, getting closer...
> 
> Dan
> 
> On Wed, 2017-05-31 at 14:10 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Tuesday, May 30, 2017 1:42 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > 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 +, Matthew Starr wrote:
> > > > > -----Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Thursday, May 25, 2017 11:25 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > > > > > > -Original Message-
> > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > Sent: Thursday, May 25, 2017 12:49 PM
> > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > >
> > > > > > > On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > > > > > > > -Original Message-
> > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > Issues
> > > > > > > > >
> > > > > > > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > > > > > > > -Original Message-
> > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > > > Issues
> > > > > > > > > > >
> > > > > > > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > > g
> > > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > > Autoconnect Issues
> > > > > > > > > > > > >
> > > > > > > > > > > > > O

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-31 Thread Dan Williams 
Another round, getting closer...

Dan

On Wed, 2017-05-31 at 14:10 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Tuesday, May 30, 2017 1:42 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > 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 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Thursday, May 25, 2017 11:25 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > > > > > -----Original Message-----
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Thursday, May 25, 2017 12:49 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > 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:d...@redhat.com]
> > > > > > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > Issues
> > > > > > > > 
> > > > > > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > > > > > > -Original Message-
> > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > Autoconnect
> > > > > > > > > > Issues
> > > > > > > > > > 
> > > > > > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr
> > > > > > > > > > wrote:
> > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > g
> > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > Autoconnect
> > > > > > > > > > > > Issues
> > > > > > > > > > > > 
> > > > > > > > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew
> > > > > > > > > > > > Starr
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnom
> > > > > > > > > > > > > > e.or
> > > > > > > > > > > > > > g
> > > > > > > > > > > > > > Subject: Re: Network Manager 1.0.

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-31 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Tuesday, May 30, 2017 1:42 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> 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 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Thursday, May 25, 2017 11:25 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > > > > -Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Thursday, May 25, 2017 12:49 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > > > > > -Original Message-
> > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > >
> > > > > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > > > > > -Original Message-
> > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > Issues
> > > > > > > > >
> > > > > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > > > > > > > -Original Message-
> > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > > > Issues
> > > > > > > > > > >
> > > > > > > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > -Original Message-----
> > > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > > g
> > > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > > Autoconnect Issues
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnom
> > > > > > > > > >

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-30 Thread Dan Williams 
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

On Tue, 2017-05-30 at 16:19 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Thursday, May 25, 2017 11:25 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Thursday, May 25, 2017 12:49 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > > > > -Original Message-
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > 
> > > > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > > > > -Original Message-
> > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > Issues
> > > > > > > > 
> > > > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > > > > > > -Original Message-
> > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > Autoconnect
> > > > > > > > > > Issues
> > > > > > > > > > 
> > > > > > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr
> > > > > > > > > > wrote:
> > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > g
> > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > Autoconnect
> > > > > > > > > > > > Issues
> > > > > > > > > > > > 
> > > > > > > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew
> > > > > > > > > > > > Starr
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > > > From: Dan Williams [mailto:d...@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 +, Matthew
> > > > > > > > > > > > > > Starr
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > &g

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-30 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, May 25, 2017 11:25 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Thursday, May 25, 2017 12:49 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > > > -Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > > > -Original Message-
> > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > >
> > > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > > > > > -Original Message-
> > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > Issues
> > > > > > > > >
> > > > > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > > > > > > > -Original Message-
> > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > > > Issues
> > > > > > > > > > >
> > > > > > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > > g
> > > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > > Autoconnect Issues
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Thu, 2017-05-18 at 15:54 +, 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
> > > > > > > > > > > > > > N

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-25 Thread Dan Williams 
On Thu, 2017-05-25 at 22:00 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Thursday, May 25, 2017 12:49 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > > -Original Message-
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > 
> > > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > > > > -Original Message-
> > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > Issues
> > > > > > > > 
> > > > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > > > > > > -Original Message-
> > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > Autoconnect
> > > > > > > > > > Issues
> > > > > > > > > > 
> > > > > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr
> > > > > > > > > > wrote:
> > > > > > > > > > > > -Original Message-
> > > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > > > > To: Matthew Starr; networkmanager-l...@gnome.or
> > > > > > > > > > > > g
> > > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > > > Autoconnect
> > > > > > > > > > > > Issues
> > > > > > > > > > > > 
> > > > > > > > > > > > On Thu, 2017-05-18 at 15:54 +, 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
> >

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-25 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, May 25, 2017 12:49 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Wednesday, May 24, 2017 3:26 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > > -Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > > > -Original Message-----
> > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > >
> > > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > > > > > -Original Message-
> > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > Issues
> > > > > > > > >
> > > > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > > > > > > > -Original Message-
> > > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > > > Issues
> > > > > > > > > > >
> > > > > > > > > > > On Thu, 2017-05-18 at 15:54 +, 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 p

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-25 Thread Dan Williams 
On Thu, 2017-05-25 at 13:06 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Wednesday, May 24, 2017 3:26 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > > -Original Message-
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > 
> > > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > > > > -Original Message-
> > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > Issues
> > > > > > > > 
> > > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > > > > > > -Original Message-
> > > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi
> > > > > > > > > > Autoconnect
> > > > > > > > > > Issues
> > > > > > > > > > 
> > > > > > > > > > On Thu, 2017-05-18 at 15:54 +, 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
> > > > > > > > > >

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-25 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Wednesday, May 24, 2017 3:26 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Wednesday, May 24, 2017 12:48 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > > -Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > > > -Original Message-----
> > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > >
> > > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > > > > > -Original Message-
> > > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > > Issues
> > > > > > > > >
> > > > > > > > > On Thu, 2017-05-18 at 15:54 +, 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
> > > &

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-24 Thread Dan Williams 
On Wed, 2017-05-24 at 18:22 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Wednesday, May 24, 2017 12:48 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Thursday, May 18, 2017 4:55 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > > -Original Message-
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > 
> > > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > > > > -Original Message-
> > > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect
> > > > > > > > Issues
> > > > > > > > 
> > > > > > > > On Thu, 2017-05-18 at 15:54 +, 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 ti

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-24 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Wednesday, May 24, 2017 12:48 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Thursday, May 18, 2017 4:55 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > > -Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > > > -Original Message-----
> > > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > >
> > > > > > > On Thu, 2017-05-18 at 15:54 +, 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  > > > > > > to
> > > > > > > start>'?
> > > > > >
> > > > > > Dan,
> > > > > >
> > > > > > This issue has occurred on several different access point I
> > > > > > have attempted to connect to all f

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-24 Thread Dan Williams 
On Thu, 2017-05-18 at 22:25 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Thursday, May 18, 2017 4:55 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Thursday, May 18, 2017 2:24 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > > -Original Message-
> > > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > > > 
> > > > > > On Thu, 2017-05-18 at 15:54 +, 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  > > > > > to
> > > > > > start>'?
> > > > > 
> > > > > Dan,
> > > > > 
> > > > > This issue has occurred on several different access point I
> > > > > have
> > > > > attempted to connect to all from different vendors (Linksys,
> > > > >

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-19 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, May 18, 2017 4:55 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Thursday, May 18, 2017 2:24 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > > -Original Message-
> > > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > >
> > > > > On Thu, 2017-05-18 at 15:54 +, 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  > > > > 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.

-Matt
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-18 Thread Dan Williams 
On Thu, 2017-05-18 at 20:23 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Thursday, May 18, 2017 2:24 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > > -Original Message-
> > > > From: Dan Williams [mailto:d...@redhat.com]
> > > > Sent: Thursday, May 18, 2017 1:31 PM
> > > > To: Matthew Starr; networkmanager-list@gnome.org
> > > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > > > 
> > > > On Thu, 2017-05-18 at 15:54 +, 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  > > > 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
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-18 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, May 18, 2017 2:24 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > > -Original Message-
> > > From: Dan Williams [mailto:d...@redhat.com]
> > > Sent: Thursday, May 18, 2017 1:31 PM
> > > To: Matthew Starr; networkmanager-list@gnome.org
> > > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > >
> > > On Thu, 2017-05-18 at 15:54 +, 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  > > 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.

-Matt
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-18 Thread Matthew Starr 
> -Original Message-
> From: Dan Williams [mailto:d...@redhat.com]
> Sent: Thursday, May 18, 2017 1:31 PM
> To: Matthew Starr; networkmanager-list@gnome.org
> Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> 
> On Thu, 2017-05-18 at 15:54 +, 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 '?

Dan,

This issue has occurred on several different access point I have attempted to 
connect to all from different vendors (Linksys, Ubiquiti, D-link).

Here is the output for my connection profile for one of them:

# nmcli con show linksys-hed-test
connection.id:  linksys-hed-test
connection.uuid:3a3fdd49-c624-42a3-acbd-135f728c9621
connection.interface-name:  mlan0
connection.type:802-11-wireless
connection.autoconnect: yes
connection.autoconnect-priority:0
connection.timestamp:   1495132442
connection.read-only:   no
connection.permissions: 
connection.zone:--
connection.master:  --
connection.slave-type:  --
connection.secondaries: 
connection.gateway-ping-timeout:0
802-11-wireless.ssid:   linksys-hed-test
802-11-wireless.mode:   --
802-11-wireless.band:   --
802-11-wireless.channel:0
802-11-wireless.bssid:  --
802-11-wireless.rate:   0
802-11-wireless.tx-power:   0
802-11-wireless.mac-address:--
802-11-wireless.cloned-mac-address: --
802-11-wireless.mac-address-blacklist:  
802-11-wireless.mtu:auto
802-11-wireless.seen-bssids:
802-11-wireless.hidden: no
802-11-wireless-security.key-mgmt:  wpa-psk
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg:  --
802-11-wireless-security.proto: 
802-11-wireless-security.pairwise:  
802-11-wireless-security.group: 
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0:  
802-11-wireless-security.wep-key1:  
802-11-wireless-security.wep-key2:  
802-11-wireless-security.wep-key3:  
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type:  0 (unknown)
802-11-wireless-security.psk:   
802-11-wireless-security.psk-flags: 0 (none)
802-11-wireless-security.leap-password: 
802-11-wireless-security.leap-password-flags:0 (none)
ipv4.method:auto
ipv4.dns:   
ipv4.dns-search:
ipv4.addresses: 
ipv4.gateway:   --
ipv4.routes:
ipv4.route-metric:  -1
ipv4.ignore-auto-routes:no
ipv4.ignore-auto-dns:   no
ipv4.dhcp-client-id:--
ipv4.dhcp-send-hostname:yes
ipv4.dhcp-hostname: --
ipv4.never-default: no
ipv4.may-

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-18 Thread Dan Williams 
On Thu, 2017-05-18 at 18:43 +, Matthew Starr wrote:
> > -Original Message-
> > From: Dan Williams [mailto:d...@redhat.com]
> > Sent: Thursday, May 18, 2017 1:31 PM
> > To: Matthew Starr; networkmanager-list@gnome.org
> > Subject: Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues
> > 
> > On Thu, 2017-05-18 at 15:54 +, 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  > 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

> Here is the output for my connection profile for one of them:
> 
> # nmcli con show linksys-hed-test
> connection.id:  linksys-hed-test
> connection.uuid:3a3fdd49-c624-42a3-acbd-
> 135f728c9621
> connection.interface-name:  mlan0
> connection.type:802-11-wireless
> connection.autoconnect: yes
> connection.autoconnect-priority:0
> connection.timestamp:   1495132442
> connection.read-only:   no
> connection.permissions: 
> connection.zone:--
> connection.master:  --
> connection.slave-type:  --
> connection.secondaries: 
> connection.gateway-ping-timeout:0
> 802-11-wireless.ssid:   linksys-hed-test
> 802-11-wireless.mode:   --
> 802-11-wireless.band:   --
> 802-11-wireless.channel:0
> 802-11-wireless.bssid:  --
> 802-11-wireless.rate:   0
> 802-11-wireless.tx-power:   0
> 802-11-wireless.mac-address:--
> 802-11-wireless.cloned-mac-address: --
> 802-11-wireless.mac-address-blacklist:  
> 802-11-wireless.mtu:auto
> 802-11-wireless.seen-bssids:
> 802-11-wireless.hidden: no
> 802-11-wireless-security.key-mgmt:  wpa-psk
> 802-11-wireless-security.wep-tx-keyidx: 0
> 802-11-wireless-security.auth-alg:  --
> 802-11-wireless-security.proto: 
> 802-11-wireless-security.pairwise:  
> 802-11-wireless-security.group: 
> 802-11-wireless-security.leap-username: --
> 802-11-wireless-security.wep-key0:  
> 802-11-wireless-s

Re: Network Manager 1.0.X Wi-Fi Autoconnect Issues

2017-05-18 Thread Dan Williams 
On Thu, 2017-05-18 at 15:54 +, 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 '?

Also, 'iw dev mlan0 scan dump', find the block for the expected AP, and
report that.  Feel free to replace the BSSID with xs or something if
you want to hide it.

My best guess is a mismatch between the AP's beacon/properties and the
connection somehow.

Dan

> Below is the debug log output when Network Manager 1.0.12 is not auto
> reconnecting. The Wi-Fi client (mlan0) is scanning for access points
> every 60 seconds, but the autoactivate attempt only happens every 5
> minutes but then appears to immediately remove the pending action of
> autoactivate on the mlan0 interface.  At the same time the cellular
> connection is attempting to connect and can't connect because of bad
> signal strength.
> 
> May 18 14:33:31 canect2 daemon.info NetworkManager[245]: 
> [1495118011.701118] [devices/nm-device.c:7019]
> nm_device_add_pending_action(): [0x213c268] (mlan0):
> add_pending_action (1): 'scan'
> May 18 14:33:31 canect2 daemon.info NetworkManager[245]: 
> [1495118011.702526] [devices/nm-device.c:7052]
> nm_device_remove_pending_action(): [0x213c268] (mlan0):
> remove_pending_action (0): 'scan'
> May 18 14:33:31 canect2 user.alert kernel: [149885.509332] wlan:
> mlan0 START SCAN
> May 18 14:33:33 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (idle -> searching)
> May 18 14:33:33 canect2 daemon.info NetworkManager[245]: 
> [1495118013.317075] [platform/nm-linux-platform.c:1950]
> event_notification(): netlink event (type 16) for link: mlan0 (6,
> family 0)
> May 18 14:33:33 canect2 daemon.info NetworkManager[245]: 
> [1495118013.317486] [platform/nm-linux-platform.c:426]
> get_kernel_object(): get_kernel_object for link: mlan0 (6, family 0)
> May 18 14:33:33 canect2 daemon.info NetworkManager[245]: 
> [1495118013.318059] [platform/nm-linux-platform.c:1950]
> event_notification(): netlink event (type 16) for link: mlan0 (6,
> family 0)
> May 18 14:33:33 canect2 daemon.info NetworkManager[245]: 
> [1495118013.318402] [platform/nm-linux-platform.c:426]
> get_kernel_object(): get_kernel_object for link: mlan0 (6, family 0)
> May 18 14:33:33 canect2 user.warn kernel: [149887.121037] wlan: SCAN
> COMPLETED: scanned AP count=12
> May 18 14:33:33 canect2 user.err kernel: [149887.134455] Invalid
> sched_scan req parameter
> May 18 14:33:47 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (searching -> idle)
> May 18 14:33:52 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (idle -> searching)
> May 18 14:33:52 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (searching -> idle)
> May 18 14:33:57 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (idle -> searching)
> May 18 14:33:57 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (searching -> idle)
> May 18 14:34:02 canect2 daemon.info ModemManager[423]:   Modem
> /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> changed (idle -> searching)
> May 18 14:34:03