Looking for 200.10.10.5.229 Feedback

[daniel_m]

Hello community!

So is anyone here running 200.10.10.5.229 at home with great success?  I'm considering upgrading for the latest security fixes and to be on the "latest and greatest," but I am a bit worried about bringing too much "ruckus" to my home network in the form of incompatibilities due to too much IoT and other legacy wireless devices.

So, anyone here with a varied home network have "200.10.10.5.229" Just Work with no issues or have seen it improve things?

Cheers.

[jp]

In fact I just moved back to 802.11r and WPA2, since I have to continue to support WPA2 anyway for quite some time.

[veno77]

Hello, it was promised the setting to limit the 2.4ghz to 802.11n only will be back with 200.10 firmware but I could not find it in the web interface. Any ideas?

Thanks,

Veno

[louis]

Dynamic VLAN assignment by the dynamic PSK used to authenticate has been disabled in 200.10. There is no explanation anywhere I can find, but it wasn't a well documented feature in the first place. I had just finished rolling out a deployment of 8 R850s using this feature heavily, it was working so well, but now it is completely broken. Not sure what else to do but to downgrade to 200.9 and evaluate other vendors. Such a disappointment...

[sam_singh]

So far only had an issue at one of the sites that uses a wireless mesh using R750s.

This site was setup after a ton of wireless surveys and trial and errors to place the APs far enough from the root AP to have a solid mesh connection but at same time also maximize coverage per AP. All APs connect directly to the root AP for the most part. Everything has been solid on 200.9 and never had any mesh dropouts since going live with the setup. 

On 200.10 however with exactly the same setup and no physical changes, I can not get the wireless mesh APs to connect to the root AP. Mesh APs will try for a few minutes then start broadcasting the Recover.me-XXXXX ssid and then reboot after 15-20 minutes to try again and repeat the cycle. Either the mesh signal is now not strong enough possibly due to the addition of 2.4GHz or some mesh logic regarding the strength allowed to connect has been changed.

Randomly after a few hours the mesh would connect and the connection from the devices on the mesh APs would be stable but the mesh APs would randomly disconnect and not connect again for hours.

I only had the weekend to do this and didn't want to start moving the APs so I reverted back to 200.9 and everything just worked as before without issues.

I did not have time to test out mesh on 2.4 GHz either.

This is a very specific use case but heads up to anyone who is using wireless mesh thinking of upgrading to 200.10

[veno77]

Lastly I see frequently AP disconnects at home on 200.10 due to "Heartbeat Loss". This was quite stable on 200.9. I have R550 + 2 x R320 in my home network.