Hmmm, I’m pretty sure you just need to systemctl disable sshd.socket and then configure it how you like. Don’t trust every “solution” you see online, they are often full of bullshit written by people trying to fit a square peg in a round hole. I bet that kernel parameter thing is something to disable it on the first boot, before you get the chance to configure the thing properly.
Edit:
@thorhop@sopuli.xyz wrote a comment about that option here, go to the thread if you are interested.
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.
Hmmm, I’m pretty sure you just need to
systemctl disable sshd.socketand then configure it how you like. Don’t trust every “solution” you see online, they are often full of bullshit written by people trying to fit a square peg in a round hole. I bet that kernel parameter thing is something to disable it on the first boot, before you get the chance to configure the thing properly.Edit: @thorhop@sopuli.xyz wrote a comment about that option here, go to the thread if you are interested.
This! Disable sshd sock, maybe rebuild initramfs.
And, the “kernel command line” is also used by the initramfs for fucks sake …
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.