If netplan is causing problems just get rid of it and use one of the older
methods.
Just add your devices in /etc/network/interfaces and disable network manager
and netplan.
FWIW Slackware doesnt bother with predictable network names. We still use eth0,
eth1 and so on. You have other options.
On Thu, Jul 8, 2021, 09:16 Chuck Hast wrote:
> For a desktop network manager does the magic. It sets things
> up for netplan, the yaml file is the netplan config file.
>
> But server does not use network manager because it is
> CLI only and NM is gui. It does us something called Subiquity
> to se
For a desktop network manager does the magic. It sets things
up for netplan, the yaml file is the netplan config file.
But server does not use network manager because it is
CLI only and NM is gui. It does us something called Subiquity
to set the network stuff up, but once done it appears that you
Also, this had some background information, including what appeared to
be how to revert to old behavior:
https://netplan.io/faq/
On Wed, Jul 7, 2021 at 5:50 PM Russell Senior wrote:
>
> Never heard of netplan. Went looking on a 20.04 desktop and found this:
>
> russell@vanhorn:~$ cat /etc/netp
Never heard of netplan. Went looking on a 20.04 desktop and found this:
russell@vanhorn:~$ cat /etc/netplan/01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
On Wed, Jul 7, 2021 at 5:42 PM Michael Barnes wrote:
>
>
On Wed, Jul 7, 2021 at 5:03 PM Chuck Hast wrote:
> No they were there the dmesg command brought them to the
> surface and the rest was just adding them to the yaml file for
> netplan, run netplan try and once happy netplan apply and THEN
> I could see them in all of the usual tools.
>
> The other
No they were there the dmesg command brought them to the
surface and the rest was just adding them to the yaml file for
netplan, run netplan try and once happy netplan apply and THEN
I could see them in all of the usual tools.
The other thing I have found out about the stupid subiquiti
installer i
I have never installed Ubuntu Server, but I find that surprising. By
default these days, interfaces will have "predictable" names, which I
think is kind of a misnomer, but afaik should show up in the output of
things like "ip a" or "ifconfig -a". It might be that your NIC needs
firmware to operate,
I had to add a nic card to an Ubuntu server. Appears that once the
server has been setup it will not recognize a new card. You have to
go in and find the port names, but in my case ifconfig, ip... etc only
showed me the functioning cards nothing else, I was finally able to
find them using dmesg |