Bug 6430 - Jive linksys wireless issue
: Jive linksys wireless issue
Status: NEW
Product: SB Controller
Classification: Unclassified
Component: Development package
: unspecified
: Other Other
: -- normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-20 07:34 UTC by Stein David
Modified: 2011-01-13 23:59 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stein David 2007-12-20 07:34:28 UTC
There is a wireless issue on the assembly floor.  Jive is unable to correctly recognize a Linksys Router from 2 feet away.

I'll describe the symptoms in order of appearance:

(1)   The first Jive failed the wifi test 6 out of 8 times.  The Jive wifi test is performed with "iwlist scan eth0" and searching for an ESSID of "JiveTestMachine".  I checked what Jive was reporting and saw the following:

#
#  iwlist eth0 scan
eth0      Scan completed :
Cell 01 - Address: 00:15:E9:84:38:E9
ESSID:"D-Link"
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100  Signal level=-77 dBm  Noise level=-96 dBm
Encryption key:off
Bit Rates:54 Mb/s
Cell 02 - Address: 00:1C:10:1E:BC:EE
ESSID:"" [2]
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100  Signal level=-35 dBm  Noise level=-96 dBm
Encryption key:off
Bit Rates:54 Mb/s

Note: the SSID of the Linksys used in the test is  00:1C:10:1E:BC:EC.
When I removed power from the Linksys and ran the test again the ESSID:""  also disappeared from the list.

(2)  I retrieved my laptop and ran Network Stumbler to verify that the Linksys was playing nice.  When I entered the factory floor with my laptop I stopped and my laptop was able to see the Linksys router from about 60 yards away.  When I reached the production line I ran Stumbler and it reported good and healthy Linksys.

(2) Chris then retrieved his D-Link router (not to be confused with the one reported earlier) and we replaced the Linksys.  It works famously!!  Jive appears very happy with it.

(3)  I took both the Linksys Router and Jive under test to the conference room that we are occupying and performed the same test and it passed famously.

(4)  I then returned to the factory floor with my cased jive and a couple uncased new jives and went over to the Ray-Squeeze RF boxes.  We tested the Linksys router (out of RF range of the Jive assembly line) with each and the boards and they all fail with...

Cell 02 - Address: 00:1C:10:1E:BC:EE
ESSID:"" [2]
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100  Signal level=-35 dBm  Noise level=-96 dBm
Encryption key:off
Bit Rates:54 Mb/s

I replaced the Linksys with another Linksys - same result
I replaces the Jive with another - same result
I ran each inside the RF box - same result
I connected the Linksys to a regulated power supply - same result
I ran Jive from a battery - same result.
I ray Jive from a battery with the Linksys from a regulated power supply from inside an RF box - same result.

The Jive reporting is always the same:  SSID:"" and the same ill formed MAC.

The same setup works fine in the conference room.
We are leaving Chris' D-Link router behind.  Thanks Chris. (Dean, we owe Chris a router.)

I never thought I would see a day where D-Link would replace Linksys :-O
Comment 1 Blackketter Dean 2007-12-27 05:13:21 UTC
We need QA to reproduce and grab logs and/or network traces
Comment 2 Blackketter Dean 2008-01-25 22:36:18 UTC
Ping QA...
Comment 3 Blackketter Dean 2008-01-28 10:27:51 UTC
Steven: can you take a look at this?  Please test with this router and see if it's an issue specific to the device or to SZ.
Comment 4 Spies Steven 2008-01-28 10:38:07 UTC
Does anyone know the exact Linksys model, revision and firmware being used?
Comment 5 Blackketter Dean 2008-01-29 22:24:13 UTC
David:  please comment asap.  Thx!
Comment 6 Spies Steven 2008-02-01 10:56:27 UTC
Speaking to David he seems to think that this is a very isolated issue specific to Linksys and the Suzhou factory floor.  Without additional information about the router and other factors I do not think I will be able to reproduce.

Dean, should this be changed to unassigned and future for now?
Comment 7 Blackketter Dean 2008-02-01 10:58:45 UTC
Yes, until we can reproduce here, we're SOL.  
Comment 8 Richard Titmuss 2008-03-12 04:53:35 UTC
Reset priority