Interestingly enough, the following information was recenly encountered regarding using netplan:
Change your /etc/netplan/01-netcfg.yaml to the following code (and only this)... using sudo -H gedit /etc/netplan/01-netcfg.yaml...
network:
version: 2
renderer: NetworkManager
Then, in terminal...
sudo netplan generate # generate config files
sudo netplan apply # apply configuration
note this message appeared but apparently did not apply to desktop configuration:
Cannot call Open vSwitch: ovsdb-server.service is not running.
reboot # reboot the computer
Then use the standard Network Manager GUI to establish a wired/wireless connection.
Note that sudo netplan generate would not execute if .yaml files in /etc/netplan contained a reference to 'random' generated MAC.
Note that sudo netplan would not execute if file permissions in /etc/netplan were too lenieent.
used chown to configure root:root and chmod at 600
It would appear that a routine apt upgrade from network-manager to network-manager/netplan is not making necessary changes/creating needed file structure.
This appears to be a bug, because only manual intervention appears to have enabled netplan to work without error messages and connection failures.
Interestingly enough, the following information was recenly encountered regarding using netplan:
Change your /etc/netplan/ 01-netcfg. yaml to the following code (and only this)... using sudo -H gedit /etc/netplan/ 01-netcfg. yaml...
network:
version: 2
renderer: NetworkManager
Then, in terminal...
sudo netplan generate # generate config files
sudo netplan apply # apply configuration
note this message appeared but apparently did not apply to desktop configuration: service is not running.
Cannot call Open vSwitch: ovsdb-server.
reboot # reboot the computer
Then use the standard Network Manager GUI to establish a wired/wireless connection.
Note that sudo netplan generate would not execute if .yaml files in /etc/netplan contained a reference to 'random' generated MAC.
Note that sudo netplan would not execute if file permissions in /etc/netplan were too lenieent.
used chown to configure root:root and chmod at 600
It would appear that a routine apt upgrade from network-manager to network- manager/ netplan is not making necessary changes/creating needed file structure.
This appears to be a bug, because only manual intervention appears to have enabled netplan to work without error messages and connection failures.
This should be addressed.