topic Re: Looking for 200.10.10.5.229 Feedback in Unleashed

Looking for 200.10.10.5.229 Feedback

daniel_m — Tue, 01 Jun 2021 16:24:10 GMT

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.

Re: Looking for 200.10.10.5.229 Feedback

raymond_lau_740 — Tue, 01 Jun 2021 16:27:23 GMT

It only came out yesterday, but as I was upgrading for frag attack anyway (which was the patch immediately before this update), I decided to go to 200.10.

I haven't seen any issues but it's only been ~16 hrs for me.

Re: Looking for 200.10.10.5.229 Feedback

george_wang_cdz — Tue, 01 Jun 2021 17:54:03 GMT

Just upgraded my R610 (single AP) to 200.10.10.5.229, the procedure is smooth.

After it finished updating, my first impression is my Google Pixel 4 XL phone with Android 12 beta 1 that used to has issue to connect to WPA2/WPA3 mixed authentication, it now quickly get connected without re-enter passphrase every time.

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 20:58:05 GMT

I upgraded my small installation at home (2 R650s, ca. 40 clients), no issues. I believe to see less "poor" connections.

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 22:04:59 GMT

Actually, I am afraid I have to correct myself: Both iPad Pro's I have cannot connect to R650s at 200.10.10.5.229. I reverted to an earlier version and it works again. All other devices in the house worked fine. There seems to be an issue here, both iPad have 802.11ax (these are the only ax devices I have).

Re: Looking for 200.10.10.5.229 Feedback

daniel_m — Tue, 01 Jun 2021 22:07:25 GMT

Thanks for the update. Are you using WPA3 anywhere?

Re: Looking for 200.10.10.5.229 Feedback

raymond_lau_740 — Tue, 01 Jun 2021 22:08:34 GMT

Interesting -- the iPads here are ac, but the iPhones are both ac and ax.... the iPhones have no problems here. This is using a pure WPA3 SSID.

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 22:11:50 GMT

The AP was configured WPA2/WPA3-Mixed. My daughters iPhone worked, but it is 2 years old, so no ax.

Re: Looking for 200.10.10.5.229 Feedback

daniel_m — Tue, 01 Jun 2021 22:14:51 GMT

@joachim_posegga In reviewing the Release Notes, the following is a Known issue:

iOS devices that support 802.11r and WPA3 cannot associate to open-WPA23-mixed+802.11r WLAN.

Re: Looking for 200.10.10.5.229 Feedback

raymond_lau_740 — Tue, 01 Jun 2021 22:15:29 GMT

Maybe this known issue? I don't use mixed.

UN-5000

iOS devices that support 802.11r and WPA3 cannot associate to open-WPA23-mixed+802.11r WLAN.

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 22:18:18 GMT

Good point. I will try 200.10.10.5.229 with 802.11r disabled and come back.

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 22:44:34 GMT

Yep, that's it: I disabled 802.11r and iPads are happy again.

Re: Looking for 200.10.10.5.229 Feedback

daniel_m — Tue, 01 Jun 2021 23:01:21 GMT

@joachim_posegga I guess let us know if you run into any side effects as a result of disabling 11r. I understand it is supposed to help speed up roaming between APs, but I'm not certain how relevant it is today.

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 23:10:48 GMT

Well, I guess it's indeed not very relevant, since applications can handle network interruptions these days. Unfortunately I am not a good Guinea Pig with only 2 APs :-), but I will report observations.

Re: Looking for 200.10.10.5.229 Feedback

raymond_lau_740 — Tue, 01 Jun 2021 23:22:36 GMT

802.11r speeds up reauthentication. When a client moves between APs, it needs to re-authenticate. 802.11r provides preauthorized key caching to reduce the amount of protocol handshakes upon reauthentication.

The benefit is much more noticeable on 802.11x (e.g. radius) authentication than for a fixed password key. Also, it is more relevant for real time traffic (Voice calling? Zoom?).

Re: Looking for 200.10.10.5.229 Feedback

jp — Tue, 01 Jun 2021 23:32:31 GMT

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

Re: Looking for 200.10.10.5.229 Feedback

veno77 — Thu, 10 Jun 2021 07:31:39 GMT

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

Re: Looking for 200.10.10.5.229 Feedback

louis — Fri, 11 Jun 2021 22:22:49 GMT

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...

Re: Looking for 200.10.10.5.229 Feedback

sam_singh — Mon, 14 Jun 2021 21:49:06 GMT

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

Re: Looking for 200.10.10.5.229 Feedback

veno77 — Tue, 15 Jun 2021 13:56:32 GMT

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.