Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Applying systemd-networkd configuration disconnects all other interfaces #6078
systemd version the issue has been seen with
In case of bug report: Expected behaviour you didn't see
In case of bug report: Unexpected behaviour you saw
In case of bug report: Steps to reproduce the problem
I am not sure I follow. networkd only takes possession of interfaces you are telling it to take possession of. "networkctl status -a" will tell you which interfaces it takes care and which .network file it applies to each...
It appears to me your .network file [Match] section is simply too broad and applies to network interfaces it really shouldn't apply to?
no, I match by name, that's not the thing.
There should be a possibility to bring up an interface on-the-fly with no impact to other interfaces (like ifup eth1).
Also, if you'd like to change the configuration of an interface which is already configured by systemd (e.g. IP, Gateway, whatever), you need to restart the whole service (systemctl restart systemd-networkd). As said, this will also bring down all other interfaces (where I didn't change anything). With ifupdown, you have the possibility to restart just a single interface (ifdown ethX && ifup ethX).