Jumping in in the middle of the conversation, but couldn't resist ....
On 11/7/24 10:23, Martin-Éric Racine wrote:
Claiming to offer a drop-in substitute all while nudging people
towards a new paradigm is not welcome.
If ifupdown's paradigm were working for people we wouldn't be having this
conversation.
[snip]
For my perspective, the main issues with ifupdown are:
1) ifupdown doesn't handle bridges and vlans without external
packages, yet it already depends upon iproute2, which provides 'ip'
i.e. a command that can handle these quite nicely.
2) ifupdown doesn't include a way to handle DHCPv6-PD for all
supported DHCP clients.
3) Since the introduction of systemd units, one can no longer rely on
interfaces being brought up sequentially following the order in which
they appear in /etc/network/interfaces.
4) That systemd unit generation blissfully ignores anything else that
physical interfaces in /etc/network/interfaces which introduces yet
more reproducibility problems.
Been working on-and-off on an alternative **guaranteed drop-in**
alternative for a while, for precisely the same reasons people are
mentioning in this thread.
Marco D'Itri, Marc Haber, Bernd Zeimetz, Simon Richter, Martin-Éric
Racine, Stephan Seitz, Daniel Gröber and others provided invaluable
feedback on this matter.
Should I be able to release something (maybe a far-fetched proposition)
more or less covering the need, what would be the *hard* requirements to
have it adopted ??
We are in the same need on my side; might as well not waste too much
effort needlessly :)
Thanks,
--
Parkinson's Law: Work expands to fill the time alloted to it.
