Comment 12 for bug 1945548

After additional discussion with other members, I retried with the same config as in comment #9:

CID: 202109-29496
SKU: AAEON UPN-EHL01
Image used: ubuntu-core-20-amd64+intel-iot.img.xz (20211014.2)
kernel: 5.13.0-1007-intel

Turns out, as Doug mentioned in comment #11, the UC20 configuration is based on the initial setup wizard when installing UC20. In my case, I had only plugged one of the two network interfaces (enp1s0), so only this one was configured. The other was marked as `disabled` and never used, even when plugging a cable afterwards.

The netplan configuration looked like this:

$ cat /etc/netplan/00-snapd-config.yaml
# This is the network config written by 'console-conf'
network:
  ethernets:
    enp1s0:
      dhcp4: true
  version: 2

In order to change this, I edited it like so:

$ cat /etc/netplan/00-snapd-config.yaml
# This is the network config written by 'console-conf'
network:
  ethernets:
    enp1s0:
      dhcp4: true
    enp2s0:
      dhcp4: true
  version: 2

then ran `sudo netplay apply`, and the second interface (enp2s0) got an IP shortly afterwards.

So, at least on my side (Aaeon EHL board), it's a non-issue.