-
-
Notifications
You must be signed in to change notification settings - Fork 49
CLASS SYSTEMD_NETWORKD #318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
crpb
commented
Apr 13, 2025
- Add systemd-networkd class and a default dhcp-fallback configuration to catch any unconfigured network interfaces which might likely be the case.
mika
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it, @zeha what's your take on this?
I think it conflicts with what we're doing in grml-network, etc. I'm not sure I understand the usecase. If it stays off by default, it doesn't provide much value. If it becomes on by default, we should drop grml-network and so on. |
Good point indeed, we should discuss whether and if at all, how we could move towards systemd-networkd or network-manager as the default, netcardconfig for sure would need to be rewritten then though or find a proper TUI replacement for it. |
Let's do a release, then merge autoconfig et al into grml-live, and maybe then all of this becomes easier. I think right now this would only add churn, or worse, cement something we might not want to end up providing. |
|
btw, i only came up with that as i was irritated by dhcpcd's "duid" default. i tried to implement a cheatcode but grml-autoconfig is running to late from what i can tell so far |
now i'm curious, what's that? |
|
no i mean, what do you not like about it?
|
* Add systemd-networkd class and a default dhcp-fallback configuration
to catch any unconfigured network interfaces which might likely be
the case.
677f1e6 to
72456b3
Compare