Thank you for all of your help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908140
Title:
Bond DHCP fails on Ubuntu Server 20.04 netplan
To manage notifications about this bug go to:
The BIOS update does indeed fix the type interface number issue. This
ticket can be marked as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141 and closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's a BIOS update available for my board. I'll install this and
hopefully I won't need a SW fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908140
Title:
Bond DHCP fails on Ubuntu Server
I thought this could be related to
https://bugzilla.kernel.org/show_bug.cgi?id=199813. Indeed dmidecode -t
41 shows there are two interfaces for type interface 1 and two for 2.
** Bug watch added: Linux Kernel Bug Tracker #199813
https://bugzilla.kernel.org/show_bug.cgi?id=199813
--
You
> your bonded links are down; nothing will happen until they are brought
up.
Yes, I figured as such. I've already tried to bring up eth0, eth1, and
bond0 via ip, ifup, and ifconfig to no success.
> your pasted log appears incomplete since i see no output for eth0 or
eth1; please paste or attach
> please paste or attach your entire log
if that *is* your entire log, then please include the output of:
$ networkctl list
$ networkctl status
$ networkctl status bond0 eth0 eth1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> eth0: mtu 1500 qdisc noop state DOWN group default qlen
> 1000
> eth1: mtu 1500 qdisc noop state DOWN group default qlen
> 1000
your bonded links are down; nothing will happen until they are brought
up.
> $ sudo journalctl -b -u systemd-networkd
...
your pasted log appears incomplete
