Re: network manager post-up hook
On 2026-01-09 13:04, Greg Wooledge wrote:
I interpreted Michael's text to mean "I want all of my Linux
distributions, of which I use a wide variety, to be configured using
the same tools".
He's rejecting ifupdown solutions because he wants everything to look
like a Red Hat system.
No, I despise NM actually, but most of the systems I work on use it and
I have little choice in the matter. So I need to know it. Kinda like
systemd.
Actually I was impressed with iwd on Arch, although there was no desktop
integration.
I've been using *nix for roughly 30 years. I'm perfectly happy using
shell scripting and a bunch of symlinks for different profiles, and I
did do that for some time on a Debian laptop a few years ago.
May I go on the record as saying that systemd is also hideously
over-engineered, but then, I worked for years on a distro using
daemontools and then runit to manage services, which I find simpler. No
user-level services that way, but do we really need all this?
$ systemctl --user list-unit-files | wc -l
255
Ah well. Simpler times maybe.
Fact is, I love the simplicity and expressiveness of
/etc/network/interfaces. On my servers it's a no-brainer, although
integration with ipv6 seems lacking compared with *sigh*
systemd-networkd if you're a gateway trying to provide an ipv6 block for
your lan dynamically via prefix delegation ala
https://wiki.debian.org/IPv6PrefixDelegation.
I set up virt-manager on a kick-ass server in my basement for dev work,
and I love how simple it was to set up a bridged interface that way,
although it oddly goes down at times and it's hard to capture why.
# Create bridge device to handle all public traffic
auto br0
iface br0 inet static
# MAC tied to enp0s31f6
hwaddress ether 30:d0:42:e8:b9:b8
address 192.168.0.7
netmask 255.255.255.0
gateway 192.168.0.1
bridge_ports enp0s31f6
# don't need spanning tree
bridge_stp off
# if stp is off, set to 0. if stp is on, set to >= 2
bridge_fd 0
very readable. Very simple to back-up and restore. Love it.
Anyway, I ramble.
Mike
Reply to: