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
RFE: networkd: honour a new ID_NET_MANAGED_BY udev propery or so #29768
Comments
Since this obviously means NetworkManager needs to be on board too with this, @thom311 would this make sense to you? |
NetworkManager already honors Supporting a |
-> #29782. |
If the property is set, networkd manages the interface only when its value is "io.systemd.Network". Closes systemd#29768.
As discussed over at #29782 let's please clal the prop ID_NET_MANAGED_BY=, i.e. let's stick to the |
If the property is set, networkd manages the interface only when its value is "io.systemd.Network". Closes systemd#29768.
If the property is set, networkd manages the interface only when its value is "io.systemd.Network". Closes #29768.
…age device If ID_NET_MANAGED_BY= attribute is set, we have an indication who is responsible for the device. If this is set to anything but "org.freedesktop.NetworkManager", then the device is unmanaged. The effect is the same as setting NM_UNMANAGED= attribute. NM_UNMANAGED= takes precedence over this setting. See-also: systemd/systemd#29768 See-also: systemd/systemd#29782
systemd/systemd#29768 systemd/systemd#29782 systemd/systemd#29767 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1413 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1414 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1780 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1779
If the property is set, networkd manages the interface only when its value is "io.systemd.Network". Closes systemd#29768.
Right now NetworkManager and networkd are happy to fight for ownership of network interfaces. That kinda sucks.
Here's an idea: let's make both unconditionally honour a NET_MANAGED_BY= udev property, and if set to any string that is different from some identifier for the respective project, the interfaces will be left unmanaged.
And example:
If the property is not set we'll live in the wild-west as before.
What's the usecase?
Allowing the admin to make an explicit choice which project shall manage which interfaces. (Could even be generated dynamically via rules files in /run/)
What's not the usecase?
This is not a locking concept: if both NM and networkd are told to configure a device then they will still fight for it.
The text was updated successfully, but these errors were encountered: