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
> >
>
> -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
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 Wed, 2017-05-17 at 21:28 -0600, Phil Daum wrote:
> Hi Dan,
>
> Now that I had a 3G connection working on my Sierra Wireless MC7354
> (thanks
> to you), I would like to utilize the on-board GPS. I was wondering
> if I
> could ask you a general question:
>
> Is the use of gpsd compatible with t
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) i
Hi.
2017-05-18 12:22 GMT-04:00 Beniamino Galvani :
> On Thu, May 18, 2017 at 11:42:47AM -0400, Nikolay Martynov wrote:
>> Just to clarify: this patch only affects wifi bonded connections.
>> 'Classic' ethernet bond slaves are still skipped - so this change
>> should not affect existing users.
>> I
On Thu, May 18, 2017 at 11:42:47AM -0400, Nikolay Martynov wrote:
> Just to clarify: this patch only affects wifi bonded connections.
> 'Classic' ethernet bond slaves are still skipped - so this change
> should not affect existing users.
> I think the intention of original patch was to hide etherne
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 NetworkMan
Hi.
Thanks for your response!
2017-05-18 11:32 GMT-04:00 Thomas Haller :
> On Tue, 2017-05-16 at 22:13 -0400, Nikolay Martynov wrote:
>> If slave connection is a wifi connection we should still display it
>> Otherwise this AP gets scanned regardless, but when user clicks it
>> new
>> network is c
On Tue, 2017-05-16 at 22:13 -0400, Nikolay Martynov wrote:
> If slave connection is a wifi connection we should still display it
> Otherwise this AP gets scanned regardless, but when user clicks it
> new
> network is created in NM's configuation - which is unlikely what user
> desired
Hi Nikolay,
11 matches
Mail list logo
