Bugzilla – Bug 7415
Apple Time Capsule doesn't work with squeezebox v3
Last modified: 2009-09-08 09:21:35 UTC
I can not get squeezebox v3 to work with or w/out encryption with Apple Time Capsule wifi router. I tired all versions of encryptions as well as none. It will not connect .. I plug in my old netgear and it works.
not a blocker as this is a rather specific problem case, not a total stoppage of slimserver. Let's try to keep the severity abuse to a minimum. https://bugs-archive.lyrion.org/page.cgi?id=fields.html#bug_severity Please consider using the netgear as a workaround.
Peter, did you try disabling the N mode and running Time Capsule in G only mode? Chris, looks like we may need to get our hands on a Time Capsule.
(In reply to comment #2) > Peter, did you try disabling the N mode and running Time Capsule in G only > mode? > > Chris, looks like we may need to get our hands on a Time Capsule. Hi - I'm another user affected by this issue. Re: running time capsule in G only mode: the available modes are: 802.11.n (b/g compatible), 802.11n (802.11a compatible) and 802.11n only (2.4 or 5.0 GHz spectrum). There is no option to disable N mode. I'm using 802.11n (b/g compatible). Available security modes are: none, WEP Transitional, WPA/WPA2 Personal, WPA2 Personal, WPA/WPA2 Enterprise, and WPA2 Enterprise. Have tried none, WPA/WPA2 Personal, and WPA2 Personal. No luck with any of those. Access control (MAC or Radius) is DISABLED. Formerly was using an Apple Airport Extreme (802.11n-capable, gigabit ethernet) with WPA2 personal, and all was peace, love, and music streaming.
Oh yea, Apple hides the legacy radio modes with their newer Airports and I don't know why, sorry about that. With the pre-N Airport extremes you need to hold down the option or alt key on the keyboard while selecting the radio mode menu with the mouse. You should see more radio modes such as G only when you do this. If you are not able to select other radio modes this way on Time Capsule or if selecting other radio modes does not do the trick hopefully another option will present itself soon. Even if selecting non pre-N radio modes work this would just be a temporary fix. I wonder if other devices are having trouble connecting to the Time Capsule, I will poke around on the Apple forums and see.
don't do it Steven. Hold out for getting one in house. Better yet, tell them you need to take it home for prolonged research.
i have had some trouble with some routers dhcp-wise, meaning trying to get SB to connect via dhcp was problematic. so instead i set the SB to a static yet private IP outside the dhcp range and that seems to work fine. have you guys tried that?
Has anyone tried hooking up their Squeezebox directly to the Time Capsule with an Ethernet cable? Does it connect ok then? If so this may indeed be a DHCP issue and not a WiFi issue just like Mike said. Any feed back welcomed and appreciated.
I have a couple of customers that have reported this issue as well. I am having them try the ethernet connection as you suggested Steven. I will let you know their results as soon as they get back to me.
(In reply to comment #8) > I have a couple of customers that have reported this issue as well. I am having > them try the ethernet connection as you suggested Steven. I will let you know > their results as soon as they get back to me. I just tried this, and my SB3 will not connect to the TC in wired *or* wireless mode. It *does* work with an Airport Extreme N. I also tried every wifi mode on the TC, even the ones that aren't visible until one holds down the 'option' key when selecting the modes menu. Still, no joy. Is the problem a DHCP conflict? My SB3 is the only piece of non-apple gear on my network (I like their koolaid), so I can't test other gear to see if it also has the problem. There are a few other squeezebox users on Apple's TC forum. <http://discussions.apple.com/forum.jspa?forumID=1253> (search for squeezebox) One guy says his works on a wired connection, but he doesn't say what gen SB he has. XBOX 360's also seem to be afflicted.
It works for me in wired, but not wireless mode. I have assigned an IP address in the middle of the DHCP range to the SB (did this before I tried wired; no idea if it makes a difference), Tony (In reply to comment #9) > (In reply to comment #8) > > I have a couple of customers that have reported this issue as well. I am having > > them try the ethernet connection as you suggested Steven. I will let you know > > their results as soon as they get back to me. > > I just tried this, and my SB3 will not connect to the TC in wired *or* wireless > mode. It *does* work with an Airport Extreme N. > > I also tried every wifi mode on the TC, even the ones that aren't visible until > one holds down the 'option' key when selecting the modes menu. Still, no > joy. Is the problem a DHCP conflict? > > My SB3 is the only piece of non-apple gear on my network (I like their > koolaid), > so I can't test other gear to see if it also has the problem. > > There are a few other squeezebox users on Apple's TC forum. > <http://discussions.apple.com/forum.jspa?forumID=1253> (search > for squeezebox) One guy says his works on a wired connection, but he doesn't > say what gen SB he has. XBOX 360's also seem to be afflicted. >
i have had the same issue on wireless connection to slim device. It worked fine with the migration from and old eMac (10.4.1) to a new imac (10.5.2) while i still kept my old apple airport extreme base station. however, when i replaced the apple base station with a new time capsule acting as my wireless router, it no longer could connect. it simply times out in the connection to the wireless network (i had also automatically taken the config settings from my previous wireless router so no other changes were made) My iphones connect through wireless fine as well as multiple IBM thinkpads. Using ethernet is not an option as the point of buying the slim device was for wireless playback.
We have had an Apple Time Capsule on order but they are hard to come by at the moment and I do not have an estimate on when we will have one. Once we have one in our possession we can investigate the situation and hopefully provide a fix quickly. Thank you for your patients.
Managed to get my hands on an Apple Time Capsule today and I am able to confirm that SB2/3, Transporter and Receiver are unable to connect successfully over WiFi. The behavior is that they all time out on the "Connecting to wireless network:" screen. Controller connects without issue and SB1 will connect with the proper settings. I will be attaching a WiFi capture momentarily. Is this one for you Felix?
Created attachment 3060 [details] WiFi capture of SB3 attempting to connect to Apple Time Capsule on channel 9
Thanks Steven. I am correct in assuming that the ssid in question is "sstc" with mac address "00:1f:5b:87:27:47"? Which is the SB mac? I see two 00:04:20:05:61:f1 and 00:04:20:05:79:bf. This is what I found so far: Packet 198: Probe Response from AP with rates: 1.0(B) 2.0(B) 5.5(B) 11.0(B) 6.0 9.0 12.0 18.0 Packet 201: Beacon where AP announces rates of: 1.0(B) 2.0(B) 5.5(B) 11.0(B) 6.0(B) 9.0 12.0(B) 18.0 Packet 209: Association Request with rates: 1.0(B) 2.0(B) 5.5(B) 11.0(B) Packet 211: Association Response, which is negative due to client not supporting all of the data rates Exact error text: Association denied due to requesting station not supporting all of the datarates in the BSSBasicServiceSet Parameter (0x0012) One thing that looks suspicious to me is the difference in packet 198 and 201 regarding data rates (6.0 and 12.0) and the other is if it is possible to set the AP to be less restrictive about what data rates need to be supported.
I have encountered exacltly thte same problems. I have been in contact with Julius and sent him the following details: Dear Sirs, I am using an Apple AirPort Time Capsule as Base Station. I have done a factory reset on my Squeezebox. My Squeezebox recognizes my SSID (and gives 65% signal strength in Current Settings) but when I enter my WPA2 password I get the message after 30 secs that it cannot connect to my wireless network. I have had the system working previously with no problems using a Linksys WRT300N Wireless Router. I have tried using both the ascii version of my WPA2 password and the HEX version on the Squeezebox but to no avail. MAC address filtering is switched off on my base station. Can you help please? Best Regards, Dave Yesterday I tried connecting the TC and SB v3 using an Ethernet cable. This worked fine - no problems. Thanks, Dave
(In reply to comment #15) > I am correct in assuming that the ssid in question is "sstc" with mac address > "00:1f:5b:87:27:47"? Which is the SB mac? I see two 00:04:20:05:61:f1 and > 00:04:20:05:79:bf. You are correct that the Time Capsule ssid is "sstc" with a mac of "00:1f:5b:87:27:47" however the SB3 is 00:04:20:06:ed:df. Do you not see that one in the log? > One thing that looks suspicious to me is the difference in packet 198 and 201 > regarding data rates (6.0 and 12.0) and the other is if it is possible to set > the AP to be less restrictive about what data rates need to be supported. I'm not sure about data rates but I will attach some screen shots of the Time Capsule configuration screens for you to peruse.
Created attachment 3062 [details] Time Capsule wireless configuration screen
Created attachment 3063 [details] Time Capsule wireless options screen
Created attachment 3064 [details] Time Capsule wireless radio mode screen
Created attachment 3065 [details] Time Capsule wireless security screen
I can only see 00:04:20:05:61:f1 and 00:04:20:05:79:bf trying to associate with the AP and both are denied because of not supported rates. 00:04:20:06:ed:df never tries to associate, but instead tries to authenticate to 00:00:00:00:00:00 which seems very odd. Could you try again to catch a trace, please, maybe do a factory reset of the SB3 first. Also have you tried with option '802.11b only' or '802.11b/g compatible'?
(In reply to comment #22) > Could you try again to catch a trace, please, maybe do a factory reset of the > SB3 first. Sure, no problem. I will attach the logs first chance I get. > Also have you tried with option '802.11b only' or '802.11b/g compatible'? I am pretty sure I have tried with all radio modes available without success. Would a WiFi capture for each radio mode help?
(In reply to comment #23) > (In reply to comment #22) > > Could you try again to catch a trace, please, maybe do a factory reset of the > > SB3 first. > > Sure, no problem. I will attach the logs first chance I get. > > > Also have you tried with option '802.11b only' or '802.11b/g compatible'? > > I am pretty sure I have tried with all radio modes available without success. > Would a WiFi capture for each radio mode help? > Hey I have the same bug with my Timecapsule SB3 can not connect wireless - connect times out. I connects painless wired to Timecapsule. I have upgraded SB hardware to version 7.0
Created attachment 3087 [details] 4 captures
I found that holding the control key while using the radio mode dropdown gives you the full list including "b only" and "g only". Neither one work but there it is.
*** BGNchannel6, BGonlychannel6, Gonlychannel6: - 00:04:20:06:ed:df (SB) sends a probe request -- supported rates: 1.0 2.0 5.5 11.0 -- extended rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 - 00:01:5b:87:27:47 (TC) sends a probe response -- supported rates: 1.0(B) 2.0(B) 5.5(B) 11.0(B) 6.0 9.0 12.0 18.0 -- extended rates: 24.0 36.0 48.0 54.0 - 00:04:20:06:ed:df tries to authenticate with destination mac 00:00:00:00:00:00 and fails *** Bonlychannel6: - 00:04:20:06:ed:df (SB) sends a probe request -- supported rates: 1.0 2.0 5.5 11.0 -- extended rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 - 00:01:5b:87:27:47 (TC) sends a probe response -- supported rates: 1.0(B) 2.0(B) 5.5(B) 11.0(B) - 00:04:20:06:ed:df tries to authenticate with destination mac 00:00:00:00:00:00 and fails
I've got one at home now too, and I can confirm SB3 + SBR cannot connect to it. I'm using the Time Capsule as a pure wireless AP (bridge mode), not a router/dhcp server, so this problem isn't dhcp or routing related. My dhcp and routing setup is unchanged (all linux-based), I just replaced my old bridge-mode device with the Time Capsule. I have an SBR connected directly to one of the ethernet ports on the TC and that works fine too. It's just the wifi connectivity for SB3/SBR that fails. I've played with all kinds of settings, including all of the available 2.4Ghz options when alt-clicking the Radio Mode selection. There's one guy on the Apple forums who claims to have an SB3 connected to TC wirelessly just fine - he's the only positive report I've heard anywhere. I've sent that guy an email to try to get some details out of him. If anyone has any suggestions for getting some more advanced debugging going, I'm ready and able to do it :) Felix: the TC has two mac addresses, one for the wireless and one for the wired side. Is there any chance it's trying to make the device auth against the wired-side mac instead of the wireless mac, leading to the auth request to 00:00:00:00:00:00? -- Brandon
Steven: Just a thought, are you selecting the SSID from the list on SB3 or entering it manually? Brandon: Thanks for the offer to help. Do you have wireless sniffing capability? Not sure, but maybe it would help to get a clean sniff as the ones from MV tend to have a lot of noise in them. Thanks.
(In reply to comment #29) > Steven: Just a thought, are you selecting the SSID from the list on SB3 or > entering it manually? I am selecting the SSID from the list. In fact Ross and I took those last captures by driving out to an empty parking lot get away from the all the rays broadcasting in the office :) If the captures are still too noisy we can drive farther away or perhaps build a Faraday cage.
Just an FYI on this bug as I didn't see anyone using a Duet. Same issues apply as listed below with the exception that I could not connect to the receiver using wired or wireless. Strangely the Controller connects fine to the Time Capsule, but the receiver fails on trying to connect. I was able to create a WDS network using my Airport Extreme and then connect the receiver but network latency was awful. I'm now back to my Airport Extreme and the Time Capsule is sitting and gathering dust until some wise soul finds a solution for this issue.
I have exactly the same problems with my Squeeze box and my time capsule. It works wired ( via an ethernet switch ). In the end I have had to connect another wireless router to the switch and connect that way.
New update for TC from Apple today--does it help anyone? Janine (In reply to comment #32) > I have exactly the same problems with my Squeeze box and my time capsule. It > works wired ( via an ethernet switch ). In the end I have had to connect > another wireless router to the switch and connect that way. >
(In reply to comment #33) > New update for TC from Apple today--does it help anyone? > > Janine > Nope, they must have been working on unrelated issues. I updated my TC firmware to 7.3.1 last night, and retested three scenarios (which aren't as exhaustive as my initial test, but should cover it): b/g/n mode + WPA2 g-only mode + WPA/WPA2 b/g-mode + WPA/WPA2 b-only mode + no security No luck :/
(In reply to comment #34) > (In reply to comment #33) > > New update for TC from Apple today--does it help anyone? > > > > Janine > > > > Nope, they must have been working on unrelated issues. I updated my TC > firmware to 7.3.1 last night, and retested three scenarios (which aren't as > exhaustive as my initial test, but should cover it): > > b/g/n mode + WPA2 > g-only mode + WPA/WPA2 > b/g-mode + WPA/WPA2 > b-only mode + no security > > No luck :/ > I also tried the squeeze box with the new Airport Express 802.11 n and it has exactly the same issues as the Time Capsule.
I'm able to connect wired to my Time Capsule, but wireless will not work.
Fixed in SB fw 88, TR fw 37, SBR fw 23
Hi Felix, Will it be fixed in Transporter firmware 40? Thanks, Xavier
(In reply to comment #37) > Fixed in SB fw 88, TR fw 37, SBR fw 23 Are you guys supportpeople? I thought it was fixed but it is not. The current firmwareversion is currently 86. How long will i have to wait
Tested with Transporter, Receiver and Classic. This firmware should be available with the nightly starting on 04-05-2008 available at http://slimdevices.com/dev_nightly.html
I'm afraid there are still problems with Leopard 10.5.2 both on iMac and MB Air (Tiger works ok though..) Ref. my post at http://tinyurl.com/59cxdp - I am able to access my Squeezenetwork favourites, but switching to Squeezebox from the default web interface just doesn't switch. but stays in SN.
Gerald: this bug is closed and not going to get any more attention. Can you file a new bug with the details for your other problem? Thanks.
This bug has been fixed in the latest release 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.