After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603959 - NetworkManager keeps controlling an interface inspite of NM_MANAGED=no
NetworkManager keeps controlling an interface inspite of NM_MANAGED=no
Status: RESOLVED NOTABUG
Product: NetworkManager
Classification: Platform
Component: general
0.7.x
Other Linux
: Normal minor
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2009-12-07 10:13 UTC by kynde
Modified: 2009-12-07 20:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kynde 2009-12-07 10:13:44 UTC
Description of problem:
NetworkManager keeps controlling an interface no matter what.

Version-Release number of selected component:
0.7.996-6.git20091021.fc12.x86_64

How reproducible:
Very, occurs every time.

Steps to Reproduce:
1. Mark eth0 with NM_MANAGED=no (by un-checking from system-config-network)
2. ifconfig eth0 10.11.12.13
3. plug line in and plug out

Actual results:
NetworkManager: <info> (eth0): ...
NetworkManager: <info> (eth0): deactivating device (reason: 40)
NetworkManager: <info> (eth0): ...

Expected results:
none of that. I expect it to not touch eth0 if I mark it unmanaged.

Additional info:
Works only if I kill it.
Comment 1 Dan Williams 2009-12-07 19:06:43 UTC
Need some /var/log/messages; but since you've filed this both on redhat bugzilla and here on gnome bugzilla, where do you want to track it?  I'd suggest we track this in Red Hat bugzilla since it's a fedora-specific issue.
Comment 2 kynde 2009-12-07 20:06:16 UTC
Ack. Added some information there. Sorry about the dupe, but since I was unsure where it belonged to I figured I'd add file it here, too. I guess we can close this one?
Comment 3 Dan Williams 2009-12-07 20:50:15 UTC
Yeah, we can close this one.  I've followed up on the RH one based on the information you've provided and you need a valid HWADDR in that ifcfg file tying the ifcfg file to a specific device.