Bug 1050546
| Summary: | NetworkManager no longer sets different metrics for ethernet and wireless | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ferry Huberts <mailings> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | bryan.sutherland, cpanceac, cra, dcbw, dylan.swift, gholms, jconroy, psimerda, samuel-rhbugs |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-29 14:16:55 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: | |||
|
Description
Ferry Huberts
2014-01-08 23:24:15 UTC
This worked fine in F19, after I filed a bug for it and it got fixed. ping? this is a (serious) regression... (In reply to Ferry Huberts from comment #2) > this is a (serious) regression... If this is indeed a regression, could you please tell us which version of the package was the last that works for you? Guys, When am I getting a fix for this _regression_? (In reply to Pavel Šimerda (pavlix) from comment #3) > (In reply to Ferry Huberts from comment #2) > > this is a (serious) regression... > > If this is indeed a regression, could you please tell us which version of > the package was the last that works for you? I did an upgrade from F19 to F20. In F20 it didn't work anymore. Don't know the exact F19 version is use. I've been running the RHEL 7 Beta for a bit and have run into the same issue with NetworkManager-0.9.9.0-25.git20131108. Based on the comments above, I rolled back to the NetworkManager-0.9.8.8-2.fc19 build and things are now working as expected. Some other notes about the change: Before the rollback, NM was assigning a metric of 0 to both the wired and wireless interfaces. After the rollback, the wireless interface received a metric of "9" while the wired interface was assigned a metric of "1". Rolling back NetworkManager also required rolling back nm-connection-editor and libnm-gtk, both from the network-manager-applet-0.9.8.4-1.git20131028.fc19 build. I run VMware Workstation and while using the supplied 0.9.9.0 package the network applet would show the vmnet virtual networking devices (also with the icon indicating that a wired connection had been made based on the virtual interfaces being available and assigned IPs). Rolling back NM fixed this as well...these devices are now hidden from the applet and network configuration utility, just as they had been in older GNOME releases. While I rebuilt these F19 SRPMs under mock for EL7, I originally tested them by directly installing the F19 builds from Fedora's Koji instance without an issue. Is this a recurrence of bug #970293 ? *** Bug 1051178 has been marked as a duplicate of this bug. *** (In reply to Charles R. Anderson from comment #7) > Is this a recurrence of bug #970293 ? no ping Any updates on this bug? Thx guys come on, 6 months and counting... (In reply to Ferry Huberts from comment #11) > guys come on, 6 months and counting... for a _regression_ (In reply to Ferry Huberts from comment #12) > (In reply to Ferry Huberts from comment #11) > > guys come on, 6 months and counting... > > for a _regression_ See https://bugzilla.gnome.org/show_bug.cgi?id=723178#c18 This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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. I don't know about metric of a connection that has no ip so here's what i know (and what i've originally reported): -i start fedora 22 -i connect ethernet cable ==> the used network connection is still the wireleess one. It's the same if i start with the ethernet cable connected. so for me the problem is still there. So please reassign to Fedora 22. this seems to be fixed in f22 Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |