Netplan seems over-complicated – Info Linux

I just setup my first 18.04 system. First time installing Ubuntu since 2015-2014. I intend to use it as an iSCSI target server for my Proxmox environment and some Windows servers. However, I did not realize that Ubuntu has decided to retire ifupdown for netplan.

I have spent over 2 hours attempting to create a bonded interface using the two Ethernet ports on my server. Regardless of config, I can not get it to work. I followed multiple sample config walk-throughs and have almost completely copied serveral available .yaml files. There are a few open cases in Ubuntu's bug tracker and various other posts across the WAN implying that netplan and bonding are ‘broken' in 18.04.

I have attempted to get it to work using ifupdown, which I understand you can install afterwards and configure separately from netplan. This did not work due to the cloud-init service which is also new to me.

As I understand, netplan is intended to resolve some of the ‘hackiness' of ifupdown, similar to the way systemd replaced init scripts. However, if I can not get bonding to work, it is useless.

I don't want to toot my own horn, but I've been using since 2006 and have been configuring, administering and maintaining Linux systems for over 8 years now. If I can not get it to work, I have a hard time believing that most find it easy and or simple.

Is anyone else running into issues with networking on 18.04? In the meantime, I'm going to install Debian again.

Article Prepared by Ollala Corp

You might also like
Leave A Reply

Your email address will not be published.