[FFe] update to the current upstream version 2.3

Bug #2012081 reported by Sebastien Bacher
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
iwd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The desktop team is considering iwd as an alternative to wpa (https://launchpad.net/bugs/1971739), while we didn't find the resources to do the transition this cycle we would still like to provide the current version in the archive as it includes several improvements which would benefit users and give us a better base to get feedback before next cycle.

Changes since the 1.30 version currently in Ubuntu

 Fix issue with length calculation for WMM IE.
 Fix issue with channel number allocation off-by-one.
 Fix issue with cached session when TLS phase2 fails.
 Add support for FastReauthentication setting for EAP-TLS.
 Fix issue with handling FT and multiple roaming scans.
 Fix issue with handling multiple wiphy registrations.
 Fix issue with with EAP-PEAP session resumption.
 Add support for using PTK rekeying in AP mode.
 Add support for setting country IE in AP mode.
 Add support for setting WMM parameter IE in AP mode.
 Fix issue with handling FT-over-DS action.
 Fix issue with handling scan and 6 GHz support check.
 Fix issue with handling when periodic scans get aborted.
 Add support for using 5 GHz frequencies in AP mode.
 Fix issue with handling P2P and limiting ciphers to CCMP.
 Fix issue with scanning before forced roaming action.
 Fix issue with provided scan frequencies from RRM.
 Fix issue with handling Michael MIC failure message.
 Fix issue with handling timestamp size in MPDU frames.
 Fix issue with handling enablement of OCVC for FT AKMs.
 Fix issue with handling FT work as highest priority.
 Fix issue with handling roaming events and Multi-BSS.
 Add support for utilizing roaming candidates list.
 Add support for utilizing TLS session caching.
 Add support for ciphers with 256 bits key size.
 Add support for Access Point mode with legacy TKIP.
 Add support for MAC address changes while powered.
 Add support for IPv4 and IPv6 network configuration.

The 2.3 version is in Debian testing and will be included in their incoming release.

The package update has been uploaded in the Ubuntu Desktop ppa for testing and correctly built on the different architectures available (the ppa doesn't have riscv enabled)
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/14558102/+listing-archive-extra

the changes can be reviews there
https://launchpadlibrarian.net/656366469/iwd_1.30-1ubuntu2_2.3-1ubuntu1~build1.diff.gz

I'm using the new version on my Lunar desktop and it's working correctly on the public and private wifi I tried.

Revision history for this message
Steve Langasek (vorlon) wrote :

How widely publicized is iwd? It's in universe but if we've been pointing lots of users to configure NM to use it (including on stable releases not just in devel), and iwd regresses for them, that's a bad bug.

It sounds like there's not going to be much validation of this as part of the update in lunar but would rely on user feedback, so there's a tension there.

Changed in iwd (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Lukas made a call for testing on discourse 2.5 years ago,
https://discourse.ubuntu.com/t/call-for-testing-improved-wifi-via-iwd

We also did change network-manager to recommends iwd over wpa during the kinetic devel cycle for a few weeks but undid that change before beta.

We haven't seen real sign of user adoption from the discourse feedback or bug reports though and the users who ended up getting iwd via discourse or being early dev cycle adopters are likely to be technical enough to uninstall iwd if needed (wpa should still be installed since we never tried to remove it from user systems since other component still make use of it directly)

The new version is in Debian testing and fedora 37/38/39 so should have got some testing (though it's not installed by default in any of those distributions so probably used by a low number of users)

The change would land before beta which give us time to get some testing and iterate if needed.

We believe that having the new features available for iwd users now in Lunar and being able to get feedback of a less outdated version if we decide to switch going forward are worth the risk if the late landing.

Changed in iwd (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in iwd (Ubuntu):
status: New → Confirmed
tags: added: upgrade-software-version
Revision history for this message
Steve Langasek (vorlon) wrote :

There is some risk here, but only for opt-in users, so +1.

Changed in iwd (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iwd - 2.3-1ubuntu1

---------------
iwd (2.3-1ubuntu1) lunar; urgency=medium

  * Resynchronize on Debian (ffe lp: #2012081), remaining changes
    + debian/iwd.conf, debian/rules:
      - provide a network-manager configuration to make iwd the default
        backend when installed
    + debian/rules:
      - build with --enable-wired to avoid functional compared to wpa
      - disable lto, it's leading to a build issue
      - install the nm config in /usr/lib instead of /etc, resolves the
        problems where the config is leftover after removing the package
    + debian/iwd.preinst:
      - remove the config from /etc on upgrade (lp: #1990891)

 -- Sebastien Bacher <email address hidden> Fri, 17 Mar 2023 11:50:18 +0100

Changed in iwd (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.