Bugzilla – Bug 5454
Jive does not connect to non broadcasted SSID's
Last modified: 2009-06-01 10:12:56 UTC
Jive will not connect to a wireless Network when SSID broadcast is disabled. I have tested this with all types of encryption as well as no encryption. After selecting 'Other Networks' on the Wireless Networks menu, I typed in the SSID and the encryption and Jive returns an error,'Connection problem, There was a problem connecting to your wireless network.
This may not be the most appropriate place to ask, but would it be possible to improve the error messages? "Connection problem, There was a problem connecting to your wireless network." I could see this making technical support difficult. I recall that with WEP when the encryption fails we won't know, we'll only be able to understand there is a problem after a DHCP failure. But what about the other encryption means, or no encryption at all? Could we give more specific error messages such as "Wireless connection problem: Encryption key failure" or maybe for this particular case "Wireless connection problem: SSID not found"
Fixed in r497.
Moving from the old 'jive hardware' product to the new 'Squeezebox Controller' product.
I have in the past couple of weeks helped two customer's that were experiencing this issue, so I am reopening the bug. This happened with two different customers with two different routers. Customer one: RN Ticket #081207-000984 Router: Netgear WGT624v4 with latest FW from December The last time we spoke he had Controller FW r3191 and we ended up just setting up his Duet using Bridge Mode. We have yet to try r3476. Customer two: RN Ticket # 090106-003049 Router: Linksys WRT54G, not sure what firmware. We ran into this issue with the Controller FW at r3476. He ended up just enabling SSID broadcast and keeping it that way
Ross could you try to repro this? Thanks.
Created attachment 4573 [details] Controller log when connecting Duet to network with SSID broadcast disabled I can reproduce this with r3698, it fails and offers try again, self assign, or static IP. Trying again fails but self assigned works for me. Also Receiver light turns blue yet Controller fails to acknowledge Receiver has connected to the network. When this happens skip this step, then choose player and it will be there waiting to choose source, which works.
What access point did you test with, Ross?
I successfully tested against the following two routers, both with hidden SSIDs and WPA2. I do not have the two routers mentioned. Jive: 7.3 r3546 Netgear WNR3500v1 - V1.0.22_6.0.22NA (US version) Linksys WGT54G2 - 1.0.01 build 003, Mar. 26, 2008 (European version) Ross: What router did you try with? What SSID did you use? Any special characters?
Felix suggests that there's a possibility that this is a bug with some of the other data that must be entered if there's no SSID
Dean and Felix looked at the log and thing it may be a DHCP issue.
(In reply to comment #7) > What access point did you test with, Ross? > Sorry I meant to respond yesterday but wasn't quite finished with some testing. I was using a dd-wrt Linksys router. I've also reproduced this with a Netgear WGR614v7, strangely with this router it works sometimes. I'll get another log.
Created attachment 4603 [details] D Link DIR 555 Seems to have issues connecting to WPA or WPA2 encrypted networks with SSID broadcast disabled. For SSID's I'm using "aa" and "bb".
The log attached to comment #8 indicates a successful wireless connection, but a failure to get a DHCP address from the DHCP server. Ross: - Is the DHCP server turned on on that router? - If you try with the same router, same settings except no hidden SSID, does SBC connect and get an IP address every time?
(In reply to comment #13) > The log attached to comment #8 indicates a successful wireless connection, but > a failure to get a DHCP address from the DHCP server. > > Ross: > > - Is the DHCP server turned on on that router? > - If you try with the same router, same settings except no hidden SSID, does > SBC connect and get an IP address every time? > Yes DHCP is enabled, but I think you're right it has something to do with DHCP. I wonder if it is related to the problem I'm seeing on bug 9208. James also mentions Controller connectivity issues with 7.3 firmware.
Sorry I didn't answer your other question. Yes, enabling SSID broadcast with identical settings the Controller connects without issue. I'll do some more testing with older firmware today.
It worked for me today with DD-WRT on a WRT54G, and the D-Link DIR 655. I've contacted MWise, what I saw yesterday could have been related to Mountain View bug issues. I'm hoping we can reduce wireless noise to improve the QA test environment. Anoop, do our customers still mention this?
I have not had a customer with this problem in some time....Julius I think has some customers with this problem. Julius can you please update the bug with the status of your customers?
Ross, Is this working for you with production SC or a nightly? I have one customer that decided to just broadcast his ssid and another that doesn't want to do that and is setup using bridge mode. Is there anything specific you would like me to try with the customer that wants to hide his ssid?
(In reply to comment #18) > Is this working for you with production SC or a nightly? Yes, both. Have you tried it? If not please give it a try when you have time with your support test network you guys have setup, it should only take 15 minutes or so. > Is there anything specific you would like me to try with the customer that > wants to hide his ssid? Yes, first disable encryption and see if it works then. If that still doesn't work have him change his SSID to 'a' or something very very simple and easy to enter with Controller. I think you understand what I'm suggesting here.
I am going to do this test myself and have also contacted the customer that I was helping with this to try it again. Please wait for me to comment again before considering this bug closed.
Ping Anoop, have you had a chance to look at this? Ross seems to think it's better now.
Tested this today and everything worked for me. Tested with a Linksys WRT54Gv8 router with firmware v8.00.2 Test 1 SSID - Anoop (non broadcasted) Encryption - None Result - Connected fine. Test 2 SSID - Anoop (Non Broadcasted) Encryption - WEP 64 Result - Connected fine. Test 3 SSID - Anoop (Non Broadcasted) Encryption - WEP 128 Result - Connected fine. Test 4 SSID - Anoop (non Broadcasted) Encryption - WPA TKIP Result - Connected Fine. Test 5 SSID - Anoop (Non Broadcasted) Encryption - WPA 2 AES Result - Connected Fine. If anyone else is still seeing this issue please feel free to re open the bug. At that time please include all information regarding the router being used.