I do like the diversity. You learn a few patterns and you can do them all. In the end basically the same but more flexible.
Somewhat. That means partially.
At least there arent 500 different ways to set a static IP.
Don’t get me wrong. I like Linux but I can’t get warm witg it as a desktop OS besides SteamDeck.
But I like it very much as a server OS.
MonkderVierte@lemmy.ml 1 day ago
sugar_in_your_tea@sh.itjust.works 1 day ago
So you’re saying you don’t like the choice in Linux? On a given distro, there’s usually one right way and maybe 2 other ways. Learn the right way for your setup and you’re good.
If you’re using Network Manager, do it the Network Manager way. If you’re using Debian as a server, do it the Debian way (`/etc/network/interfaces). If you’re using SUSE, do it the SUSE way (YaST).
If you don’t want to deal with it, use DHCP (usually default) and set the static lease on your router using the MAC address. That’s better anyway because you can change all of your static leases in one spot if you ever need to.
Appoxo@lemmy.dbzer0.com 1 day ago
I tried doing it the debian way and (I believe) followed the instructions of one of the debian manuals.
Problem: Most assume (like you) that the DHCP server is always on and able to give out adresses. But sometimes life is in the way (and in my case: offline for maintenance) and it doesnt work with the DHCP option.
sugar_in_your_tea@sh.itjust.works 1 day ago
Usually the DHCP server is the same as the router, so if the router is offline, you can’t access it anyway. Right?
Or are you saying you’d plug in directly with a patch cable?
Could you explain more about your network setup?
Appoxo@lemmy.dbzer0.com 1 day ago
My router is just that: A gateway
This follows a HW firewall (I intend to replace)
Behind that is