Skip to content
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

Ensure persistence of network config during first boot, future boot and in case NICs physically get added or replaced #131

Open
Martin-Weiss opened this issue Dec 11, 2024 · 0 comments

Comments

@Martin-Weiss
Copy link

Just had the problem that durining initial installation the NIC was detected as ETH4 but after the first reboot the NIC was ETH0. So the load order of modules / race conditons etc. influence the NIC naming.

To persist this properly we have been creating udev rules based on PCI bus ID / SysFS or other ways (tried to avoid MAC addresses, because they change when NICs are replaced in existing devices).

-> could we get some sort of "create udev persistence" for the NICs NMC is configuring to avoid problems in case NICS are added / removed / replaced?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant