Open nullr0ute opened 5 years ago
As requested by @kgiori for Fedora IoT context.
Hi @nullr0ute,
What exactly is it you want to do with this? Is the idea that you want network settings to work across both Raspbian and Fedora with the same implementation?
For 2019 our main focus is going to be OpenWrt, which uses ubus by default. However, as long as we continue to support Raspbian there may be some reason to do this.
@benfrancis well I'm focused on Fedora but it would make it much easier to use across generic distributions. I've been working with @kgiori so you might want to sync with her.
@nullr0ute - indeed a platform agnostic approach to network config seems best for Fedora. while Mozilla's IoT team is looking at doing this for ubus on OpenWrt, any chance someone from your team can propose a solution for dbus? or point me where to look for similar open source solutions to a project like this?
This should now be possible by adding a new platform here: https://github.com/mozilla-iot/gateway/tree/master/src/platforms
@mrstegeman to add a new "platform", do you mean define them by distro, such as linux-debian, linux-fedora, ... ?
Yes. That’s how things are currently set up.
The majority of mainstream distributions use NetworkManager for WiFi and other network configuration. It allows configuration using a well documented API over dbus which abstracts all the various distribution backends away from the Things Gateway, as well as allowing configuration by a standard user, or to run in a constrained container with access to the dbus.
It would also allow changing the WiFi backends (wpa_supplicant, iwd etc) without having to changing any code.
It support connecting to wired, wireless as well as configuring a WiFi AP (#895).
It would also integrate well for issues like #1596 and integrate well with #423
dbus API is well documented: https://developer.gnome.org/NetworkManager/stable/spec.html https://developer.gnome.org/NetworkManager/stable/nm-dbus-types.html