As someone who is currently attempting to set up a VM lab on Ubuntu Server 18.04, I am very much in agreement that netplan is an abomination. Finding a guide to get bridging working with netplan is a nightmare too. Canonical has vexed me yet again.
What if i install clean ubuntu desktop 18.04.3 LTS and there was netplan and network manager in the same time? What actually controls the network? How to find it out? I always used DHCP as ordinary user, but now I want to understand networking in modern Ubuntu and it seems to me like a mindblowing chaos if you have to configure something static or take controll over automatic configuration like in case of configuring big networks with plenty of hosts. Btw, i saw yaml language in the different project and it is really bad approach, which is hard to understand without tons of documentation and if documentation is missing or wrong, then it is nightmare.
Martin Brakl I just remove netplan as a first step. I use FreeBSD, OpenBSD, and several Linux distributions, and nothing approaches the annoyance of netplan. It’s easy to remove, it just needs to be done in the right order and replaced successfully. Also, if you ever find a system that has removed ifconfig for ip addr type commands, you can install net-tools to reinstall ifconfig. This will give you the most interoperable environment across UNIX, Linux, old, and new.
I just remove netplan as a first step. I use FreeBSD, OpenBSD, and several Linux distributions, and nothing approaches the annoyance of netplan. It’s easy to remove, it just needs to be done in the right order and replaced successfully. Also, if you ever find a system that has removed ifconfig for ip addr type commands, you can install net-tools to reinstall ifconfig. This will give you the most interoperable environment across UNIX, Linux, old, and new.
The interface config is then very straightforward. /etc/network/interfaces. Example: ip address 10.10.10.12 netmask 255.255.255.0 gateway 10.10.10.1 dns-nameservers 1.1.1.1 4.2.2.2 8.8.8.8
Thank you for the note! I am always excited to see someone taking an alternative path to administration. I began these videos as an opportunity to help guide statements much like this. In every sense of the response, this support for yaml files is trendy and fashionable and seems innocuous enough; however, this debate goes back to UNIX and Linux System Administration techniques that have been in use for over 40 years. YAML is rare and young (it is only about 20 years old at max, and not common.) On an average Linux system, there are 11 YAML files, 1551 .config files, and 9102 .conf files in common usage. This means that .yaml comprises only 0.001032573 of the configuration files on the system. Or, to put differently, 99.9% of the text-based configuration files in a normal Linux box are not yaml. YAML attempts to provide a new method of text configuration that improves upon xml, sgml, text, and others for tasks that are often better controlled in structured text. In this, it fails. Net Plan, NMCLI, and Systemd-networkd are also current trends that are available in some systems and not in others. YAML and NetPlan complicate the uncomplicated and create a programmatic, heavily-structured textual system that is difficult for cli parsing across distributed clusters. This complication costs administrators years of lost hours and broken systems. It prevents generations of new administrators from attempting Linux and UNIX because they find the unforgiving syntax of yaml painful and difficult to use. A great reference for your research would be Eric Raymond's book, The Art of Unix Programming. An example quote, "Unix is not so much an operating system as an oral history." - Eric Raymond. The first portion of the book is available to read for free on Amazon. www.amazon.com/UNIX-Programming-Addison-Wesley-Professional-Computng/dp/0131429019 I posted some of the commands to compare the extent of yaml to config to conf at pastebin from one of my BSD boxes: pastebin.com/VQdi7N7i I hope that this explanation helps inform everyone in the community about the dangers of complicating the simple.
I liked the "burned with fire" part.
this brings me joy
i follow some of your steps. in my arm device i have to install isc-dhcp-client package so i can have DHCP.
Thank you, you are a hero!
As someone who is currently attempting to set up a VM lab on Ubuntu Server 18.04, I am very much in agreement that netplan is an abomination. Finding a guide to get bridging working with netplan is a nightmare too. Canonical has vexed me yet again.
What if i install clean ubuntu desktop 18.04.3 LTS and there was netplan and network manager in the same time? What actually controls the network? How to find it out?
I always used DHCP as ordinary user, but now I want to understand networking in modern Ubuntu and it seems to me like a mindblowing chaos if you have to configure something static or take controll over automatic configuration like in case of configuring big networks with plenty of hosts.
Btw, i saw yaml language in the different project and it is really bad approach, which is hard to understand without tons of documentation and if documentation is missing or wrong, then it is nightmare.
Martin Brakl I just remove netplan as a first step. I use FreeBSD, OpenBSD, and several Linux distributions, and nothing approaches the annoyance of netplan. It’s easy to remove, it just needs to be done in the right order and replaced successfully. Also, if you ever find a system that has removed ifconfig for ip addr type commands, you can install net-tools to reinstall ifconfig. This will give you the most interoperable environment across UNIX, Linux, old, and new.
I just remove netplan as a first step. I use FreeBSD, OpenBSD, and several Linux distributions, and nothing approaches the annoyance of netplan. It’s easy to remove, it just needs to be done in the right order and replaced successfully. Also, if you ever find a system that has removed ifconfig for ip addr type commands, you can install net-tools to reinstall ifconfig. This will give you the most interoperable environment across UNIX, Linux, old, and new.
The interface config is then very straightforward. /etc/network/interfaces.
Example:
ip address 10.10.10.12
netmask 255.255.255.0
gateway 10.10.10.1
dns-nameservers 1.1.1.1 4.2.2.2 8.8.8.8
Netplan is a pain but you need to get use to YAML because its everywhere. You also have other options such as nmcli or systemd-networkd.
Thank you for the note! I am always excited to see someone taking an alternative path to administration. I began these videos as an opportunity to help guide statements much like this. In every sense of the response, this support for yaml files is trendy and fashionable and seems innocuous enough; however, this debate goes back to UNIX and Linux System Administration techniques that have been in use for over 40 years. YAML is rare and young (it is only about 20 years old at max, and not common.) On an average Linux system, there are 11 YAML files, 1551 .config files, and 9102 .conf files in common usage. This means that .yaml comprises only 0.001032573 of the configuration files on the system. Or, to put differently, 99.9% of the text-based configuration files in a normal Linux box are not yaml. YAML attempts to provide a new method of text configuration that improves upon xml, sgml, text, and others for tasks that are often better controlled in structured text. In this, it fails. Net Plan, NMCLI, and Systemd-networkd are also current trends that are available in some systems and not in others. YAML and NetPlan complicate the uncomplicated and create a programmatic, heavily-structured textual system that is difficult for cli parsing across distributed clusters. This complication costs administrators years of lost hours and broken systems. It prevents generations of new administrators from attempting Linux and UNIX because they find the unforgiving syntax of yaml painful and difficult to use. A great reference for your research would be Eric Raymond's book, The Art of Unix Programming. An example quote, "Unix is not so much an operating system as an oral history." - Eric Raymond. The first portion of the book is available to read for free on Amazon. www.amazon.com/UNIX-Programming-Addison-Wesley-Professional-Computng/dp/0131429019 I posted some of the commands to compare the extent of yaml to config to conf at pastebin from one of my BSD boxes: pastebin.com/VQdi7N7i I hope that this explanation helps inform everyone in the community about the dangers of complicating the simple.
Those developers must be indentation nazis. Makes my blood boil.
Such a crap software it is indeed. First thing after installing a modern Ubuntu is to remove Netplan! The same applies to systemd-resolved.