> ifup and ifdown are thus unavailable, replaced by ip link set $device up and ip link set $device down.
That's weird, they do two very different things. ifup and ifdown apply / unapply the configuration in /etc/network/interfaces, like setting IP addresses, setting routes, running other commands you might have like configuring card-specific hardware things or sending notifications to other processes, etc. ip link set dev $dev up/down only enables or disables the card. They also require the card to exist already, in the case of bridges or bonds or VLANs or similar things.
Does netplan cause all of these things to be done automatically when the card is upped or downed?
> ifconfig ... staple of a proper Linux installation to me.
To be honest, I have a lot of muscle memory for ifconfig because it's what I grew up with, but also Linux's ifconfig has gotten very different from the BSD ifconfig (or ifconfigs? I know FreeBSD's and macOS's support different things), so it's not like it was a standard tool across UNIXes, just a standard name. I'm honestly happier with the Linux tool having its own name.
Also, ip supports things that ifconfig straight-up doesn't, like having multiple IP addresses on an interface (without configuring alias interfaces), creating various types of virtual devices, creating VLANs without using an even more awful tool, getting card stats (ip -s -s link) in a vendor-neutral way, etc.
I do really really hate the ip command's syntax though.
That's weird, they do two very different things. ifup and ifdown apply / unapply the configuration in /etc/network/interfaces, like setting IP addresses, setting routes, running other commands you might have like configuring card-specific hardware things or sending notifications to other processes, etc. ip link set dev $dev up/down only enables or disables the card. They also require the card to exist already, in the case of bridges or bonds or VLANs or similar things.
Does netplan cause all of these things to be done automatically when the card is upped or downed?
> ifconfig ... staple of a proper Linux installation to me.
To be honest, I have a lot of muscle memory for ifconfig because it's what I grew up with, but also Linux's ifconfig has gotten very different from the BSD ifconfig (or ifconfigs? I know FreeBSD's and macOS's support different things), so it's not like it was a standard tool across UNIXes, just a standard name. I'm honestly happier with the Linux tool having its own name.
Also, ip supports things that ifconfig straight-up doesn't, like having multiple IP addresses on an interface (without configuring alias interfaces), creating various types of virtual devices, creating VLANs without using an even more awful tool, getting card stats (ip -s -s link) in a vendor-neutral way, etc.
I do really really hate the ip command's syntax though.