Bug 8942 - Wireless SSID parse error and failed connection
Summary: Wireless SSID parse error and failed connection
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: Mageia 3
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-02 04:03 CET by Tony Blackwell
Modified: 2013-05-21 03:48 CEST (History)
3 users (show)

See Also:
Source RPM: drakx-net
CVE:
Status comment:


Attachments
attach1 (87.54 KB, image/png)
2013-02-02 04:23 CET, Tony Blackwell
Details
MCC with router wifi SSID invisible (87.54 KB, image/png)
2013-02-03 03:00 CET, Tony Blackwell
Details
MCC with router wifi SSID visible (83.73 KB, image/png)
2013-02-03 03:02 CET, Tony Blackwell
Details
DrakConf selected ath5k (63.95 KB, image/jpeg)
2013-02-03 03:03 CET, Tony Blackwell
Details
Drakconf sees visible SSID correctly (67.62 KB, image/jpeg)
2013-02-03 03:04 CET, Tony Blackwell
Details
routine wifi config (81.05 KB, image/jpeg)
2013-02-03 03:05 CET, Tony Blackwell
Details
Drakconf 'connect now' failure, why still sees \x00\x00\x00 ? (61.07 KB, image/jpeg)
2013-02-03 03:06 CET, Tony Blackwell
Details

Description Tony Blackwell 2013-02-02 04:03:06 CET
HW: acer extensa 5620Z laptop, ath5k
Background:  Initially M3B2 failed to show any wifi stations via MCC.  Running the sequence of rmmod ath5k, rfkill unblock all, modprobe ath5k leads to MCC seeing the wifi stations.  This has been bug-reported by others.

Problem: After the above fixes, still can't connect.  In some circumstances, the SSID of the wifi seems to be incorrectly handled.

When the SSID on the router is set 'not visible', it is seen by MCC as SSID name of '\x00\x00\x00\x00\x00' repeated many times.  See attachment1 [details]

When the router SSID is set visible, MCC correctly sees the name, in this case 'CocoPrivateRouter'.  See attachment 2 [details].  Adding password and attempting connect fails.

I then closed MCC, logged out of graphical session, went to text login and ran DrakConf in text mode.  Going through the wireless config here resulted in a parse error of SSID name still being seen as '\x00\x00\x00\x00 etc.  In failing, it complained of 'len=68, max_len=32'  which is clearly an error.

Why, when the SSID name seems to be correctly seen, does it appear (using drakconf to get more error feedback) that the SSID name is still seen as that erroneous \x00\x00 string?


One further problem which should perhaps be split of as a separate bug.  In the course of working this out, I think there is no way in MCC to set up the logon for a wifi router which does not disclose its SSID name. The user can edit properties of a router which is visible, but not edit the SSID name and I think not set up login from a totally new blank set of fields.  I got around this in M1 by temporarily making the SSID visible, after configuration it then works fine with the SSID changed back to invisible.  Having write access to admin in the router is often not an option however.  Need a fix for this in MCC.

I'll log this first then add attachments
Comment 1 Tony Blackwell 2013-02-02 04:23:41 CET
Created attachment 3476 [details]
attach1
Jani Välimaa 2013-02-02 13:41:44 CET

CC: (none) => jani.valimaa

claire robinson 2013-02-02 15:32:51 CET

CC: (none) => eeeemail

Comment 2 Tony Blackwell 2013-02-03 03:00:46 CET
Created attachment 3479 [details]
MCC with router wifi SSID invisible

Attachment 3476 is obsolete: 0 => 1

Comment 3 Tony Blackwell 2013-02-03 03:02:02 CET
Created attachment 3480 [details]
MCC with router wifi SSID visible
Comment 4 Tony Blackwell 2013-02-03 03:03:30 CET
Created attachment 3481 [details]
DrakConf selected ath5k
Comment 5 Tony Blackwell 2013-02-03 03:04:23 CET
Created attachment 3482 [details]
Drakconf sees visible SSID correctly
Comment 6 Tony Blackwell 2013-02-03 03:05:15 CET
Created attachment 3483 [details]
routine wifi config
Comment 7 Tony Blackwell 2013-02-03 03:06:33 CET
Created attachment 3484 [details]
Drakconf 'connect now' failure, why still sees \x00\x00\x00 ?
Tony Blackwell 2013-02-03 03:07:27 CET

Attachment 3484 description: Crakconf 'connect now' failure, why still sees \x00\x00\x00 ? => Drakconf 'connect now' failure, why still sees \x00\x00\x00 ?

Manuel Hiebel 2013-02-03 13:20:11 CET

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

Comment 8 Marja Van Waes 2013-02-15 13:20:02 CET
I have the \x00\x00 issue, too (but I don't see it repeated as many times as Tony).

However, our SSID can remain hidden and it is still possible to setup WLAN.

I can only do that by Choosing "Set up a new network interface" in MCC, or by starting drakconnect in a console.

In the "Wireless
Please Select you network" screen
I have to choose "Unlisted - edit manually"
because if I choose \x00\x00 I can't set the correct SSID.

After filling out all needed fields the WLAN adapter works fine.

(Sometimes, it won't work after setting it, but then it works on reboot)

Also sometimes, WLAN works but netapplet thinks it is connected to \x00\x00

CC: (none) => marja11

Comment 9 Tony Blackwell 2013-03-13 20:19:53 CET
Still not successfully connecting, as at M3B3 released version
Comment 10 Tony Blackwell 2013-05-21 03:48:12 CEST
Seems more or less OK with M3.  There are still some issues; at first login after install, from xfce, as a general user but via MCC with root pwd, I can't establish wireless at all - all connections fail.  At reboot it is connected just fine.  Can't explain this.

Best to close this bug, as the system will connect after reboot.

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


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