Bugzilla – Bug 9415
boom DHCP timeout too short, doesn't even count down to zero
Last modified: 2008-12-15 12:07:21 UTC
When the Boom is looking for a DHCP server to get a lease/IP address, it starts a timer that counts down from 30. It stops at 9, never getting to zero. My DHCP server can be slow and doesn't always respond quickly. When this happens a Boom can't get a lease, can't find a SqueezeCenter, and life is bad. As a result, it looks like the Boom can't talk to the network. I reported this during beta, and Mickey G and I did a swap. When he got the beta/pre-production unit, it worked perfectly for him, at Slim Galactic HQ. The replacement unit, is a new production unit, standard packing, etc. It also can not talk to my server. See http://forums.slimdevices.com/showthread.php?t=50828
QA to reproduce
Can you tell us what router you are using, as well as which DHCP host you have? Is your boom Wired or Wireless? What version of firmware is on your boom currently?
I've tried both wired and wireless. I'm mostly interested in wireless, did wired just to problem isolate. I know how to get the firmware version once it is on the network, but I'm not getting that far. How do I get it without the network? is it in a menu? PS, this is fairly easy to replicate, at least the failure to count down past 9. Setup a SC server with DHCP, use a hub, and have just the Boom on the network. Kill the dhcp daemon, start the boom, and it will try to get a DHCP lease and fail. You can watch it count down from 30 to 9, where it gives up. At least we need to count down all the way to 0
QA has verified that BOOM r33does time out after 21 seconds, not 30 seconds as the count down timer would indicate. Felix, would this be a Firmware fix? reassign to 73 if appropriate.
Pat: It would still be interesting to know what router / DHCP server you are using that is so slow not to react within 20 seconds, especially since you state in the forum thread that you can see the DHCP request in the log. Thanks, Felix
Pat, another question came up. Are you saying with the same DHCP server your SBs and other players get an ip address just fine and Boom is the only one that fails to do so?
I have two Debian Etch servers that are the DCHP servers for the subnet. One primary, other failover. The failover server is also the server for SqueezeCenter. The SC/dhcp box is a AMD 3000+ single cpu system, one gig ram, terabyte of disks. on MB nic. Yes, I've had two booms, and neither can get a DHCP lease in time. I've got two SB1, a Transporter, Controller, Receiver, in addition to the booms. And lots of laptops, desktops, etc. Only the Booms fail to get a DHCP lease. For some reason that I can't debug, connecting to the SC box is much slower than all the rest of the computers in my house. For example, a simple SSH into it takes 10 seconds, and SSH into anything else is near instant.
I have no idea why only Booms would fail in that particular setup. As far as I am concerned all players (SB3, TR, SBR and Boom) use identical fw code regarding DHCP. Caleb: Could different hardware (i.e. ethernet jacks, etc.) be a possible cause?
Changed code to allow DHCP 30 seconds countdown to go all the way down to 0. This should help when a slow DHCP server is used. Fixed in rev5125, will be in SB3 fw 119, TR fw 69, SBR fw 54 and SBB fw 39
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.