Bug 8847 - Controller loses its wireless connection when connected to Actiontec MI424-WR.
: Controller loses its wireless connection when connected to Actiontec MI424-WR.
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: PC Windows XP
: P1 normal (vote)
: 7.3.3
Assigned To: Ross Levine
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-23 13:54 UTC by Julius Dauz
Modified: 2010-07-09 08:34 UTC (History)
8 users (show)

See Also:
Category: ---


Attachments
log showing dhcp failure, controller reboot (267.22 KB, application/octet-stream)
2009-01-07 16:09 UTC, Ross Levine
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julius Dauz 2008-07-23 13:54:02 UTC
A customer with a Squeezebox 1 is having issues connecting it to his Actiontec MI424-WR with WEP enabled. If he disables WEP, then it connects just fine.
Comment 1 James Richardson 2008-07-29 11:13:17 UTC
Ross: do we have this router here? if not, let get one to test with.
Comment 2 Ross Levine 2008-07-29 13:27:56 UTC
Reproduced, thanks James for helping me find the Actiontec router. 
Comment 3 Chris Owens 2008-08-04 09:26:47 UTC
We're not going to update that firmware at this point.
Comment 4 Osama Zaidan 2008-12-09 16:13:52 UTC
I have been testing the Actiontec MI424-WR router for a few days.
Initially the Duet controller and the receiver connect fine during the setting.
But, the controller keeps going to a Blue light and drops its connection every now and then.

When the controller losses its connection if I click any of the controller options, the controller tries to connect to my testing PC, and then it  comes to the following menu 

Try Again 
Choose Music Source 

The wireless indicator is always blue, it does not go to red nor white. 


Setting the controller to factory reset solves the problem for 45 minutes to two hours then the controller goes to blue again.
Comment 5 Ross Levine 2008-12-09 17:04:21 UTC
Osama, you were testing with an SB3 and Duet right? This bug is about SB1; if you've confirmed with newer hardware that would make this bug more relevant. 
Comment 6 Osama Zaidan 2008-12-10 09:16:15 UTC
Sorry, I had tested the Duet only. 
I have been instructed to reopen this bug instead of creating a new one for the Duet controller.
Sorry about the confusion.
Would you like for me to open a new bug and leave this one for SB1 only?
Comment 7 James Richardson 2008-12-19 08:01:47 UTC
Changing target to next release
Comment 8 Ross Levine 2009-01-07 16:09:17 UTC
Created attachment 4572 [details]
log showing dhcp failure, controller reboot

I can't seem to get my Controller to get an address via DHCP from the Actiontec MI424 with 7.3 r3698. Attaching a log show many DHCP failures. I'm able to get Duet working fine with this router using self assigned IPs most of the time. However this log shows the one time I tried it and the Controller rebooted after I chose my Receiver.
Comment 9 Ross Levine 2009-01-08 13:54:15 UTC
Any other testing needed from me? Richard would you like me to ship this to you?
Comment 10 Walker LaRon 2009-02-12 20:08:55 UTC
Ticket 090212-002829
Squeezebox Boom

