Bug 450116
Summary: | [Enhancement Request] NetworkManager should not report the user is offline, unless the user really is offline | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill C. Riemers <briemers> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | dcbw, wtogami |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-03 02:01:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bill C. Riemers
2008-06-05 13:39:41 UTC
NM will report that the user is offline if NM does not control the user's primary network device. If you have told NM to ignore the primary network device by marking it as NM_CONTROLLED=no (either through system-config-network or by adding that option to the ifcfg file) then NetworkManager cannot determine the state of that device, precisely because you've told NM to ignore that device. Either let NM control the primary device, or turn NM off with chkconfig. NM should be able to run without controlling all devices. I consider this a bug, because NM is reporting false information. But if it makes you feel better, consider it an enhancement request. If you wish I can submit a patch. If there's a connection metohd that NetworkManager does not support, we add support to NetworkManager to control that connection method. We don't hack around it by adding _partial_ support for noticing that some interface is up and maybe grabbing the IP address or routes off that interface when we can't even control it. It needs to get done the _right_ way, not in a compatibility hack. If NetworkManager is not able to control the primary network interface of the machine, then NM should not be enabled on that machine. |