Package Details: networkmanager-iwd 1.52.0-1

Git Clone URL: https://aur.archlinux.org/networkmanager-iwd.git (read-only, click to copy)
Package Base: networkmanager-iwd
Description: Network connection manager and user applications; using iwd backend instead of wpa_supplicant
Upstream URL: https://networkmanager.dev/
Licenses: GPL-2.0-or-later, LGPL-2.1-or-later
Conflicts: networkmanager
Provides: networkmanager
Submitter: digitalone
Maintainer: buzo
Last Packager: buzo
Votes: 34
Popularity: 0.84
First Submitted: 2019-08-10 10:04 (UTC)
Last Updated: 2025-03-05 19:10 (UTC)

Required by (288)

Sources (2)

Pinned Comments

digitalone commented on 2019-08-10 10:37 (UTC) (edited on 2019-08-15 09:14 (UTC) by digitalone)

This is a modified package configured to get NetworkManager working exclusively with iwd. Main difference with upstream version is that iwd is required and wpa_supplicant is not needed (so you can uninstall it); iwd seems more reliable on certain wireless cards, so someone could prefer it in place of wpa_supplicant.

It's recommended to enable systemd iwd.service at boot: systemctl enable iwd.service

Tested with Plasma NM system tray applet (plasma-nm), it's working.

Note that wpa_supplicant is still needed to build the package, but you can uninstall it after the building stage.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

buzo commented on 2021-07-15 16:36 (UTC)

maksverver: Thanks for the detailed clarification.

maksverver commented on 2021-06-22 13:01 (UTC)

The mainline networkmanager package switched to provides=(libnm.so) and its dependants have been updated too, so it makes sense for networkmanager-iwd to do the same.

Using the name of the provided library (rather than the name of a compatible package) seems compatible with the packaging guidelines described here: https://wiki.archlinux.org/title/PKGBUILD#provides

There is no rationale provided there, but I suspect the goal is to decouple library dependencies from package dependencies:

  1. Packages that work with any implementation of libnm.so but don't care about which package provides it should depend only libnm.so (the library can be provided by either libnm or libnm-iwd).
  2. Packages that need a particular implementation can depend on the package that provides it (e.g networkmanager-iwd must depend on libnm-iwd, because it won't work with mainline libnm).

The conclusion is that if your system is up-to-date, the official packages should already work, and for any custom PKGBUILDs or AUR packages, you should update the dependency on libnm to either libnm.so (if mainline will work) or libnm-iwd (if required).

Gadgethm commented on 2021-06-22 05:27 (UTC) (edited on 2021-06-22 05:30 (UTC) by Gadgethm)

If you change all instances of 'provides=(libnm.so)' and 'provides = libnm.so' to 'provides=(libnm)' and 'provides = libnm' respectively in both the PKGBUILD and the .SRCINFO files, then it will properly build and install, or at least that worked for me. Will report back more if I run into problems.

Not sure why the changes in 48622efab81d got backed out... Any ideas?

frebib commented on 2021-06-21 10:06 (UTC) (edited on 2021-06-21 10:07 (UTC) by frebib)

buzo: Echoing what cubethethird said, libnm-iwd dependencies are broken again. This happened before and you fixed it in 48622efab81d. Why does this keep happening? Thanks

cubethethird commented on 2021-06-19 02:39 (UTC) (edited on 2021-06-19 02:40 (UTC) by cubethethird)

I can no longer install libnm-iwd as it no longer provides libnm, but instead only libnm.so, and it complains that this breaks dependencies for other packages. Is there a particular reason for this change?

buzo commented on 2021-05-13 09:06 (UTC)

maksverver: Fixed, thanks. (Please click on “Flag package out-of-date” next time.)

maksverver commented on 2021-05-12 18:40 (UTC)

I had to bump ppp_version to 2.4.9 to install this, which is the current version of ppp in the core repo. Maybe a pkgrel update is in order?

Gadgethm commented on 2021-02-01 23:30 (UTC)

I also see the same issue as cubethethird, hopefully will be fixed in the next update.

cubethethird commented on 2021-01-17 20:57 (UTC)

It's looking like there's an issue with the package version (possibly 1 too many characters in the hash). When running the pkgver function, the version gets updated to 1.28.1dev+7+g3f5df3cdc-1, which is considered to be older than the stated version in the PKGBUID of 1.28.1dev+7+g3f5df3cdc6-2. As a result, each time I build and update, I am still informed that the upstream is newer than the current.

buzo commented on 2021-01-04 12:54 (UTC)

Thanks, frebib – fixed.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »