On Mon, Oct 16, 2023 at 9:56 AM Dale <
rdalek1967@gmail.com>
wrote:
<SNIP>
> Mark, the command nmcli you listed isn't installed on this
machine as it
> uses netplan. It seems netplan is new so maybe it is a
little buggy
> right now. I read that if I have netplan, I shouldn't
install other
> network managers, tools like ifconfig to see things is OK
but don't use
> those to "manage" the network. The use of two network
managers can and
> likely will cause a clash. That said, I do have ip and
route
> installed. Given it is working now, well, no need posting
the working
> results. ;-) Since Michael mentioned that netplan is new,
that
> explains why I wasn't getting many hits when searching.
It's new.
> There likely isn't many hits to find when searching, yet.
<SNIP>
netplan isn't new. It's been in Ubuntu since 16.04 LTS
which was
2015. What is new is making it the default way of handling
networks. I don't find it buggy and I don't know why you
cannot find
help in Google. I'm finding 100's of things to look at
without going
to 'Ask Ubuntu'
netplan status is nice because it shows who rendered a
network
whether netplan did it or not.
It is possible to have multiple renderers on the machine
but you
do have to configure things so they don't collide. I do
not
recommend you do anything like that.
For my Kubuntu desktops I actually use System Settings to
set fixed ip addresses but I do agree that cli
configuration
for Ubuntu Server can be confusing. However, complaining
about systemd in this day and age seems pointless. It's
here
and it isn't going away.