Bug 3281 - WPA & WPA2 flakey with Netgear WPN802v1 (V2.0.6.0 firmware)
: WPA & WPA2 flakey with Netgear WPN802v1 (V2.0.6.0 firmware)
Status: RESOLVED WORKSFORME
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 41
: All All
: P2 major (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-16 14:12 UTC by Dr. Kooler
Modified: 2008-12-18 11:38 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dr. Kooler 2006-04-16 14:12:00 UTC
I've never had any problem connecting to a Netgear WPN802v1 (V2.0.6.0 firmware) Access Point with firmware 28 using WEP 128 encryption. But I never managed to get WPA nor WPA2 working (FYI, the AP is working perfectly in WPA2 mode with a G4 Powerbook and a G5 Imac.

I've now tried firmware 41 (with a frightening 'malloc failed' message displayed almost right after firmware upgrade) and got a bit further up the road to encryption-happiness as I managed to connect 2 times using WPA2 with a test key (987654321) though with having to frequently factory-reset & going back to WEP 128 in between in order to get back to a working setup.

Unfortunately, I eventually had to revert to firmware 28 as after the above fiddling I couldn't connect using wireless anymore (even with WEP 128 or encryption disabled), always getting the "Couldn't connect to the specified network" message...

Thanks for your help.

Cheers !
Comment 1 Chris Owens 2006-04-17 11:58:54 UTC
I tried to repro this bug on a Netgear WPNT834 we have in-house, and I was able to connect reliably using any security type.

I'm still going through other routers we have here to find problems.  With any luck, I'll find one that has the same issues with the SB3 as your Netgear.  Otherwise, I'll order one of that exact model to test with.
Comment 2 Dr. Kooler 2006-04-21 06:15:05 UTC
Tried firmware 43 today. No luck, still no WPA/WAP2. I only managed to connect once with WEP 128 after many unsucessful trials (and factory-reset)...
Back to firmware 28 (and WEP 128), which is the only one that picks up my network SSID immediately as the others (firmware 41 & 43) timeout 98% of the time with the "Cannot find specified wireless network" message .FYI, when testing, Squeezebox and AP are about 30 cm (1 ft.) away from each other.
Comment 3 Chris Owens 2006-05-02 17:28:48 UTC
Okay my wpn802 finally arrived.  I upgraded it to firmware 2.0.6.0, and it works great, I'm afraid.

What kind of Squeezebox do you have there?
Comment 4 Dr. Kooler 2006-05-03 08:47:07 UTC
Hi, I have a Squeezebox v3. Unfortunately, I won't be able to update it to the latest firmware (v48 I think ?) until a few day's time... I'll let you know once it's done.

By the way, what's the squeezebox firmware release you're testing against ?

Thanks for your help & time.
Cheers.
Comment 5 Chris Owens 2006-05-03 11:32:38 UTC
I'm testing with firmware 48 at the moment, yes.

You might want to compare your router settings to mine to see if there are obvious differences.

I have dhcp client enabled.  The unit is connecting downstream from my old reliable SMC7008ABR wired router, which is acting as DHCP server.  You may want to see on your router what your DHCP lease time is, and try changing it to see if it affects the amount of time before your SB3 disconnects.  That would narrow it down to a DHCP client issue rather than all of networking and wireless.

Under Wireless Settings:

Country/Region: United States (affects which channels are available)
(checked) Turn Radio On
SSID: qa-wpn802-2may06
(checked) Enable SSID Broadcast
Operating Mode: Auto 108Mbps
Channel/Frequency: 06
Output Power: 50% (set this low to try and reproduce your system since on my desk the router is only a few inches from the SB3)

Under Advanced Wireless Settings:

WMM Support: No (default)
RTS Threshold: 2346 (default)
Fragmentation Length: 2346 (default)
Beacon Interval: 100ms (default)
DTIM Interval: 1 (default)
Preamble Type: Auto (default)
(not checked) Disable Advanced 108Mbps Features (default)
(not checked) Enable eXtended Range (XR) Feature (default)
Comment 6 Chris Owens 2006-06-07 15:15:46 UTC
Hi Dr. Kooler,

Are you still having problems with this?  Let me know how it's gone for you.
Comment 7 Blackketter Dean 2006-06-20 11:32:34 UTC
Waiting for feedback from Dr. Kooler
Comment 8 Chris Owens 2006-06-30 14:15:22 UTC
I'll keep an eye out for this in the future, but it seems to work for me, for now.

Thanks for the info, Dr. Kooler