Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => mageia
Source RPM: net-applet => drakx-net

I can't reproduce, if I configure a wireless interface with NEEDHOSTNAME=yes and connect to it with net_applet, NEEDHOSTNAME is not changed.

Is it still valid?

CC: (none) => thierry.vignaud

No, sorry, I had lost track of this.  This no longer occurs.

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

I'm afraid this is still happening,or has started happening again. I suspect it now has to do with Network Manager running,even if the interface has NM_CONTROLLED=no.

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

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Some more information...

I suspect this happens when the access point changes.  It's happened again to me when I have set NEEDHOSTNAME on my home access point to YES, take the laptop toanother location, connect to a different access point, then bring the laptop back home again and connect to my original access point.  At that point,I'm back to NEEDHOSTNAME=NO.  Roaming is not enabled.

It appears that net-applet is either not saving recent access point profiles, or is not honoring their NEEDHOSTNAME when it rebuilds the ifcfg the next time they are activated.

This is not related to NetworkManager, which is not running.  

I can reproduce this easily by

1) running drakconnect to configure wlan0 with NEEDHOSTNAME=YES and selecting YES for "start interface now".  wlan0 comes up, and the ifcfg-wlan0 shows NEEDHOSTNAME=YES after drakconnect ends

2) opening draknetcenter, disconnecting the interface, and re-connecting.to the same interface.  The ifcfg-wlan0 now shows NEEDHOSTNAME=NO.

So, while changing the access point will cause the problem, so will disconnecting and reconnecting to the same access point with draknetcenter.  It appears that the ifcfg is being rebuilt at every connect.

I also notice that sometimes draknetcenter can re-connect to the access point, and sometimes it can't; if it fails, it will fail consistently, but then running drakconnect *or* rebooting connects just fine.  That's not part of this bug report, but it indicates that draknetcenter is not using the same code to bring up an interface as drakconnect or the boot sequence, which may be pertinent here.

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.

(In reply to comment #9)

n/a here

@ Frank

Is this bug still valid?

Please close if it isn't

Thanks :-)

CC: (none) => marja11
Whiteboard: MGA2TOO => NEEDINFO

Closing as OLD.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD