Bug 1899 - wpa fails with netgear fwg114p
: wpa fails with netgear fwg114p
Status: CLOSED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 14
: Macintosh All
: P2 normal (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-01 13:32 UTC by Kevin Pearsall
Modified: 2008-12-18 11:38 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2005-08-01 13:32:10 UTC
 
Comment 1 Blackketter Dean 2005-08-01 14:36:24 UTC
Awaiting arrival of device.  Will give to kevin to reproduce when it arrives.

Comment 2 Blackketter Dean 2005-08-08 09:53:39 UTC
Kevin's got it and will test.
Comment 3 Blackketter Dean 2005-08-29 14:14:25 UTC
Kevin, can you take a look at this?
Comment 4 Blackketter Dean 2005-09-07 15:21:51 UTC
Kevin, can you take a look at this?
Comment 5 Kevin Pearsall 2005-10-06 15:48:03 UTC
i don't seem to have this device?  i have an fm114p but that unit does not
support WEP
Comment 6 Kevin Pearsall 2005-10-18 15:47:00 UTC
tested with fwg114pv2 v1.1_02 with wpa, 64b wep, and 128b wep and saw no
failures.  closing...:(
Comment 7 Kevin Pearsall 2006-01-19 12:17:09 UTC
reopening due to customer report of this issue occurring with SB3 with new wireless card.  Assigning to myself for regression.
Comment 8 Kevin Pearsall 2006-01-20 16:26:16 UTC
dont know if it helps, but from the bug report I see that you tested it with fwg114pv2. Mine is fwg114p(v1)...
Comment 9 Richard Titmuss 2006-04-18 11:53:16 UTC
Ready for Chris to test with firmware 41.
Comment 10 Chris Owens 2006-04-18 18:13:04 UTC
richard@slimdevices.com notes he has fixed this problem
Comment 11 Chris Owens 2006-04-18 18:13:22 UTC
Verified fixed in FW41
Comment 12 James Richardson 2008-12-15 12:31:19 UTC
This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.