Client disconnections after 200.19.7.11.283 upgrade, disabling "force DHCP" seems to fix it

[seanm]

We have a Ruckus R750 running Unleashed.

Everything was fine with 200.18.7.101.244, then we updated to 200.19.7.11.283 and many people were reporting disconnections and/or unstable connections.

Turning the "force DHCP" option from ON to OFF seems to have fixed it.

Anyone else have this same issue?

Sean

[username]

only device i have tested really. I have heard complaints from other users alluding to the same problems though during the 200.19 test I did. 

[sanjay_kumar]

Thank you for the update, checking with specific model might take some time.
Is there any possibility to upgrade to 200.19 MR so that we can check with other devices.
We can also gather logs while testing.

[kiler129]

Hoping the new release solves the issue, I wanted to add this isn't only occurring with iOS and ChromeOS. I observed the "Force DHCP" being enabled on IoT network (to deliberately force misbehaving devices to re-connect) also causes issues with many devices losing connectivity and never re-establishing it. Based on general observation, it happens both with RADIUS-authenticated devices, as well as ones using dynamic PSK. The most affected devices are ones using Atheros chipset.

[sanjay_kumar]

Hi All,

Is anyone else facing disconnection issue with Android or Apple devices after upgrading to 200.19 MR ?
If yes, we can connect over a call to gather the necessary logs.