Note that you should be able to simply run sudo console-conf, which is that first-boot setup you've already gone through. But it doesn't support more complex networking setups, so a more thorough answer is:
The Ubuntu Core images utilize netplan, and uses the systemd-networkd backend for it. I don't have a Joule on hand, but I have my Dragon board here, and I used the first boot setup to configure a wired ethernet connection. Let me walk you through what I'd do with netplan to setup a wireless connection.
Modify /etc/netplan/00-snapd-config.yaml. This is the file generated by console-conf on first boot. Since I configured the wired connection on first boot, mine looked like this:
# This is the network config written by 'console-conf'
network:
ethernets:
eth0:
addresses: []
dhcp4: true
version: 2
Since I wanted to enable wifi, I updated this file to this:
# This is the network config written by 'console-conf'
network:
ethernets:
eth0:
addresses: []
dhcp4: true
wifis:
wlan0:
access-points:
<access point name>:
password: <password>
dhcp4: true
version: 2
Run sudo netplan generate to generate the necessary backend configuration for systemd-networkd.
- Run
sudo netplan apply to actually apply the new config.
You can run networkctl periodically and you'll see the interfaces come up.
networkctlshows: – Vahid Alimohamadi Feb 26 '20 at 11:25wpa-supplicant? There are a number of packages you don't get which are required for WiFi functionality when installing a system as "server" and then converting to a "desktop" (as I had to do because the desktop install media refused to even get to the installation UI). So I basically installed Ubuntu server, it came withnetplanand no bells and whistles andwpa-supplicantwas one of the missing puzzle-pieces. That was installed alongsidecinnamon-desktop-environment, though. – 0xC0000022L Jan 16 '21 at 23:07systemctl daemon-reloador I'd have wierd dhcp4 issues and state degraded status. – Ray Foss Jan 27 '21 at 21:00