jbl 500 authentics connection problems

[jp]

Hi pack ;-),

I ran into a problem with connecting a jbl 500 authentics speaker to Ruckus Unleashed (latest available version) on an R320: I can connect it to a WLAN set up without a password, but as soon as I set up WPA2, WPA3 or WPA2/3 combined it won't connect any more (the setup app simply stays with the message "connecting...". All attempts to reset the speaker, delete the WLAN, etc. failed.

Any ideas on this? My falback now is to have an open WLAN which just allows one client, but obviously this is far from an ideal solution. I also failed with setting up MAC access control, it won't connect either.

Cheers, Joachim.

[sanjay_kumar · Accepted solution]

Hi,

Could you try the below steps which was having similar issue with Sonos speaker>
We have the fix applied in later version, 200.15 is the last version supported for R320.

But try this workaround from CLI and check.

https://community.ruckuswireless.com/t5/RUCKUS-Support-for-Lennar-Homes/Cannot-connect-Sonos-wireles... 

[jp]

Sorry, I am late ;-( ... just didn't manage yet, but it's moving up on my priority list.

[jp]

... here we go: The R320 runs Unleashed 200.15.6.212.27. I set up a WLAN on it as below. You then connect with an iPhone to the WLAN (works with no problem), it finds the (resetted) JBL box but unfortulately the JBL box won't connect, the iPhone app says "cannot connect". I could not find anything useful in the R320 logs. I can connect the JBL box when I use an open WLAN without encryption.

Am I correct that the other WLAN parameters need to be editied via the CLI?

[Imran_ruckus]

Hi @jp 

Greetings!

Thank you for confirming the settings.

Could you please verify the following additional security parameters:

• Is Management Frame Protection (PMF) set to Disabled?

WLAN>>Edit>>Security>>Management Frame Protection

• Is the WLAN strictly WPA2-PSK (AES only) with no WPA3 or transition mode enabled?

On recent Unleashed 200.15 firmware builds, PMF or WPA3 transition mode can cause authentication failures with certain IoT devices even if WPA2 is selected.

If PMF Is Already Disabled:

Then the next likely steps you can check:

The JBL firmware itself has weak WPA2 implementation
Or firmware 200.15 tightened security behavior

At that point please test:

• Create a brand-new WLAN (not cloned)
• Simple SSID name (no spaces)
• Simple PSK
• No advanced features touched

If that fails too then we can consider:

• Testing on older Unleashed firmware
• Checking JBL firmware update

Let me know if that works.

Thank you again for your patience.

Best regards,
Imran Sanadi
RUCKUS | Community Support Forums

[jp]

Dear Imran, first of all thanks a lot for your prompt help - very much appreciated!!! 

All seems as suggested.  I guess by PMF you mean the CLI switch 80211w-pmf, but OKC / Opportunistic Key Caching appears neither in the GUI nor in the CLI documentation. Where can I find this switch?

Best, Joachim.

[sanjay_kumar · Accepted solution]

Hi,

Could you try the below steps which was having similar issue with Sonos speaker>
We have the fix applied in later version, 200.15 is the last version supported for R320.

But try this workaround from CLI and check.

https://community.ruckuswireless.com/t5/RUCKUS-Support-for-Lennar-Homes/Cannot-connect-Sonos-wireles...