4 ms·

How about just shipping a networkd.conf(.d) config snippet and .network file with the wanted defaults. This is just another instance of I-hate-systemd-for-no-re

How about just shipping a networkd.conf(.d) config snippet and .network file with the wanted defaults. This is just another instance of I-hate-systemd-for-no-reason whining

simoncion 2y ago
> This is just another instance of I-hate-systemd-for-no-reason whining systemd appears to (whether deliberately, or through incompetence) ignore kernel configuration and do its own thing. That's a good reason to complain, don't you think?
egberts1 2y ago
Networkd is still missing the most crucial part of DHCP protocol: DHCP OPTIONS leg of the DHCP negotiation stage.
- jauntywundrkind 2y ago
  You've shown up twice to neg about this, but this isn't a problem with systemd-networkd's DHCP client. Right now there's no rules engine for the DHCP server to dynamically generate options. Sure, you can't embed Lua scripts in the server at this point. But bro, this has nothing to do with the discussion here. The DHCP client works fine, has no such concerns or issues. Stop blowing smoke.
  - egberts1 2y ago
    When having displaced the ISP-supplied DSL/ADSL/SDSL router at a premise using DHCP OPTIONS using a FreeBSD/Linux and ISC dhclient at many locations, and that is the client-side of DHCP. And ISP likes to have their custom routers (which is a DHCP client, BTW) respond in all sorts of funky ISP-specific DHCP key/value sets. Not just smoke. FIRE!
yjftsjthsd-h 2y ago
> This is just another instance of I-hate-systemd-for-no-reason whining This is a person actually examining it and specifically spelling out reasons why it's unsuitable.