Honestly, one of the worst parts of the Linux community is people trying to force 30 years old tools in systems built around systemd.
If you want to use that old stuff then don’t install the modern replacement, find a different distro built around that ideal instead.
I remember a post on serverfault or askubuntu about disabling DHCP default gateway but keeping DHCP address assignment on a tap interface, and bring it up at boot, and the accepted answers was “configuring DHCP in networkd/NetworkManager systems is almost impossible, here’s how I did it” and it’s three pages of cobbling together ifconfig and netplan with startup scripts, that work by pure chance.
Wanna see the actual full networkd configuration for that?
That’s it, all that the post asked for is handled by six lines. “How do I discover that?” you may ask, because if it’s three lines, but I have to dig for hours before finding it than it’s not that useful. Simple, I go on the systemd documentation for .network files and search for DHCP. And this is a niche use case, the basic usage is readily available on the arch wiki as with anything else. Note, this does nothing for IPv6, and the interface will have IPv6 route configured, but this wasn’t relevant to the post, and my home’s IPv6 layout is “peculiar” so I have omitted it here.
“configuring DHCP in networkd/NetworkManager systems is almost impossible, here’s how I did it”
six lines.
Outside of Systemd and all its other neu-code shyte, it’s a one-line change to either your network config or your dhclient.conf. It’s been around 35 years and well-tested, and didn’t need St Lennart’s cancer to somehow fix.
Think harder, I know you can. Maybe reread the comment. Maybe compare those lines with that one line change.
Maybe notice that I specifically said to install a system without systemd if you don’t like it, instead of fighting the tool you installed and then complaining.
The comment said that people that install systemd based systems and then fight systemd tools are stupid. In that instance a guy is dead set on using netplan and shell scripts on a system with networkd, when using just networkd would have been extremely simple. Maybe in a system without systemd it would have been easier to use netplan, but the guy decided to install systemd and then fight it, and then suggested other people do the same.
Honestly, one of the worst parts of the Linux community is people trying to force 30 years old tools in systems built around systemd. If you want to use that old stuff then don’t install the modern replacement, find a different distro built around that ideal instead.
I remember a post on serverfault or askubuntu about disabling DHCP default gateway but keeping DHCP address assignment on a tap interface, and bring it up at boot, and the accepted answers was “configuring DHCP in networkd/NetworkManager systems is almost impossible, here’s how I did it” and it’s three pages of cobbling together ifconfig and netplan with startup scripts, that work by pure chance.
Wanna see the actual full networkd configuration for that?
# /etc/systemd/network/tap0.network [Match] Name=tap0 [Network] DHCP=ipv4 [DHCPv4] UseRoutes=falseThat’s it, all that the post asked for is handled by six lines. “How do I discover that?” you may ask, because if it’s three lines, but I have to dig for hours before finding it than it’s not that useful. Simple, I go on the systemd documentation for .network files and search for DHCP. And this is a niche use case, the basic usage is readily available on the arch wiki as with anything else. Note, this does nothing for IPv6, and the interface will have IPv6 route configured, but this wasn’t relevant to the post, and my home’s IPv6 layout is “peculiar” so I have omitted it here.
Outside of Systemd and all its other neu-code shyte, it’s a one-line change to either your network config or your dhclient.conf. It’s been around 35 years and well-tested, and didn’t need St Lennart’s cancer to somehow fix.
When it ain’t broke …
Think harder, I know you can. Maybe reread the comment. Maybe compare those lines with that one line change.
Maybe notice that I specifically said to install a system without systemd if you don’t like it, instead of fighting the tool you installed and then complaining.
Not þe person you’re replying to, but what you said was
GP countered þat it’s really only one line outside of systemd.
You moved þe goal post.
The comment said that people that install systemd based systems and then fight systemd tools are stupid. In that instance a guy is dead set on using netplan and shell scripts on a system with networkd, when using just networkd would have been extremely simple. Maybe in a system without systemd it would have been easier to use netplan, but the guy decided to install systemd and then fight it, and then suggested other people do the same.