Cockpit: [Feature request] Make cockpit compatible with systemd-networkd besides NetworkManager

[q2dg]

Hello

Here (http://cockpit-project.org/guide/latest/feature-networkmanager.html) it is said Cockpit uses D-Bus API offered by NetworkManager to interact with system's network configuration.

Could it be possible that Cockpit had the same behavior but running on systemd-networkd service (that is to say: could it recognize and manage .netdev/.network/.link files?)

Thanks!

PD: I don't know if systemd-networkd offers a D-Bus API like NetworkManager does. Sorry if this issue is a silliness, then.

[raneon]

This would be nice, originally I removed NetworkManager from all my servers and I only had to add it again as of cockpit, but my network is still managed by systemd-networkd.

[q2dg]

I've put a Feature Request on Systemd GitHub: https://github.com/systemd/systemd/issues/7593

[martinpitt]

Marking as blocked, until networkd gets an API (D-Bus or varlink or similar).

[enaut]

some network functionality has been exposed to D-Bus see:
https://github.com/systemd/systemd/blob/v243-rc1/src/network/org.freedesktop.network1.policy

The implemented features are mostly dns settings:

• org.freedesktop.network1.set-ntp-servers
• org.freedesktop.network1.set-dns-servers
• org.freedesktop.network1.set-domains
• org.freedesktop.network1.set-default-route
• org.freedesktop.network1.set-llmnr
• org.freedesktop.network1.set-mdns
• org.freedesktop.network1.set-dns-over-tls
• org.freedesktop.network1.set-dnssec
• org.freedesktop.network1.set-dnssec-negative-trust-anchors
• org.freedesktop.network1.revert-ntp
• org.freedesktop.network1.revert-dns

[q2dg]

Regarding to this...do you think this list of currently implemented systemd-networkd's items is enough for using it as a viable Cockpit's backend: https://github.com/systemd/systemd/issues/7593#issuecomment-713131716 ?
Thanks a lot