Customer cannot connect Squeezebox Boom to Actiontec MI424-WR
Firmware on the router is up to the latest (he performed update while I was on the phone

Will connect when using WEP 64
Will connect when encryption is off
Will not connect using WPA TKIP (also tried AES just to see)

Per the router status page, should work with WPA2, but customer states he called Verizon,and there is no WPA2

Customer does not want to use WEP64 because states it is "not secure"
Comment 11 Chris Owens 2009-03-16 09:35:31 UTC
We are now planning to make a 7.3.3 release.  Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future.

Thanks!
Comment 12 erik 2009-03-16 21:30:38 UTC
I agree with all below findings except I still have 'dropping' issues under WEP64.  Will connect, but drops after an indefinite and ever changing period of time.
Comment 13 Chris Owens 2009-03-30 17:18:59 UTC
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out.  If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it.

Thanks.
Comment 14 stevesatch 2009-03-30 17:28:02 UTC
Please don't wait for the 7.4 release.  So many people have Verizon Fios and use the Actiontec router.  It just doesn't work correctly with the squeezebox.  We're all just waiting for the fix so we can use our squeezeboxes like everyone else.
Comment 15 erik 2009-03-30 19:13:11 UTC
I couldn't agree more with comment#14.  Every day I check for a fix - hoping that one day i will be able to simply turn on the squeezebox rather than reboot and reset.  There are probably not a lot of people bothering to get this far in their quest to find a solution but there are A LOT of connection complaints out there on the interweb.  I's probably safe to say that anyone with a Squeezebox and FIOS would benefit from an immediate fix.  Thanks.  I'll buy you a cookie.
Comment 16 James Richardson 2009-04-06 09:59:08 UTC
Ross: Can you please check 7.3.3 r5149, as this version may address this bug.
Comment 17 Ross Levine 2009-04-08 13:53:15 UTC
Fixed in 7.3.3 - r5225. If you've experienced this bug please update to latest nightly 7.3.3 build. Install the new version of SqueezeCenter, update your Duet firmware, factory reset both Controller and Receiver and setup one more time. Please post here in the bug with your findings. 

7.3.3 nightly download here:

http://downloads.slimdevices.com/nightly/?ver=7.3
Comment 18 erik 2009-04-08 20:54:39 UTC
7.3.3 - 25862 squeezecenter installed on computer.  
both components factory reset.
controller still at software version 7.3 r3993
squeezebox connected to squeezenetwork ok
(unable to determine squeezebox firmware, assume its up to date)
so far so good after 20 min.  will keep everything on for a couple of hours and let you know if anything drops.  
thanks for the efforts.
Comment 19 stevesatch 2009-04-09 13:34:47 UTC
working so far for me :)
Comment 20 erik 2009-04-13 19:10:33 UTC
went away for 4 days.  came home and clicked "turn on squeezebox", but it didn't turn on.  unplugged squeezebox and plugged it back in.  clicked on "turn on squeezebox" and it worked.  perhaps problem still exists?
Comment 21 erik 2009-04-13 19:11:11 UTC
went away for 4 days.  came home and clicked "turn on squeezebox", but it didn't turn on.  unplugged squeezebox and plugged it back in.  clicked on "turn on squeezebox" and it worked.  perhaps problem still exists?
Comment 22 Ross Levine 2009-04-14 11:08:27 UTC
Erik, was your source Squeeze Center or Squeeze Network?
Comment 23 erik 2009-04-14 17:22:25 UTC
(In reply to comment #22)
> Erik, was your source Squeeze Center or Squeeze Network?
I always leave the source as Squeeze Network to take advantage of my online locker and online radio. Though the computer is usually on with SC running, the remote is set w/ SN as source. I almost never change this.
Comment 24 Ross Levine 2009-04-14 17:50:18 UTC
Thanks Erik. We had a couple Squeeze Network issues last week that sound a lot like what you described. I'm still optimistic about the wireless connectivity improvements in the 7.3.3 nightly firmware.
Comment 25 erik 2009-04-15 21:07:23 UTC
2 days since last operated, and, once again, the remote would not turn on the Sbox until i unplugged it and plugged it back in again.  Then, oddly, I could navigate, select, and hear different music sources and, but the controller consistently showed an older playlist as "now playing".  even if the playlist was "cleared", it would return on the controller when another song from any source was selected.  A quick battery in-n-out fixed this.  Since you mentioned having issues with the network, I did another factory reset of both the SB and controller.  Will advise.  How about SteveSatch, all ok?
Comment 26 erik 2009-04-27 22:26:20 UTC
i know you show this as resolved already, but just wanted to say thanks for the efforts.  after resetting everything one final time 1 week ago, there seem to be no more issues; connections stay put.  Again, my thanks to all: this is a great product.  take care.
Comment 27 Ross Levine 2009-04-29 17:39:33 UTC
Verified to be fixed in 7.3.3 - 26246, r5497. Thank you Erik!
Comment 28 James Richardson 2009-06-17 09:35:23 UTC
This bug has been fixed in the 7.3.3 release version of SqueezeCenter!

If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html 

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 29 Perry 2009-12-29 17:22:59 UTC
I am still experiencing problems with my SB1 when I try to connect to the Actiontec via wireless.  I also have two Booms that connect fine.  It seems like it could be an 802.11b issue between the SB1 and the Actiontec.

My solution has been to put a DLink 625 in front of the Actiontec to serve as a Wireless Access Point.  This configuration allows the SB1 to connect, but it has the disadvantage that nothing synchronizes properly.  Even the two Booms which sync perfectly through the Actiontec wireless are out of sync once the DLink is in the picture.

So I would very much like to go back to just the Actiontec.

I am running 7.4.1 with firmware 40 on the SB1 and I checked that the Actiontec is up to date as well (at least its web interface said it was up to date).
Comment 30 erik 2009-12-29 22:24:12 UTC
Hi,

I'm back.  I have to agree that the problem is back as well.  All was good for a while but after the major update the connection drops have returned.  I frequently have to reset the duet squeezebox and the controller, which is annoying at the least.

The box is connected via ethernet to the network (not wireless.)

I can honestly say that whatever you did before to make it "fixed" has been undone by the latest "major" update.  Please reopen the investigation into this and repair (again).

Thanks.
Comment 31 stevesatch 2009-12-29 22:42:15 UTC
I've been having trouble with my duet controllers lately.  It had been fixed for a long time too.  I hope it gets looks at again because the fix was working really well.
Comment 32 erik 2010-01-19 20:00:48 UTC
(In reply to comment #31)
> I've been having trouble with my duet controllers lately.  It had been fixed
> for a long time too.  I hope it gets looks at again because the fix was working
> really well.

Hey guys.  I'm not sure if the latest comments went through since this is marked as "Closed." So I e-mailed Ross directly with the bug link and asked him to reopen.  We'll see if anything happens.  I hope it does.
Comment 33 Adam Irwin 2010-07-09 07:29:18 UTC
Customer Comments:
================
- Cust is still unable to get SB Boom Connected to Router

Agent Notes:
==========
- Verizon Action Tech Model # E212044.....Mi424-Wr
- 00:04:20:1e:ee:14
 
Troubleshooting:
============
- Factory Reset - walked through Setup - Failed to Connect
- Router is 3 ft away 
- Boom Firmware 50
- Turned encryption off worked
- Connected via ethernet ok 

Resolution:
========
- Waiting - Reported issue to www.bugs.slimdevices.com bug # 8847
- Escalated 

Case # 100708-001024
Comment 34 Adam Irwin 2010-07-09 08:30:16 UTC
Customer Comments:
================
- Cust is still unable to get SB Boom Connected to Router

Agent Notes:
==========
- Verizon Action Tech Model # E212044.....Mi424-Wr
- 00:04:20:1e:ee:14
 
Troubleshooting:
============
- Factory Reset - walked through Setup - Failed to Connect
- Router is 3 ft away 
- Boom Firmware 50
- Turned encryption off worked
- Connected via ethernet ok 

Resolution:
========
- Waiting - Reported issue to www.bugs.slimdevices.com bug # 8847
- Escalated 

Case # 100708-001024