-
-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
Support more network interface types in systemd-initrd #251388
Comments
@ElvishJerricco I think this is your area of expertise. Can you let me know if the approach in #251290 looks good for addressing these? Thanks! |
I can take part of this one on. I've done
and I can do these. How many of these do we need NixOS tests for, vs. getting them just generated and expressible in the NixOS module? |
NixOS tests would be good to have for these. If someone makes a change to the initrd environment that affects these options (e.g. changing available kernel modules), it's not straightforward to manually test an initrd with bridging, tunneling, etc. There are test examples in #251290 that should help. |
For ipvlan/ipvtap, it looks like there are no corresponding Of course, it would be great to have ipvlan/ipvtap working in initrd with networkd. [EDIT] Yeesh, here I am misunderstanding my own issue text. The |
With systemd-initrd and initrd networking enabled, we can use
networking.interfaces
to automatically configure interfaces in stage 1. Some network configuration that we support in a fully booted system is not supported in stage 1, however:networking.bridges
(#251290)networking.bonds
networking.macvlans
networking.fooOverUDP
networking.sits
networking.greTunnels
networking.vlans
(#251290)At least some of these can be supported without much difficulty.
The text was updated successfully, but these errors were encountered: