jpblanch75  Master Member

Any update on this?

Can you send me that beta firmware to test? I've been part of the beta program for a while.

Unfortunately the feature is only half baked. If there isn't another AP stronger this feature can cause you to totally be disconnected from it.

Again: When using WPA3, Roaming is not working as it is supposed to using PMKID. I will drop wifi before grabbing a new Access Point.

I really don't understand what you are saying here. I've used WPA3 and WPA2. They all produce the same results. So you are telling me that if I combine 5Ghz and 6Ghz on the same SSID I'll get 802.11be for both 5 and 6 Ghz? This is odd after yopu told be this above: "Additionally, in our second testing, the SSID…

An update on this would be great!

It has been a few days, an update would be great!

I'd say make me more active in Hardware Beta testing would be best for me. =)

When I was looking at the list I wasn't seeing what you attached. Maybe it was holding on to old data but what I said stands true. I can only connect to Wi-Fi 7 on 6ghz...Originally I couldn't but then it started to work. I have not been able to connect to Wi-Fi 7 at 5ghz or 2.4ghz.

Only 2 of my 3 access points are capable of 802.11be. When any of those Pixel 9 devices are connected to the NWA50ax Pro they won't show that they are 802.11be capable. That's why you are seeing it change in my client list. Also, if you disable 6ghz in that ssid you use I bet you stop connecting at 802.11be.

I told you above in the first post and title combination. Am I not being clear? When using WPA3 security, none of my 802.11r capable devices show that capability in the client list.

I'm using Nebula, latest firmware and the client list. What made me look was while walking between access points my phone would switch to cellular then back to Wi-Fi instead of I'm jumping APs. Using WPA2 it works fine and shows 802.11r in the client list.

What settings are different because I have tried many different settings to try and resolve this.

I've been getting them as well. I feel like I had them often when in Stand Alone mode. After switching back to Nebula I still got them but less frequent. I noticed the it was going into limited power mode as well and tuning off WLANs. I don't know why but I enabled the Override Full Power setting and I haven't had any…

This isn't working. I get the following error every time. The capture session could not be initiated on capture device "rpcap://192.168.5.6:2002/miireg". (miireg: That device is not up) I will say that only getting one reply from you while I'm sleeping every 24+ hours is painful.