Bugzilla – Bug 3146
Squeezebox cannot connect to 2wire 1700hg in WEP-open mode
Last modified: 2008-12-18 11:38:49 UTC
I am a novice at this, so I'll do my best to give you the info you need. I am running Slimserver 6.2.1, on a Toshiba laptop with a 2.00 MHz pentium processor and .99 GB RAM with Microsoft Windows XP Home Edition 2002 Version 2. My Squeezebox2 (Serial #237CA2A) is using firmware version 28. I am wirelessly connected to the Squeezebox using a 2Wire Gateway 1701HG wireless modem/router with 64-bit encryption. The music files are being burned to a Seagate external hard drive with 400GB of memory, using Exact Audio Copy, with a .flac extension, and (I think) LAME compression. The problem is that from time to time (sometimes after every two minutes, sometimes after an hour), the music completely stops playing. The Slimserver shows that the music is playing and the Squeezebox shows the wireless connection at 100%, but no music is playing. This problem goes away if the Squeezebox is hardwired. I can start the music again by pressing play (or forward or reverse) on the remote control, but it will stop again after some short period of time. I am entering this bug at Kevin Pearsall's direction--he already had me try firmware version 29 and get rid of the encryption on the wireless router (which made the problem worse). I have a number of bug reports (from the slimserver d_source debugging program) that show what's happening (I can email those to you if you like). The common thread I've been able to find is the following entries: 2006-02-27 21:52:26.4108 00:04:20:05:d0:e6: Decoder underrun while this mode: play 2006-02-27 21:52:36.2780 00:04:20:05:d0:e6: Underrun while this mode: play If the response to "Decoder underrun while this mode:" is "playout-play", then there is no "underrun while this mode" entry and the device doesn't stop. If it's as above, then it stops. Please help. Thanks.
Chris, can you help reproduce?
jdg, Judging from your log, I'm theorizing that the Slimserver is failing to stream your music on to the squeezebox for some unknown reason. Many, many users store their music in FLAC format, so this should be pretty well-tested territory. Can you tell me what flac settings you are using to compress your files? For EAC + FLAC, I would expect this information to be under the "EAC" menu, then click on "Compression Options". This will bring up a little dialog box. Click the "External Compression" tab at the top. If you've set up EAC to compress to FLAC, the "Use external program for compression" box should be checked, and there should be a path to the flac.exe file in the "Program, including path, used for compression" box. Check to make sure that's true. If so, what are the command line options listed below that? Also, is there anything else unusual about the files you've created? Do they have exceptionally long or complicated names? Do you notice it "hangs" on one of your files more than any other? Thanks for any info! -- Christopher Owens QA Manager chris@slimdevices.com (510) 743-1152 x717
Actually a squeezebox2 bug.
Jeff: please try the soon-to-be-released 6.2.2 beta available on our website. A number of bugs that might trigger this symptom have been addresssed.
We're trying an RMA on Jeff's player to see if it fixes the problem.
Created attachment 1201 [details] ethereal capture of failing 2wire router Failure to connect using firmware 48. Test platform is: 2wire 1701HG ADSL gateway. mac address ending in 3d:39 Squeezebox 2 with FW48. mac address ending in c8:db WEP64 open authentication
Okay I have now reproduced Jeff's specific problem. I thought we'd fixed all the connectivity problems, but this one seems to have slipped through the cracks. I have attached an ethereal log from my test setup. Please let me know if there's anything more I can do to expedite things.
This is fixed in firmware 50. I do not have access to this router, so Chris will have to confirm. It is now in test and will be released soon.
Verified fixed in fw50
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.