Bug 6536 - WPA/WPA2 encryption on Verizon Actiontec router
: WPA/WPA2 encryption on Verizon Actiontec router
Status: RESOLVED WORKSFORME
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 81
: PC Windows XP
: P2 normal with 1 vote (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-03 14:58 UTC by Osama Zaidan
Modified: 2008-12-18 11:42 UTC (History)
7 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Osama Zaidan 2008-01-03 14:58:06 UTC
SqueezeBox is unable to access/talk to Verizon Actiontec router MI-424WR using WPA or WPA2.
It works fine if we us WEP encryption. 
After looking in our Forums this problem may not be an isolated incidence.
http://forums.slimdevices.com/showthread.php?t=35952&highlight=verizon. 
The common factor between all of these complains is Verizon.
Comment 1 Chris Owens 2008-03-11 11:31:43 UTC
Hi Osama, just a note: It's best to leave new bugs with a target of '--' or they will get ignored, sadly.
Comment 2 Chris Staab 2008-03-13 12:37:41 UTC
I am contemplating purchasing HomePlug adapters to work around this, but would rather not spend the $$ if a fix is in the works.  Is this likely to be addressed in the near future or is it considered an issue on the router side, not the Squeezebox side?  If there is any need for testing of possible fixes I would be happy to assist.
Comment 3 Adrian Vasquez 2008-03-25 09:36:48 UTC
Same thing happened to me:  

Duet Receiver cannot be set with WPA/WPA2 encryption.  Controller has no trouble with this, so there's got to be something about the receiver that is not working.  Workaround is to use WEP encryption. 

Adrian.-
Comment 4 Alberto J. Chinique 2008-04-04 15:16:55 UTC
This bug is still present in squeezecenter 7.0 running firmware 86 on a squeezebox 3. I originally contact tech support a few months ago and they opened this bug report for me. Since then, there has been NO ACTION, NO UPDATES, nothing from Logitech/Slim Devices on this issue.  I'm a seriously annoyed customer at this point! This issue is not unique to me, check out your own community forums. More and more folks are switching to Verizon FIOS service here on the east coast. As they switch they'll end up hitting this problem too!  Will someone please take responsibility for this bug and address it soon. Otherwise, I'll probably think twice about purchasing any other Logitech/Slim Devices products!!!!  I'm willing to provide as much assistance as I can to try and resolve this. I'm sure that others having this problem would as well.  Please contact us, get our help and get this fixed before you ruin your reputation as a company.

Thanks,
Alberto
Comment 5 James Richardson 2008-04-07 08:54:40 UTC
Alberto:

Can you please try 7.0.1 build 

http://www.slimdevices.com/downloads/nightly/latest/trunk/

Let us know if this issue still happens with this version.
Comment 6 Chris Owens 2008-04-07 09:36:29 UTC
Ross do we have an Actiontec router we could do a Sniffy capture on?
Comment 7 Ross Levine 2008-04-07 13:35:11 UTC
Chris we do not have an Actiontec but we should, I just ordered one from the bay I'll attach sniffy captures once I receive it. 
Comment 8 Chris Owens 2008-04-14 09:39:42 UTC
Did we get the router yet?
Comment 9 Ross Levine 2008-04-14 11:46:15 UTC
Due here tomorrow according to UPS. 
Comment 10 Ross Levine 2008-04-15 16:27:53 UTC
Actiontec MI424-WR arrived DOA, thanks ebay. Trying to get a hold of another one, sorry for the delay. 
Comment 11 Chris Owens 2008-04-16 09:51:10 UTC
Please do that as quickly as you can, Ross.  Thanks.  I promise I will approve the expense report! :)
Comment 12 Ross Levine 2008-04-16 11:42:00 UTC
I convinced them to cross ship a replacement which should ship today. Thanks Joseph for helping me ship the DOA back. 
Comment 13 Alberto J. Chinique 2008-04-17 17:18:24 UTC
I just tried the 7.0.1 nightly build on linux. It appears that the bug was fixed. I was able to connect to the ActionTec MI424WR using WPA2. Perhaps it was fixed by one of:

#6994 - Problems connecting WPA and WPA2 to Netgear WNR3500
#7415 - Apple Time Capsule, Airport Express N don't work with Squeezebox

I'll do some more testing to see if I can break it. Thanks for working on this!

Alberto
Comment 14 Chris Staab 2008-04-17 19:21:28 UTC
I updated to the latest nightly and am able to connect using WPA2.
Comment 15 Chris Owens 2008-04-21 09:33:15 UTC
This is encouraging, but I'd still like Ross to have a look next week when we get the router in.
Comment 16 Ross Levine 2008-04-22 17:02:00 UTC
Thanks Steven for looking at this along with me. We received the MI424WR and tested with firmware 88, it connects fine with WPA. We then went back to firmware 81, it also connects fine with WPA. 

Please feel free to re-open this if anyone sees this issue again.  
Comment 17 Andy Grundman 2008-04-28 21:45:59 UTC
My friend has one of these and says he still cannot use WPA with firmware 88.  Even after a factory reset, the SB asks for a WPA2 password, even though he is only using WPA.

His router firmware version is 4.0.16.1.56.0.10.7.
Comment 18 Andy Grundman 2008-04-28 22:10:35 UTC
More info: WPA2 does work, but then fails at DHCP.  I've asked him to add his comments to the bug.
Comment 19 Joe Polk 2008-04-28 22:33:36 UTC
When I first tried accessing my Squeezebox after upgrading my home Internet to Verizon FiOS (and their lovely Actiontec router), my SB auto-detected my network and asked for a WPA2 password (even though my router was set to WPA).

I changed my router to WPA2 and my SB accepts the password now.  Unfortunately, it fails when trying to get an IP address from the router and gives the following error -- Can't find DHCP server -- and then it asks me to self-assign the IP address.  I shouldn't need to do that, however, since every other wireless device on my network works just fine via DHCP.


Comment 20 Chris Owens 2008-06-04 15:49:13 UTC
Andy says he'll try to go over to his friend's house and check it out in more detail.
Comment 21 Chris Owens 2008-06-20 13:45:23 UTC
I'd like to put a target on this to make sure it gets looked at.

Andy or Ross, is there any update?  

Ross, perhaps you could correspond with one of the fine users who have added their addresses to this bug and see if they will permanently or temporarily trade you for our Actiontec router long enough to get a capture for Felix to look at?
Comment 22 Ross Levine 2008-06-20 15:04:02 UTC
Chris we actually already have this router in house and so far are unable to reproduce this bug, see comment 16. Andy did you ever get a chance to take a closer look? I'll give this another shot today. 
Comment 23 Andy Grundman 2008-06-20 15:10:59 UTC
No, not yet.
Comment 24 Ross Levine 2008-06-20 15:28:00 UTC
Still works fine here. Andy or Chris let me know if you'd like anything else from me. 
Comment 25 Andy Grundman 2008-06-24 09:41:44 UTC
Going to check this router out tomorrow.
Comment 26 Ross Levine 2008-06-25 13:06:34 UTC
Andy was able to connect just fine at his friends house, marking this works for me. Please feel free to re-open if anyone feels this needs further investigate; please include details. Thanks Andy.