Agreement to relicense NetworkManager under LGPL-2.1+

Intel Corporation, by and through Mark Skarpness, Vice President and GM of IAGS-OISA-System Software Engineering, hereby agrees to relicense any contributions under Intel Corporation's copyright to NetworkManager under GNU LGPL-2.1+ as proposed by Thomas Haller. Specifically, this authorization

Re: What is needed for NetworkManager and WPA2 Enterprise?

On Wed, 25 Sep 2019 at 13:16, Paul Menzel wrote: > On 25.09.19 12:54, Andrew Zaborowski wrote: > > I believe there's now also an auto-configuration tool for eduroam > > called CAT. Maybe you should also address proposals to that project. > > When I was an eduroam user mysel

Re: What is needed for NetworkManager and WPA2 Enterprise?

On Wed, 25 Sep 2019 at 12:33, Paul Menzel wrote: > On 25.09.19 12:27, Andrew Zaborowski wrote: > > I replied to that issue but provisioning EAP networks other than > > through the config files is not currently on IWD's todo list. You > > didn't really explain your

Re: What is needed for NetworkManager and WPA2 Enterprise?

Hi Paul, On Wed, 25 Sep 2019 at 11:43, Paul Menzel wrote: > Could you please talk to the NetworkManager folks, what you need? I > created the issue *Extend D-Bus API for iwd and WPA2 Enterprise* in > their GitLab instance [2] for that. I replied to that issue but provisioning EAP networks other

Re: [RFC PATCH 0/8] Export IWD known networks as Connections

