Bugzilla – Bug 9907
Network settings after power interruption
Last modified: 2008-12-18 10:28:19 UTC
When I move the Boom from one room to the next the network reconnection is erratic. Sometimes I just get the normal "obtaining network address" and then it uses DHCP to find one. Other times I have to go through all the network setup steps, just reconfirming the setup options I've chosen (country, WEP key, etc). Other times I have to unplug it and replug it to make it chose either of these options, it just hangs. There are other (weaker) wireless routers in the area, but I've specified a unique named one so there shouldn't be any confusion. In addition it also fails to connect to the squeezenetwork and I have to select this manually. I don't use squeezeserver, so it always complains that it can't find one under these circumstances, since there isn't one. There should be a way to tell it to ignore this option. I've tried giving it a fixed IP address, but then I have to reconfirm all the setup: netmask, DNS, etc. when it fails to reconnect by itself. I can't see any pattern as to when it reconnects properly and when it demands going through the options.
Normal behavior for a fully setup player when powered up is to reconnect to what it was connected to last. I've just tried that here with a Boom using wireless and DHCP connected to SN about ten times and it always just reconnected to SN just fine. If wireless is in play I could think of two reasons why it could fail: - Another wireless AP with the same SSID (from a neighbor maye?) - Player is placed too far away from the AP If DHCP is used: - No free IP addresses left If it is connecting to SN: - Internet connection temporarily down When the player is powered up again, make sure you do not press any buttons or use the remote else the automatic reconnection will be interrupted and you either have to go through all settings again manually or unplug and replug it again. I would try changing SSID and/or channel and maybe give it a fixed IP address. Felix
There is only one machine on the wireless LAN and it has a fixed IP address. The network SSID is unique in the region. Giving the boom a fixed IP means that when it fails to connect when repowered one has to go through an even longer list of setup items. Instead of just region, router identity, use DHCP and WEP key, one also has to answer questions about fixed IP address, netmask and DNS address. This means scrolling through all the IP digits. Signal strength as reported by the boom is 80+% is the both locations that it is moved to. As I said when it connects and when it requires going through the setup doesn't seem to be correlated to anything else, that's why I opened a bug report. The thing about obscure bugs is that they only occur when a certain set of conditions exist, so others may have a hard time reproducing them. Perhaps the model of router and/or its firmware may be the difference. Some routers may respond slower or use slightly different handshake protocols that affect timing. For what it's worth mine is a linksys WRT54G.
RDF: how long do you let the Boom sit after a power cycle, before you 'reconfigure' the network settings? As Felix notes, "When the player is powered up again, make sure you do not press any buttons or use the remote else the automatic reconnection will be interrupted and you either have to go through all settings again manually or unplug and replug it again."
I've done some further experiments. When I get the setup screen now I just unplug and replug the Boom and most times it will then shift to the "obtaining IP" screen, get the address via DHCP and then return to the power off state. I think this confirms my guess that there is some type of handshake failure with the wireless router that happens from time to time. If I get the network setup screen it will sit there "forever" until I press the knob and step through the various options. Another curiosity is when I use my microwave which is a bit too close to the Boom (about four feet through a wall). The stream gets interrupted, but the Boom gets confused and ends up just showing the clock (as it does when off). I have to turn it off and on again for it wake up properly, and, of course, reselect the stream I was listening too. I don't really consider this a bug, since there were no promises made by the FCC when they opened up this part of the spectrum that one wouldn't run into interference.
Felix: related to bug 9706 or bug 9693 in any way?
James: No, I don't think so because these both are when switching from SN to SC; bug 9706 is if SN is sending a player to SC and bug 9693 is if you first connect to SN and then connect to SC. In this bug the settings are _not_ lost, just the automatic step-through seems to be confused somehow, which then makes it necessary to go through all settings again manually.
Tested Boom r33 with SN only (no SC associated) Tested Boom r39 with SN only (no SC associated) Wireless Setup - Auto DHCP Re-set power to the device several times, unable to reproduce the error. Tested Boom r33 with SN only (no SC associated) Tested Boom r39 with SN only (no SC associated) Wireless Setup - Manual DHCP Re-set power to the device several times, unable to reproduce the error. ============== Can you tell me more about your Access Point; 1) Manufacture 2) Model 3) Firmware Version 4) Internet Provider 5) Internet type (cable/fiber/DSL/etc.) Can you also give me the MAC address from the bottom of your Boom?
(In reply to comment #7) > Tested Boom r33 with SN only (no SC associated) > Tested Boom r39 with SN only (no SC associated) > > Wireless Setup - Auto DHCP > > Re-set power to the device several times, unable to reproduce the error. > > Tested Boom r33 with SN only (no SC associated) > Tested Boom r39 with SN only (no SC associated) > > Wireless Setup - Manual DHCP > > Re-set power to the device several times, unable to reproduce the error. > ============== > Can you tell me more about your Access Point; > 1) Manufacture > 2) Model > 3) Firmware Version > 4) Internet Provider > 5) Internet type (cable/fiber/DSL/etc.) > > Can you also give me the MAC address from the bottom of your Boom? > 1. Linksys 2. WRT54G 3. v1.00.6 4. AceDSL (irrelevant, the Boom fails to get the IP address via DHCP from the router) 5. DSL MAC addr on Boom: 00:04:20:1E:05:65 Firmware version 33 Using a WEP key Note unplugging and replugging will usually get the Boom to get the IP address on the second (or third) try.
Robert: can you try the following and report back please: 1) power up a boom 2) press and hold the back button to get to the setup menu 3) scroll to Current Settings 4) scroll to Factory Test 5) scroll to Snoozebutton test 6) test your snoozebutton(s) - the display should start out by showing a 'full' icon. as you press the snoozebutton (there are 5 sensors) they should change to a 'half up' then 'half down' icon. At the end of the test, they should all be 'half down' Pressing DOWN should move the cursor UP Let me know if you see that behavior, or, if any of the buttons are "stuck" in the 'half up' mode.
(In reply to comment #9) > Robert: can you try the following and report back please: > > 1) power up a boom > 2) press and hold the back button to get to the setup menu > 3) scroll to Current Settings > 4) scroll to Factory Test > 5) scroll to Snoozebutton test > 6) test your snoozebutton(s) - the display should start out by showing a 'full' > icon. as you press the snoozebutton (there are 5 sensors) they should change to > a 'half up' then 'half down' icon. At the end of the test, they should all be > 'half down' > > Pressing DOWN should move the cursor UP > > Let me know if you see that behavior, or, if any of the buttons are "stuck" in > the 'half up' mode. > It seems to work as you described. I assume the five sensors are distributed across the snooze bar, so that one has to be in the right spot to trigger each of the icons. If I get the spot correct then pressing down on the bar causes the icon to go up and then releasing it leaves it in the down position. Not that you asked, but I also ran the regular button test and everything worked as expected. When moving the radio to a new location I carefully stay away from pushing the snoozebar by accident, or any other button for that matter.
I'm trying something else. At times when powering up it seems as if the boom is hanging up trying to connect to squeezecenter (which is undefined) so it just sits there saying "connecting..." I just entered the IP of the real squeezenetwork as the address of the squeezecenter as well as squeezenetwork and I'll watch to see if they has any effect on future repowering behavior.
Robert, let me know how that works out. Later this week we are releasing a new version of Squeezenetwork, which should include a new firmware version for Boom. Once that happens lets see if the error you are having goes away or not.
Robert: can you try again this week? we have released new firmware for the boom, that my address this issue. Make sure you are on Firmware 40
(In reply to comment #13) > Robert: can you try again this week? we have released new firmware for the > boom, that my address this issue. > > Make sure you are on Firmware 40 > I've tried powering up and down several times since the firmware upgrade and haven't had any problems. The handshake seems to take slightly longer (still not more the 10 seconds) welcome->connecting->obtaining IP address -> powers off. So it seems fixed.
Robert: Thank you for the feedback and I'm glad its working for you now :) Marking bug as verified