Bugzilla – Bug 7983
When connecting Duet via ethernet, Controller fails to detect ethernet
Last modified: 2009-03-25 08:29:21 UTC
I don't know if this is a Controller bug or a Receiver bug. When trying to connect a Duet via ethernet, either Standard Wired or Bridged, we should get the screen labeled "Wireless Connection" with choices, "Connect using Squeezebox" and "Connect to other wireless network". Currently this is hit or miss. Often when dealing with a customer, or in my own experience, this screen gets skipped the first time we try. Factory resetting both devices usually fixes the problem. This leads me to believe either: * Ray is not altering its wireless SSID when an ethernet cable is plugged in or * Jive is not detecting the altered SSID when it should This change should work on the fly, or rather, we should not require a factory reset to make this work correctly.
Dan: What firmware versions are on the Controller / Receiver. During the firmware validation testing, I did see this on r1425 - r18, but not with later versions. Please gather the following data so we can narrow down where this error is happening 1) Controller FW version 2) Receiver FW version 3) Manufacture / Model of customers AP / Router / Hub / Switch (Network Topography) 4) Was power applied to the Ray before or after the Ethernet cable was plugged in
I'm having connectivity issues as well. SB cannot find server. Mac OSX 10.4.11, SB hardwired to netgear 614 v6 wireless router. SB drops after computer reboot or sometimes after Netgear router reboot. DHCP enabled. When I restart router I often get a message indicating that the computer's local hostname is already in use on the network and it reassigns a new host name to my computer. This only started happening since adding the SB to my system. I have all the latest builds and firmware and nothing seems to help. When I can get the SB to talk to the server, it is usually pretty stable, but as soon as I power off the computer and on again I have to go through a serious dance of factory resetting, etc. in order to get back live. This is very annoying as I'm sure others can attest. I'd be happy to switch routers to a known good one of this is indeed the issue. It seems like the SB doesn't like DHCP with this router. That said, I haven't tried going static as I have many devices that I'd have to reconfigure. If it would help I would. Any help would be appreciated. Is this happening with the previous version of Squeezebox? Maybe I should downgrade and turn in the Duet. Seems like we are the involuntary beta testers here. Thank you, Tyler
I have the same problem. I need a solution soon before my 30 day return is up, or it all goes back. Controller Version 7.0.1 r2448 root@padbuild #74 Tue May 13 11:45:21 Receiver Firmware Version 23 Router Watchguard Soho wg2500 I tried every combination of power up sequence. It sometimes connects on repower up of router, reboot server, restart squeezecenter factory reset receiver then factory reset controller. One day later, the BLUE light is back. Ed
What this bug refers to is an issue in Setup only. The workaround for the Setup issue is to first plug the ethernet cable into your Receiver, then do a factory reset on the Receiver by holding down the front-button for 10 seconds. (the LED will flash red very quickly indicating it's doing a reset.) Then go through setup and you should get the additional setup menus allowing for ethernet connectivity. Once connected, you should not need to reset again to reestablish connection. Any other issues you are experiencing, please contact Support at 877-887-8889 or support@slimdevices.com.
Dan is this bug assigned to you for a particular reason? If not, please assign it to QA to reproduce and add appropriate logs etc.
Unknown. I'll assign it to QA.
Is the behavior here because the ethernet cable needs to be plugged in prior to powering on? QA to reproduce, recommend assigning to Felix if that is confirmed.
QA to reproduce in 7.2
Unable to reproduce with 7.2
*** Bug 8740 has been marked as a duplicate of this bug. ***
Verified not reproducible with SqueezeCenter 7.2.1-23472 Controller 7.2 r3070 Receiver r48 SB2/3 r113 Transporter r63 Boom r33
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.