Bugzilla – Bug 12260
Non-alphanumeric SSID not displayed correctly, does not connect
Last modified: 2009-09-08 09:15:19 UTC
Any SSID broad cast with non-ascii chararcters does not show up. Examples: #Pound @mYp0und =^..^= Poûnd
Felix: Where does this stand?
Felix, where does this stand?
Those are ascii characters, it's non alphanumeric characters that aren't working.
James: can you confirm that this is not related to the encryption type or WPS flag on the SSID?
Tested WPS and NON-WPS routers, with & w/o encryption. It's the 'funny name' that just doesn't show up in the scan
It seems that even a dash "-" in the SSID name will prevent the AP from showing up in the network list on Baby.
It also seems that entering the ssid manually, even if the characters are available to enter, does not get around this issue. For example I am able to enter my ssid, ss-wrt54gs, but Baby still does not connect.
Well, after a factory reset with r6277 I am now able to see some networks with dashes in their names so this seems to be intermittent. Perhaps this has more to do with the number of ssids visible in Mountain View?
I tried with the first 3 listed SSIDs above and Baby was able to see and connect to the AP just fine. The fourth example: Poûnd doesn't work as wpa_supplicant converts that to Po_nd and then fails to connect. # wpa_cli scan_r Selected interface 'eth1' bssid / frequency / signal level / flags / ssid 00:1e:2a:55:f4:32 2412 216 [WPA2-PSK-CCMP][WPS] No Support 00:18:4d:85:e0:44 2462 212 [WPA2-PSK-CCMP-preauth] No Device 00:21:29:c7:7a:6a 2427 206 [WPA2-PSK-CCMP][WPS] WRT54G2 00:22:3f:13:cd:f8 2437 206 [WPA2-PSK-CCMP][WPS] WGR614L 00:21:91:33:f6:8f 2417 203 [WPA2-PSK-CCMP][WPS] DIR-300 00:11:6b:2a:27:06 2447 199 [WPS] Po_nd I had a total of 6 APs running at the time. AP used: Level One WBR-6001 Baby rev.: r6277
This bug has been identified as one that may not be required for MPQ since it now seems clear that MPQ and MP firmwares will be different. Please comment if you disagree with this assessment. Thanks!
r6430 does address this issue. Should we close it as fixed or wait for newer drivers? Deferring bug to MP till a decision is made.
Poûnd still shows as Po_nd with r6430
(In reply to comment #12) > Poûnd still shows as Po_nd with r6430 Also note, that when this happens, I am unable to connect to the AP
Connecting issue with special char SSIDs fixed in r6735 (Baby) and r6743 (Fab4). Special chars in SSID will show as '?' in the GUI. Some background: An SSID consists of simple 8 bit ASCII chars (not UTF-8) and the upper half of the ASCII table can be many things - it could be pseudo graphical chars or umlauts or ... Simple from an SSID it's not possible to determine what the user has entered on it's AP. For instance a 'û' is reported back from the wireless driver as '{', on a Mac it shows as small circle, etc.