Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1861919 - NetworkManager does not automatically reconnect when using iwd as wifi backend.
Summary: NetworkManager does not automatically reconnect when using iwd as wifi backend.
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 32
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
Reported: 2020-07-29 21:42 UTC by Jóhann B. Guðmundsson
Modified: 2021-05-25 16:36 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-25 16:36:10 UTC
Type: Bug

Attachments (Terms of Use)

Description Jóhann B. Guðmundsson 2020-07-29 21:42:21 UTC
Description of problem:
When using iwd as a wifi backend NetworkManager does not automatically re-connect to the available wifi once it has lost connection to it. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

dnf install iwd

create the file /etc/NetworkManager/conf.d/iwd.conf which contains 

systemctl disable --now wpa_supplicant
systemctl enable --now iwd
systemctl restart NetworkManager

Create a hotspot on your mobile phone. 
Connect using iwd as the wifi backend.
Disable the hotspot on your mobile phone
Enable the hotspot on your mobile phone

Actual results:
NetworkManager does not automatically re-connect to the hotspot

Expected results:
Same behaviour as it does with wpa_supplicant as the wifi backend.

Additional info:
Something we need to fix before switching to iwd as the wifi backend.

Comment 1 Martin Pitt 2021-02-01 10:40:43 UTC
I recently reported bug 1915641 against iwd -- that may be a special case of this more general bug?

Comment 2 Fedora Program Management 2021-04-29 16:34:44 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2021-05-25 16:36:10 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.