Bug 129660

Summary: NetworkManager cannot Create New Wireless Network
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Martin Vidner <mvidner>
Component: NetworkAssignee: Robert Love <rml>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /var/log/messages while attempting to create an ad-hoc network 'kaname'

Description Martin Vidner 2005-10-20 08:52:29 UTC 
I tried to 'Create New Wireless Network' with NM. Entered an essid and 
passphrase. Immediately I checked with iwconfig and it appeared OK, in Ad-Hoc 
mode. Then the applet said "Requesting a new address from the wireless network 
'(null)'..." and after a while reverted to my previous network, 'frogs'.

I do not understand where is NM trying to get the address from, when I have just 
created a new network. Is it trying DHCP? I would expect a zeroconf link local 
address.

I will recheck whether my driver (rt2500) supports Ad-Hoc, but if not, NM should 
give an error message to that sense.
BTW, can NM write a log of its actions for debugging? Or perhaps can dbus-daemon 
do that?
Comment 1 Robert Love 2005-10-27 20:45:02 UTC 
It is indeed obtaining a link-local Zeroconf address.

Please check if your driver supports AdHoc and let me know.

You can see information from the daemon by running it on the console with "--no-daemon"
Comment 2 Robert Love 2005-12-08 18:33:47 UTC 
Ping?  Is this fixed?

If not -- can you retry with the latest version (20051201 or later) and confirm if your driver supports AdHoc?  Thanks.
Comment 3 Robert Love 2005-12-09 20:20:05 UTC 
One way to confirm is

% /usr/sbin/iwconfig <interface> mode Ah-Hoc

Let me know.  Danke.
Comment 4 Martin Vidner 2005-12-13 17:51:07 UTC 
It does support Ad-Hoc. I tried with 20051212.
Comment 5 Robert Love 2005-12-13 17:58:07 UTC 
And still does not work?

Can I get the output of the NetworkManager log during the problem?  It should be in your syslog (/var/log/messages).  Otherwise, you can grab the log directly:

% /etc/init.d/networkmanager stop
% NetworkManager --no-daemon >cheese.log

and attach the log.

Thank you!
Comment 6 Martin Vidner 2005-12-13 20:40:58 UTC 
Created attachment 60460 [details]
/var/log/messages while attempting to create an ad-hoc network 'kaname'

It did not work. The applet was showing (null) as the network name before it reverted to frogs.
Comment 7 Robert Love 2005-12-13 20:55:01 UTC 
Thank you!

Just to be clear: You tried to create "kaname" and "frogs" was an existing network?

It looks as if NM successfully creates "kaname" but for some reason decides to fall back to "frogs" ... Hmm.
Comment 8 Martin Vidner 2005-12-13 21:52:08 UTC 
Right.
Comment 9 Robert Love 2006-01-12 17:57:31 UTC 
With luck, this is fixed in 0.5.1cvs20060112.  Can you reproduce and check?
Comment 10 Robert Love 2006-02-06 16:16:35 UTC 
Closing.  Ought to be fixed.