Bug 1501664
| Summary: | nm-connection-editor keeps resetting IPV6_ADDR_GEN_MODE to stable-privacy | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> | ||||
| Component: | network-manager-applet | Assignee: | Lubomir Rintel <lkundrak> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 26 | CC: | bgalvani, blueowl, cra, dcbw, fgiudici, 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: | 2018-05-29 11:58:17 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
Charles R. Anderson
2017-10-13 03:28:40 UTC
did you reload the connection profile after editing the ifcfg-file? either via - nmcli connection load /etc/sysconfig/network-scripts/ifcfg-br0 - nmcli connection reload - systemctl restart NetworkManager - reboot (the last two are the big hammer. Usually, you wouldn't restart NM in order to reload a connection). As mentioned, after manual ifcfg-* file update, you need to reload the connection $ nmcli connection load /etc/sysconfig/network-scripts/ifcfg-br0 NetworkManager doesn't monitor the files (by default). This can be changed with monitor-connection-files setting in the configuration file (though it is discouraged). See man NetworkManager.conf The property can also be changed via nmcli this way: $ nmcli con modify br0 ipv6.addr-gen-mode eui64 Created attachment 1346736 [details]
[PATCH] editor: allow setting IPv6 address generation mode (rh #1501664)
I agree that nm-connection-editor should allow editing addr-gen-mode property.
This patch implements that. (It is published in upstream branch jk/rh1501664-edit-addr-gen-mode too.)
Note that the original bug report is probably not correct. At least, I cannot reproduce the issue. nm-connection-editor may not support addr-gen-mode (yet), but saving a connection in nm-connection-editor leaves the addr-gen-mode unchanged. The reporter may not have reloaded the connection, which is a user-error. Anyway, it's useful to expose this feature. (In reply to Blueowl from comment #3) > Created attachment 1346736 [details] > [PATCH] editor: allow setting IPv6 address generation mode (rh #1501664) Pushed minor fixup commits to jk/rh1501664-edit-addr-gen-mode Rest lgtm. Patch and fixup commits LGTM. (In reply to Beniamino Galvani from comment #5) > Patch and fixup commits LGTM. merged to master: https://git.gnome.org/browse/network-manager-applet/commit/?id=6a0a3dd51202116e1e72f7874f1472a906b2bcb5 (including the fixup commits) Thanks Jirka! 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. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. |