Bug 2915 – rogue high ascii characters randomly show up while entering a long SSID manually

Bug 2915 - rogue high ascii characters randomly show up while entering a long SSID manually

Summary:

rogue high ascii characters randomly show up while entering a long SSID manually

Status:	CLOSED FIXED

Product:	SB 2/3
Classification:	Unclassified
Component:	Setup
Version:	29
Platform:	All Other

Importance:	P3 minor (vote)
Target Milestone:	---
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-02-01 13:43 UTC by Kevin Pearsall
Modified:	2008-12-18 11:38 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Kevin Pearsall 2006-02-01 13:43:30 UTC

Comment 1 Kevin Pearsall 2006-02-01 13:49:51 UTC

re-prioritizing...  can't seem to reproduce without:
- graphite airport in range
- graphite airport set to 'create a closed network'

Comment 2 Blackketter Dean 2006-02-01 13:55:44 UTC

Subject: Re:  rogue high ascii characters randomly show up while entering a long SSID manually

Please add details about what keys you pressed, etc....

Comment 3 Kevin Pearsall 2006-02-01 14:15:52 UTC

- graphite airport must be in range
- graphite airport must be set to 'create a closed network'
- graphite airport was set to 40 bit wep
- graphite airport's ssid was set to 'GRAPHITE PIECE OF SHIT' (with spaces)
- rogue characters showed up while entering the SSID manually
- one other odd thing, when the airport was set up this way, the first network it found was just a space (i.e. choose your network name (SSID) had a blank-looking entry that was actually " ")
- joe used number buttons on the remote to enter ssid manually, add button on remote to add the spaces

Comment 4 Blackketter Dean 2006-04-21 21:10:47 UTC

I suspect that this was fixed in the recent firmware changes.  Chris, can you try to reproduce?

Comment 5 Chris Owens 2006-04-25 09:16:20 UTC

Richard fixed this during the great networking overhaul of fw35-fw47

Comment 6 Chris Owens 2006-04-25 09:17:15 UTC

And I verified the fix.  Amusingly, the Graphite AP was still set up as Kevin described in the bug from February.  I guess it doesn't get a lot of use.

Comment 7 Chris Owens 2006-06-27 14:22:05 UTC

This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.