Bug 87376

Summary: networkd - doesn't offer an access to its configuration process
Product: systemd Reporter: Brane2 <brankob>
Component: generalAssignee: Tom Gundersen <teg>
Status: RESOLVED WONTFIX QA Contact: systemd-bugs
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Brane2 2014-12-16 18:46:30 UTC
So, when something goes wrong, all I can do is restart the service, which mostly does nothing. And all that is left, is reboot.

If for some reason dhcp or some other component didn't do its job, I need to know it and have some mean of repairing it, like restarting the dhclient util.

Same goes for static routes. 

Say my card doesn't have a driver, so system can't see it. Or that I have had wrong MAC for it in the config.

When networkd doest it thing, I end up with inactive network. And I can't make networkd rescan the card and reconfigure it.

It's one-shot system, without any redundance. If it fails, it's doomed.

It would be nice to have some configureation setting for periodic rescanning failed interfaces etc.
Comment 1 Lennart Poettering 2015-02-03 16:33:55 UTC
Note sure I follow. Note that networkd doesn't really "scan" network devices, it simply subscribes to network interfaces coming and going. The kernel will notify it each time an interface is added or removed, that's all.

I am not really sure I understand what precisely is requested here?
Comment 2 Zbigniew Jedrzejewski-Szmek 2018-03-09 08:00:46 UTC
Closing all stale bugs with NEEDINFO. Please open a new bug at https://github.com/systemd/issues if the problem still occurs.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.