| Summary: | NetworkManager must not enable wireless devices after restart | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Slebodnik <lslebodn> |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | bgalvani, dcbw, lkundrak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-26 17:47:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Any news after 9 months? This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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. NetworkManager maintains a persistent state that includes the desired radio state, and enforces this state each time it's started. Therefore, if you are using NetworkManager and want to keep wifi disabled, 'nmcli radio wifi off' should be used. (In reply to Beniamino Galvani from comment #3) > NetworkManager maintains a persistent state that includes the desired > radio state, and enforces this state each time it's started. > > Therefore, if you are using NetworkManager and want to keep wifi > disabled, 'nmcli radio wifi off' should be used. It is something different what I would like to achieve. "rfkill block" and "rfkill unblock" are equivalent to enabling/disabling wifi on laptop using fn+f8 (or other combination of keys) If I disable wifi with keybord then I would like to have this state even after restarting NetworkManager. After calling "nmcli radio wifi off" it is not possible to use wifi anymore with NM. sh# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no sh# nmcli radio wifi off sh# rfkill list 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no sh# rfkill unblock 0 sh# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no sh# nmcli radio wifi disabled sh# nmcli connection show --active NAME UUID TYPE DEVICE docker0 0ae125a0-160d-49ad-9815-768bf1b9866a bridge docker0 enp0s25 74d46029-a6c5-4c6e-a922-d09d7e34e9ab 802-3-ethernet enp0s25 sh# nmcli connection up "MY Guest" Error: Connection activation failed: No suitable device found for this connection. sh# nmcli radio wifi on sh# nmcli connection up "MY Guest" Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/10) sh# nmcli connection show --active NAME UUID TYPE DEVICE MY Guest d08d434c-2700-44ac-a2df-c9c1ef76b90c 802-11-wireless wlp3s0 docker0 0ae125a0-160d-49ad-9815-768bf1b9866a bridge docker0 enp0s25 74d46029-a6c5-4c6e-a922-d09d7e34e9ab 802-3-ethernet enp0s25 This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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. Reproducible on f29 This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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. This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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. Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: I do not have a hardware switch for disabling wireless devices on my laptop. I have to use "soft blocking" with keyboard or with rfkill. There isn't any light which could display state of wireless device. However the state is not preserved after restarting NM. Version-Release number of selected component (if applicable): NetworkManager-1.2.0-0.6.beta2.fc24.x86_64 How reproducible: Deterministic Steps to Reproduce: A. [root@host ~]# rfkill list 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no B. [root@graviton ~]# systemctl restart NetworkManager Actual results: [root@graviton ~]# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Expected results: [root@host ~]# rfkill list 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no