systemd/network: Fix dummy interface exclusion rule in default networkd unit#90
Conversation
The default networkd unit should not apply to all devices, e.g., not to bridges, tunnels, dummy interfaces etc. However, for dummy interfaces the rule was wrong. Fix the exclusion rule for dummy interfaces, which are not a type but a certain driver.
|
I don't know how to verify this PR. I was looking for a list of possible values for the |
|
Observing behavior like in natural science, not following rules on paper like in math or engineering ;) Actually it would be nice to submit our default network unit file as example in the systemd docs to spare others running into the same problems. |
Yeah, I was being lazy. :) Repeated the steps in a VM, seems to be doing the trick.
Right, there seem to be no example for configuring links as unmanaged. |
This pulls in flatcar/init#90 to fix the dummy interface exclusion rule in the default networkd unit. It was supposed to work before but didn't. With it we wouldn't have needed the special exclusions for Kubernetes interfaces.
This pulls in flatcar/init#90 to fix the dummy interface exclusion rule in the default networkd unit. It was supposed to work before but didn't. With it we wouldn't have needed the special exclusions for Kubernetes interfaces.
The default networkd unit should not apply to all devices, e.g., not to bridges, tunnels, dummy interfaces etc. However, for dummy interfaces the rule was wrong.
Fix the exclusion rule for dummy interfaces, which are not a type but a certain driver.
How to use
Testing done
Was tested by copying it to
/etc/systemd/network/and doingip link add dummy0 type dummyto create such an interface andnetworkctl reloadto apply the unit change and see that the interface becomes unmanaged.