> 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 your entire log. This is the entire log since reboot. If I look at the journal from previous boots, there are mentions of eth0 and eth1, as well as eno1 and eno2. $ networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eno1 ether off unmanaged 3 eno2 ether off unmanaged 4 eth0 ether off pending 5 eth1 ether off pending 6 bond0 bond no-carrier configured 7 docker0 bridge no-carrier unmanaged After doing ip link set dev {eth0,eth1} up, they change from off to degraded in networkctl list. Attempting the same on bond0 afterward does nothing. $ networkctl status -n 40 * State: no carrier Address: 172.17.0.1 on docker0 Dec 14 21:29:44 lore systemd[1]: Starting Network Service... Dec 14 21:29:44 lore systemd-networkd[852]: bond0: netdev ready Dec 14 21:29:44 lore systemd-networkd[852]: Enumeration completed. Dec 14 21:29:44 lore systemd[1]: Started Network Service. Dec 14 21:29:44 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 21:29:44 lore systemd-networkd[852]: bond0: Link UP Dec 14 21:31:44 lore systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE Dec 14 21:31:44 lore systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. Dec 14 21:31:44 lore systemd[1]: Failed to start Wait for Network to be Configured. Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 21:31:50 lore systemd-networkd[852]: docker0: Link UP Dec 15 18:13:43 lore systemd-networkd[856]: eth1: Link IP Dec 15 18:13:45 lore systemd-networkd[856]: eth0: Ganied carrier Dec 15 18:13:47 lore systemd-networkd[856]: eth0: Gained IPv6LL Dec 15 18:13:47 lore systemd-networkd[856]: eth1: Ganied carrier Dec 15 18:13:48 lore systemd-networkd[856]: eth1: Gained IPv6LL Dec 15 18:15:13 lore systemd-networkd[856]: bond0: Link DOWN Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Link DOWN Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Lost carrier Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Link DOWN Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Lost carrer All of the lines from today (Dec 15) correspond to my attempts to bring interfaces up as mentioned above, then bringing them back down after it failed. > networkctl status bond0 eth0 eth1 * 4: eth0 Link File: n/a Network File: n/a Status: off (pending) HW Address: 0c:c4:7a:c6:c6:a2 (Super Micro Computer, Inc.) MTU: 1500 (min: 68, max: 9710) Queue Length (Tx/Rx): 64/64 Auto negotiaition: yes Speed: n/a Port: tp Dec 14 21:29:42 lore systemd-udevd[588]: eth0: Failed to rename network interface 4 from 'eth0' to 'eno1': File exists Dec 14 21:29:42 lore systemd-udevd[588]: eth0: Failed to process device, ignoring: File exists Dec 15 18:13:45 lore systemd-networkd[856]: eth0: Ganied carrier Dec 15 18:13:47 lore systemd-networkd[856]: eth0: Gained IPv6LL Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Link DOWN Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Lost carrier * 5: eth1 Link File: n/a Network File: n/a Status: off (pending) HW Address: 0c:c4:7a:c6:c6:a2 (Super Micro Computer, Inc.) MTU: 1500 (min: 68, max: 9710) Queue Length (Tx/Rx): 64/64 Auto negotiaition: yes Speed: n/a Port: tp Dec 14 21:29:42 lore systemd-udevd[588]: eth1: Failed to rename network interface 5 from 'eth1' to 'eno2': File exists Dec 14 21:29:42 lore systemd-udevd[588]: eth1: Failed to process device, ignoring: File exists Dec 15 18:13:43 lore systemd-networkd[856]: eth1: Link IP Dec 15 18:13:47 lore systemd-networkd[856]: eth1: Ganied carrier Dec 15 18:13:48 lore systemd-networkd[856]: eth1: Gained IPv6LL Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Link DOWN Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Lost carrer * 6: bond0 Link File: /usr/lib/systemd/network/99-default.link Network File: /run/systemd/network/10-netplan-bond0.network Type: bond State: off (configured) Driver: bonding HW Address: 52:8b:2c:cc:a0:15 MTU: 1500 (min: 68, max: 65535) Queue Length (Tx/Rx): 16/16 Auto negotiation: no Speed: n/a Dec 14 21:29:44 lore systemd-networkd[852]: bond0: netdev ready Dec 14 21:29:44 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 21:29:44 lore systemd-networkd[852]: bond0: Link UP Dec 15 18:15:13 lore systemd-networkd[856]: bond0: Link DOWN It seems there's a naming conflict between the eth and eno devices. udevadm test-builtin net_id ... shows both enp3sf0 and enp5s0f0 should be eno1 and enp3sf1 and enp5s0f1 should be eno2