Quick check
Problem or use case
Similarly to #284, I don't use NetworkManager, instead I configure wpa_supplicant directly for connecting to wifi (and use systemd-networkd as my DHCP server).
Proposed solution
It would be great if I could get basic info about the connected network. wpa_supplicant provides a CLI as well as a d-bus interface AFAIK, so this should be possible. Implementing active features or actions like scanning is optional, although it would certainly be welcome, and I don't believe it adds significantly more burden on top of the passive features, as wpa_cli has the same interface for those. Alternatively, if systemd-networkd provides all necessary info, that would also work, although obviously then it would not be possible to support actions.
Alternatives considered
No response
Related area
Configuration
Quick check
Problem or use case
Similarly to #284, I don't use NetworkManager, instead I configure wpa_supplicant directly for connecting to wifi (and use systemd-networkd as my DHCP server).
Proposed solution
It would be great if I could get basic info about the connected network. wpa_supplicant provides a CLI as well as a d-bus interface AFAIK, so this should be possible. Implementing active features or actions like scanning is optional, although it would certainly be welcome, and I don't believe it adds significantly more burden on top of the passive features, as wpa_cli has the same interface for those. Alternatively, if systemd-networkd provides all necessary info, that would also work, although obviously then it would not be possible to support actions.
Alternatives considered
No response
Related area
Configuration