Bug 1413297
| Summary: | Wi-Fi connections created in Fedora <= 24 get "Cloned MAC address: permanent" in nm-connection-editor, blocking save | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matt McCutchen <matt> | ||||
| Component: | network-manager-applet | Assignee: | Lubomir Rintel <lkundrak> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | alick9188, bgalvani, blueowl, dcbw, lkundrak, thaller | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-09-15 03:50:49 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: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Matt McCutchen
2017-01-14 16:44:10 UTC
thanks for the analysis. It is wrong that keyfile reader sets mac-address-randomization in absence of the field. That is fixed upstream: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e11012c047e09d04f663c1c36e6c47dc298 nm-1-4: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2a960d3936d78087d74ba556df8ac808639c96a0 This causes old keyfiles (that pre-date mac-address-randomization property) to be interpreted as wifi.mac-address-randomization=1 wifi.cloned-mac-address=permanent as they don't specify one of the settings explicitly. It's not too bad, because adding a new property obviously needs that we choose some value in those old connections. "permanent" is not too bad as a default value, because that is also what old versions of NetworkManager did implicitly. So, on upgrade, NetworkManager still behaves the same. Better would be of course to leave the value unspecified. Because: - we changed the default value to no longer mean "permanent" but "preserve". So, leaving the value unspecified, allows for the desired(?) change in behavior (https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=fae5ecec5a4d9987a1915441602cb78275a9f490) - it allows the default value to be overwritten by global connection defaults (https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8eed67122c58540360b617eb42d5df8328e21b5d) Another problem is that nm-connection-editor doesn't know how to handle the special values like cloned-mac-address=permanent. It's not too bad however, because the user can delete the word "permanent" and use nm-c-e to edit the connection. Of course, he is unable to save those unsupported values, but for that he can use nmcli or nmtui. (this is TODO) (In reply to Thomas Haller from comment #1) > - we changed the default value to no longer mean "permanent" but > "preserve". So, leaving the value unspecified, allows for the desired(?) > change in behavior > (https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=fae5ecec5a4d9987a1915441602cb78275a9f490) (btw, the change of the final fallback for the default value of cloned-mac-adress from "permanent" to "preserve" will be part of 1.6.0. It will not reach Fedora 25 (but Fedora 26+). So is the idea that https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2a960d3936d78087d74ba556df8ac808639c96a0 will be released to Fedora 25 and this bug will go away as a consequence? NetworkManager-1.4.4-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b8bd593c7 (In reply to Matt McCutchen from comment #3) > So is the idea that > https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=2a960d3936d78087d74ba556df8ac808639c96a0 will be released to Fedora 25 > and this bug will go away as a consequence? Correct. Please try NetworkManager-1.4.4-3.fc25. Thanks. Verified that NetworkManager-1.4.4-3.fc25 fixes this bug for me. NetworkManager-1.4.4-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b8bd593c7 (In reply to Thomas Haller from comment #1) > Another problem is that nm-connection-editor doesn't know how to handle the > special values like cloned-mac-address=permanent. > (this is TODO) Fixed upstream with commit: https://git.gnome.org/browse/network-manager-applet/commit/?id=85b6b659a140a59c3df787062e089a0b4e2a547d NetworkManager-1.4.4-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. I am bitten by the same bug. I don't think it is fully fixed. Now I know I can delete the text "permanent" in "Cloned MAC" field to make changes able to "Save". However, every time I save the changes (with an empty Cloned MAC), "MACADDR=permanent" still gets written to the ifcfg-SSID file, and next time I want to edit the connection, I need to delete "permanent" again... This is quite annoying. Besides, it is confusing to not able to "Save" in the GUI because of this automatic generated entry. Finally, why is the bug still ON_QA after so many months? (In reply to Alick Zhao from comment #10) > I am bitten by the same bug. I don't think it is fully fixed. you don't say which version of NetworkManager/nm-connection-editor you are using. On Fedora25, the patch https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=7f63c875f973f3b7cc136130c61348b36e280ab6 is not present. That could cause what you describe. Probably the workaround is to reset wifi.mac-address-randomization: https://mail.gnome.org/archives/networkmanager-list/2017-January/msg00061.html (In reply to Thomas Haller from comment #11) > (In reply to Alick Zhao from comment #10) > > I am bitten by the same bug. I don't think it is fully fixed. > > you don't say which version of NetworkManager/nm-connection-editor you are > using. Sorry I forgot to mention, but this is a fully updated Fedora 25 laptop: NetworkManager-1.4.4-5.fc25 network-manager-applet-1.4.0-1.fc25 (contains nm-connection-editor) > > On Fedora25, the patch > https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=7f63c875f973f3b7cc136130c61348b36e280ab6 is not present. That could > cause what you describe. > I think so. Would be good to make it a patch for fc25. > Probably the workaround is to reset wifi.mac-address-randomization: > https://mail.gnome.org/archives/networkmanager-list/2017-January/msg00061. > html I agree, and will test when I have access to the laptop. NetworkManager-1.4.6-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-a2f2ef5a3c please try NetworkManager-1.4.6-1.fc25 NetworkManager-1.4.6-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-a2f2ef5a3c (In reply to Thomas Haller from comment #14) > please try NetworkManager-1.4.6-1.fc25 Seems fixed with this version. Thanks! NetworkManager-1.4.6-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. |