this triggers NM to behave as it should be
Am Mi., 21. Nov. 2018 um 19:47 Uhr schrieb Goran <[hidden email]>:
> Netplan is not installed. It is no dependency. So I guess it is not
> needed by NM.
> Am Mi., 21. Nov. 2018 um 19:42 Uhr schrieb Karl Auer <[hidden email]>:
> > On Wed, 2018-11-21 at 19:31 +0100, Goran wrote:
> > > So I went to /etc/network due to disable the interfaces file. But
> > > there is none.
> > >
> > > What else can I do?
> > Google "Ubuntu NetPlan"
> > --
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Karl Auer ([hidden email])
> > http://www.biplane.com.au/kauer > > http://twitter.com/kauer389 > >
> > GPG fingerprint: A0CD 28F0 10BE FC21 C57C 67C1 19A6 83A4 9B0B 1D75
> > Old fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A
> > --
> > ubuntu-users mailing list
> > [hidden email] > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> I'm booting a 18.04-Server image, which was installed via debootstrap. All fine.
> Further I installed network-manager to use is at the command prompt.
> My goal is to boot any server and connect via any ethernetcard I plug
> a cable into.
> When I invoke
> nmcli device status
> I get an
> enp9s0 ethernet unmanaged ---
> So I went to /etc/network due to disable the interfaces file. But there is none.
> What else can I do?
Doesn't the server edition default to systemd-networkd?
> On 2018-11-21 02:01 PM, Goran wrote:
>> My problem is solved with
>> touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
> As a follow-up, for anyone curious, the real problem is in the
> /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf file
> Touching the /etc copy just effectively nullifies it.
> The idea behind the default configuration is the belief that by default,
> NetworkManager is the preferred interface to manage Wifi Connections,
> but leave wired lan alone to the classic config.
Thanks for the info. Bizarre choice. But that's the way that it is...
> If you jump through the netplan hoops, it will change that for you if
> you specify Network Manager as your network configuration of choice.
> But I would have to go on an whole different rant about netplan :)
netplan's a good idea. It's just a question of learning its yaml
format. It would've been easier to use RH's ifcfg's familiar .ini
format (and variables) but that ship's sailed.