networkmanager
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
networkmanager [2021/04/14 22:31] Andrew Zaborowski wifi.iwd.autoconnect only landed in 1.30, not 1.28 |
networkmanager [2021/05/22 23:14] Andrew Zaborowski Bump header levels to make them show in the TOC |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Using IWD with Network Manager ==== | + | ===== Using IWD with Network Manager ===== |
| [[https://wiki.gnome.org/Projects/NetworkManager|Network Manager]] version 1.12 integrated a basic IWD-based wifi backend as an alternative to wpa_supplicant. To use Network Manager (NM) with the IWD backend one NM configuration change is necessary. Additionally the versions of the two software packages need to be compatible, this is because IWD's API and capabilities are evolving and the NM backend is adapting to those changes. IWD and the NM backend are work in progress and the capabilities are still limited. | [[https://wiki.gnome.org/Projects/NetworkManager|Network Manager]] version 1.12 integrated a basic IWD-based wifi backend as an alternative to wpa_supplicant. To use Network Manager (NM) with the IWD backend one NM configuration change is necessary. Additionally the versions of the two software packages need to be compatible, this is because IWD's API and capabilities are evolving and the NM backend is adapting to those changes. IWD and the NM backend are work in progress and the capabilities are still limited. | ||
| Line 13: | Line 13: | ||
| | 1.0 and later | 1.34.0 and later | Open, WPA/WPA2/WPA3 Personal and Enterprise networks, Infrastructure/AP/Ad-hoc modes, infrastructure-mode Hidden networks, no P2P, IWD-side autoconnect, network config editing from NM | | | 1.0 and later | 1.34.0 and later | Open, WPA/WPA2/WPA3 Personal and Enterprise networks, Infrastructure/AP/Ad-hoc modes, infrastructure-mode Hidden networks, no P2P, IWD-side autoconnect, network config editing from NM | | ||
| - | === Building NM === | + | ==== Building NM ==== |
| If you can use an NM build provided by the Linux distribution that will simplify things a lot. So far Arch linux is known to ship compatible [[https://wiki.archlinux.org/index.php/Iwd|iwd]] and [[https://wiki.archlinux.org/index.php/NetworkManager#Using_iwd_as_the_Wi-Fi_backend|NM]] packages so there's no need to manually build the sources. | If you can use an NM build provided by the Linux distribution that will simplify things a lot. So far Arch linux is known to ship compatible [[https://wiki.archlinux.org/index.php/Iwd|iwd]] and [[https://wiki.archlinux.org/index.php/NetworkManager#Using_iwd_as_the_Wi-Fi_backend|NM]] packages so there's no need to manually build the sources. | ||
| Line 33: | Line 33: | ||
| <code># /etc/init.d/apparmor stop</code> | <code># /etc/init.d/apparmor stop</code> | ||
| - | === NM configuration === | + | ==== NM configuration ==== |
| To switch NM from the wpa_supplicant backend to the IWD backend the following lines need to be added in ''nm.conf''. This file is normally located at ''/etc/NetworkManager/conf.d/nm.conf'' but if you've built NM from source it may be in your ''/usr/local/etc/NetworkManager/conf.d/'' instead. | To switch NM from the wpa_supplicant backend to the IWD backend the following lines need to be added in ''nm.conf''. This file is normally located at ''/etc/NetworkManager/conf.d/nm.conf'' but if you've built NM from source it may be in your ''/usr/local/etc/NetworkManager/conf.d/'' instead. | ||
| Line 63: | Line 63: | ||
| </code> | </code> | ||
| - | ==== Limitations ==== | + | ===== Limitations ===== |
| === EAP-PWD, EAP-GTC, EAP-MsCHAPv2 Identity === | === EAP-PWD, EAP-GTC, EAP-MsCHAPv2 Identity === | ||
| Line 81: | Line 81: | ||
| The NM-side profile for the 802.1X network should match the settings stored in the IWD provisioning file for given network, as closely as possible, but using the standard NM settings sytntax (''**nm-settings**(5)'', ''**nm-settings-keyfile**(5)'') -- this will allow the NM clients to ask users for the right secrets during a connection attempt, if any secrets are required. If no connection-time secrets are needed, e.g. because they're provided in the provisioning file already, then the NM profile can have any settings in it -- the profile will not be used by IWD, it only tells NM that given network is known and connectable. | The NM-side profile for the 802.1X network should match the settings stored in the IWD provisioning file for given network, as closely as possible, but using the standard NM settings sytntax (''**nm-settings**(5)'', ''**nm-settings-keyfile**(5)'') -- this will allow the NM clients to ask users for the right secrets during a connection attempt, if any secrets are required. If no connection-time secrets are needed, e.g. because they're provided in the provisioning file already, then the NM profile can have any settings in it -- the profile will not be used by IWD, it only tells NM that given network is known and connectable. | ||
| - | ==== Distribution info ==== | + | ===== Distribution info ===== |
| Debian: https://wiki.debian.org/NetworkManager/iwd | Debian: https://wiki.debian.org/NetworkManager/iwd | ||
networkmanager.txt ยท Last modified: 2022/09/23 15:21 by Andrew Zaborowski
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
