Comments on: How to Configure Network Bonding or Teaming in Ubuntu

By: Ravi Saive

Ravi Saive — Thu, 15 Apr 2021 06:04:11 +0000

In reply to Spar.

@Spar,

Thanks, corrected the variable in the configuration…

By: Spar

Spar — Wed, 14 Apr 2021 16:24:35 +0000

There is a typo in the interfaces config example:

bound_updelay 200

Should be:

bond_updelay 200

By: LInux Guy

LInux Guy — Sat, 03 Apr 2021 14:50:16 +0000

Thank you for your post! Where can I find information about adding network redundancy, not just link redundancy?. Specifically, connecting a single server with 2 NIC’s to 2 separate switches. I’m more worried about a switch failure in the network; it’s the weak link that would shut the whole system down completely. Ideally, I’d have a redundant network allowing (at bare minimum) out-of-band access to remote servers through Telnet, SSH, or web GUI’s.

Link Aggregation also requires configuration on a switch… meaning a minimum of a QUAD port NIC. If I have only 2 ports, I’m splitting them between switches, not bonding them. So it seems that link aggregation (to me) is a conversation only after network redundancy/stability is achieved. Can you recommend any specific articles or resources?

By: Patrick Wingert

Patrick Wingert — Sun, 16 Aug 2020 00:14:45 +0000

Now that Unbuntu in 20.04 is using Netplan what do I need to do to configure a real server (HPE dl60 H9) with two network interfaces at 192.168.3.24 and 192.168.3.25 as fixed IP with no DHCP and binded into a single interface? Can I still use these commands or do I have to figure out the arcane syntax of Netplan?

By: Vitaly

Vitaly — Fri, 05 Jun 2020 13:11:18 +0000

I’m trying to bond enp3s0 and wlp4s0 interfaces connected to one wireless repeater.

enp3s0 is connected to ap2, which is connected to ap1.

wlp4s0 is directly connected to ap1.

So they are getting IP from one source.

As enp3s0 first gets ip it’s working fine, but wlp4s0 doesn’t get IP because of error:

wlp4s0: IAID conflicts with one assigned to enp3s0

CTRL-EVENT-DISCONNECTED bssid=bc:ee:7b:90:74:c8 reason=4 locally_generated=1

wlp4s0: IAID 03:d7:8c:63
Jun 05 11:30:45 fallback-os dhcpcd[23163]: wlp4s0: IAID conflicts with one assigned to enp3s0
Jun 05 11:30:45 fallback-os dhcpcd[23163]: wlp4s0: adding address fe80::3e65:1ccc:341a:27c9
Jun 05 11:30:45 fallback-os dhcpcd[23163]: wlp4s0: soliciting a DHCP lease
Jun 05 11:30:46 fallback-os dhcpcd[23163]: wlp4s0: offered 192.168.1.178 from 192.168.1.254
Jun 05 11:30:46 fallback-os dhcpcd[23163]: wlp4s0: soliciting an IPv6 router
Jun 05 11:30:46 fallback-os dhcpcd[23163]: wlp4s0: probing address 192.168.1.178/24
Jun 05 11:30:46 fallback-os dhcpcd[23163]: wlp4s0: hardware address f8:1a:67:5c:7c:e2 claims 192.168.1.172

It would be great if someone could help to resolve this issue.