On 10/18/2018 11:30 PM, Thomas Haller wrote:
Btw, note that if you configure the device as unmanaged via
NM_CONTROLLED=no in ifcfg, then the device cannot be set to managed.
This way of unmanaging a device is definite,
Hello again, another use case I'm still wrapping my head around (even
with
On Wed, 2018-10-24 at 16:40 +0200, Thomas HUMMEL wrote:
> On 10/24/2018 04:11 PM, Thomas HUMMEL wrote:
>
> > > Reapply doesn't seem to have any relevance with modification or
> > > persistance.
> >
> > Yes so now my understanding of reapply is more like "restore" (to
> > its
> > original
On Thu, 2018-10-25 at 15:09 +0200, Thomas HUMMEL wrote:
> On 10/25/2018 03:05 PM, Thomas Haller wrote:
> > On Thu, 2018-10-25 at 14:58 +0200, Thomas HUMMEL wrote:
> > > On 10/24/2018 01:19 PM, Thomas Haller wrote:
> > >
> > >
> > > > Both the device and the profile must be willing to autoconnect
On Wed, 2018-10-24 at 19:58 +0200, Thomas HUMMEL wrote:
> On 10/24/2018 06:22 PM, Thomas Haller wrote:
>
> > Let's call this "externally managed". Not sure that's helpful, but
> > in
> > NetworkManager source code it's called like that.
> >
> > In nmcli output, you cannot really distinguish a
On 10/25/2018 03:05 PM, Thomas Haller wrote:
On Thu, 2018-10-25 at 14:58 +0200, Thomas HUMMEL wrote:
On 10/24/2018 01:19 PM, Thomas Haller wrote:
Both the device and the profile must be willing to autoconnect for
it
to happen. It's both ways. That's why you can suppress autoconnect
on
both
On Thu, 2018-10-25 at 14:58 +0200, Thomas HUMMEL wrote:
> On 10/24/2018 01:19 PM, Thomas Haller wrote:
>
>
> > Both the device and the profile must be willing to autoconnect for
> > it
> > to happen. It's both ways. That's why you can suppress autoconnect
> > on
> > both sides.
>
>
> Also,
