Bug 7249 - networkmanager is rewriting wireless ifcfg with NEEDHOSTNAME=NO
Summary: networkmanager is rewriting wireless ifcfg with NEEDHOSTNAME=NO
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 7557
  Show dependency treegraph
 
Reported: 2012-08-29 23:54 CEST by Frank Griffin
Modified: 2012-10-29 15:01 CET (History)
0 users

See Also:
Source RPM: networkmanager
CVE:
Status comment:


Attachments

Description Frank Griffin 2012-08-29 23:54:04 CEST
Fresh cauldron install, NM installed and active, wired eth0 interface and wireless wlan0 interface defined, both with NEEDHOSTNAME=YES.  Neither one controlled by NM.

Reboot with NM enabled.  Wired ifcfg still has NEEDHOSTNAME=YES, wired ifcfg has been changed to NEEDHOSTNAME=NO.  Change it back, and net-applet can't activate wlan0.

Disable NM, reste wlan0 to NEEDHOSTNAME=YES, reboot, and all is well.
Manuel Hiebel 2012-09-23 21:20:34 CEST

Blocks: (none) => 7557

Comment 1 Frank Griffin 2012-10-29 13:24:12 CET
Please refer to the discussion in bug#7873 and bug#2160 and see if your problems with NM go away if you either allow GNOME (if you have it installed) to activate it or you install plasma-network-management under KDE, add it to your panel, and use it to configure your SSID.

For NM to handle wireless correctly, it needs to create SSID-specific files of its own by parsing the ifcfg files produced by drakconnect.  GNOME's nm-applet does this automatically, since it has no option to *not* use NM, but since NM isn't the default yet for other desktops, it doesn't happen automatically there.  

You'll need to install NM and let it start, and recreate your wireless interface with drakconnect specifying "Allow NM to control this interface".

Please test and post your results, as whether NM works for all the chips involved when it's properly configured will have a significant impact on how it needs to be handled for non-GNOME desktops in MGA3.
Comment 2 Frank Griffin 2012-10-29 15:01:34 CET
@ comment#1 :

My wireless now works with NM, so closing this as it's covered by bug#865

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.