On 21 June 2018 at 15:17, Thomas Haller via networkmanager-list wrote: > First of all, I think that the NetworkManager profile (in NM's D-Bus > API) must abstract the Wi-Fi backend. Otherwise, all clients would need > to learn how to handle iwd-typed profiles. So, this hard work of > abstracting

[RFC PATCH 8/8] iwd: Register the IWD settings plugin

Add the IWD plugin to the build and use nm_settings_add_plugin to add its instance. The plugin is built into the wifi plugin's binary because with an independent binary it's difficult to cleanly listen to NMIwdManager's signals and call its methods. The meson configuration is not in this patch.

[RFC PATCH 7/8] settings: Add an IWD plugin

The plugin listens to NMIwdManager signals to add and remove connections for IWD's KnownNetworks. The connections are currently read-only and contain the minimum settings to mirror the information provided by IWD: the SSID and the security type. If this approach is taken the connections will

[RFC PATCH 6/8] libnm-core: 8021x: Allow a new eap value "extern"

To allow connections that mirror IWD's configured WPA-Enterprise networks to be seen as valid by NM, add a new value for the eap key in 802-1x settings. 802-1x.eap stores EAP method names. In the IWD connections we don't know what EAP method is configured and we don't have any of the other

[RFC PATCH 4/8] iwd: Add nm_iwd_manager_forget_network API

Add a function that maps to the net.connman.iwd.KnownNetworks.ForgetNetwork DBus call and causes an IWD Known Network to be forgotten with its config file removed. --- src/devices/wifi/nm-iwd-manager.c | 36 src/devices/wifi/nm-iwd-manager.h | 2 ++ 2 files

[RFC PATCH 2/8] wifi: Move KnownNetworkData to nm-iwd-manger.h

--- src/devices/wifi/nm-iwd-manager.c | 17 ++--- src/devices/wifi/nm-iwd-manager.h | 5 + 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/src/devices/wifi/nm-iwd-manager.c b/src/devices/wifi/nm-iwd-manager.c index 39db3a04c..2da6db0e4 100644 ---

[RFC PATCH 3/8] iwd: Emit known-networks-changed signals from NMIwdManager

Emit a signal when NMIwdManager learns that a KnownNetwork has been added or removed and when the list has been initially loaded. --- src/devices/wifi/nm-iwd-manager.c | 26 ++ src/devices/wifi/nm-iwd-manager.h | 3 +++ 2 files changed, 29 insertions(+) diff --git

[RFC PATCH 1/8] wifi: Move get_connection_iwd_security to nm-wifi-utils.c

Make this function public. I'm not sure if at this point it makes much sense to add a new file for iwd-specific utilities. --- src/devices/wifi/nm-device-iwd.c | 35 ++- src/devices/wifi/nm-wifi-utils.c | 23 +++

Re: How does IWD handle setting MAC address?

Hi, On 5 January 2018 at 14:58, Thomas Haller wrote: > For NM, at each moment not all its connection profiles are candidate > for connecting automatically. The list of which profiles can be > autoactivated depends on NM internal state, for example > - is the profile even

Re: How does IWD handle setting MAC address?

Hi, On 3 January 2018 at 20:58, Marcel Holtmann wrote: >> I think a valueable feature with NetworkManager + Wi-Fi + >> wpa_supplicant is that MAC address options. >> >> I tried to explain how that works here: >> >>

Re: [PATCH 3/4] devices/wifi: Add the wifi-backend config option

On 13 December 2017 at 17:21, Thomas Haller wrote: > there is a patch for review to do that: > > on https://github.com/NetworkManager/NetworkManager/pull/41 Great, I'll remove that from my own tasks then. The patches look good, I only added a small comment, in fact I had a

[PATCH 3/6] devices/wifi: Add NMDeviceIwd class to support IWD backend

This is very similar to NMDeviceWifi but simplified to remove the things currently unsupported and with calls to nm_platform_wifi_* and nm_supplicant_* replaced with IWD DBus API calls. Only unsecured infrastructure-mode networks are supported here. --- Makefile.am |6 +

[PATCH 6/6] devices/wifi: Register an IWD PSK agent on dbus

Add the PSK agent support to support PSK networks. Note that the PSK itself will be saved by IWD on the first successful connection to the network and will not be updated when it is changed by the user on the NM side, this still needs fixing like a bunch of other problems. ---

[PATCH 4/6] devices/wifi: Track IWD devices, match to NMDeviceIwd objects

Add the NMIwdManager singleton to be responsible for matching NMDeviceIwd objects created from platform devices, to IWD Device dbus objects when they appear/disappear. --- Makefile.am | 4 +- src/devices/wifi/nm-device-iwd.c | 41 + src/devices/wifi/nm-device-iwd.h

[PATCH 2/6] devices/wifi: Move is_manf_default_ssid to nm-wifi-utils.c

Move the function for easier code reuse. --- src/devices/wifi/nm-device-wifi.c | 36 ++-- src/devices/wifi/nm-wifi-utils.c | 32 src/devices/wifi/nm-wifi-utils.h | 2 ++ 3 files changed, 36 insertions(+), 34 deletions(-) diff

[PATCH 5/6] devices/wifi: Add the wifi-backend config option

Let the config file select between creating classes of NMDeviceWifi (for the usual wpa_supplicant based devices) and NMDeviceIwd depending on the new NetworkManager.conf setting. --- src/devices/wifi/nm-wifi-factory.c | 23 --- src/nm-config.h| 1 + 2

[PATCH 1/6] devices/wifi: Move AP list utilities to nm-wifi-ap.c

Move three functions for easier code reuse. --- src/devices/wifi/nm-device-wifi.c | 111 ++ src/devices/wifi/nm-wifi-ap.c | 85 + src/devices/wifi/nm-wifi-ap.h | 8 +++ 3 files changed, 108 insertions(+), 96 deletions(-)

Re: [PATCH 3/4] devices/wifi: Add the wifi-backend config option

Hi, On 7 December 2017 at 08:22, Thomas Haller wrote: > Maybe the documentation should not say: > wpa_supplicant is also the default backend. > but instead: "if the setting is missing, it is autodetected.". > > -- although for now, it means to always ~detect~ supplicant. > >

Re: [PATCH 1/4] devices/wifi: Add NMDeviceIwd class to support IWD backend

On 7 December 2017 at 08:22, Thomas Haller <thal...@redhat.com> wrote: > On Tue, 2017-12-05 at 16:25 +0100, Andrew Zaborowski wrote: >> + >> +typedef struct { >> + GDBusObject * dbus_obj; >> + GDBusProxy *dbus_proxy; >> + GHashTable *

Re: [PATCH 3/4] devices/wifi: Add the wifi-backend config option

Hi Dan, On 5 December 2017 at 17:47, Dan Williams <d...@redhat.com> wrote: > On Tue, 2017-12-05 at 16:26 +0100, Andrew Zaborowski wrote: >> Let the config file select between creating classes of NMDeviceWifi >> (for the usual wpa_supplicant based devices) and NMD

[PATCH 2/4] devices/wifi: Track IWD devices, match to NMDeviceIwd objects

Add the NMIwdManager singleton to be responsible for matching NMDeviceIwd objects created from platform devices, to IWD Device dbus objects when they appear/disappear. --- Makefile.am | 4 +- src/devices/wifi/nm-device-iwd.c | 41 + src/devices/wifi/nm-device-iwd.h

[PATCH 4/4] devices/wifi: Register an IWD PSK agent on dbus

Add the PSK agent support to support PSK networks. Note that the PSK itself will be saved by IWD on the first successful connection to the network and will not be updated when it is changed by the user on the NM side, this still needs fixing like a bunch of other problems. ---

[PATCH 3/4] devices/wifi: Add the wifi-backend config option

Let the config file select between creating classes of NMDeviceWifi (for the usual wpa_supplicant based devices) and NMDeviceIwd depending on the new NetworkManager.conf setting. --- man/NetworkManager.conf.xml| 13 + src/devices/wifi/nm-wifi-factory.c | 23

Re: [RFC] IWD as wifi backend

Hi Thomas, On 30 November 2017 at 17:20, Thomas Haller wrote: > Maybe it's simpler to have just two indpendent types NMDeviceWifi (for > supplicant) and NMDeviceIwd. > > They both can implement the D-Bus interface > org.freedesktop.NetworkManager.Device.Wireless, there is no

Re: [RFC] IWD as wifi backend

Hi Thomas, Thanks for the motivating response, (sorry for breaking the threading, I only now confirmed subscription to the list) On Wed, 29 Nov 2017 09:12:20 +0100 Thomas Haller wrote: > Can you shortly comment on the plan (timetable) for first release of > iwd and whether there is an effort to

[RFC] IWD as wifi backend

Hi, I'd like to gather comments on integrating NetworkManager with IWD for Wifi support. IWD is a light-weight daemon that manages Wifi devices and provides a DBus interface: https://git.kernel.org/pub/scm/network/wireless/iwd.git/ It covers some wpa_supplicant functionality and some Network