I finally got to the point to open another thread on this I recently often thought about. I have a system with several cAP-ACs running ROS 7.15.3 stable but not with the standard wireless drivers, more with the wifi-qcom-ac driver. I switched over to have WPA3 encryption and FT.
As I faced many issues with not getting FT set up to work with android phones properly I disabled the WPA3 encryption and after still not facing any improvements in the transitions (or getting “roamed” log msgs) I don’t see any advantage of the qcom-ac driver.
Rather I face the immense disadvantage of configuring vlans manually on each cAP.
What are your opinions on this? Is it worth switching back to the old wireless driver which instead worked very reliably? When not using WPA3 and FT there should be no other constraints.
The only think that stops me from doing this is that I’m not sure whether or when MT will maybe abandon the old driver.
Without a doubt…use the wifi-qcom-ac driver. I have zero problems with Android and FT (as well as WPA3, I just disabled WPA3 for the time being). It all comes to configuration, you might want to give us the opportunity to help you get it to work.
/export show-sensitive file=anynameyoulike
Remove serial and any other private info and post in between code tags by using the </> button.
Currently I have disabled WPA3 and didn’t care about FT.
Actually the FT and WPA3 would only be relevant for the “lan.robtor.de” network, and maybe for the fon network.
I’m sticking with the legacy wireless drivers for this very reason. Really do need to either replace CAPsMAN with a better controller system or sort out the driver.
Had an older install that I haven’t been able to replace the wireless.
The router had to be replaced. They also finally got a public IP. I wanted to use Wireguard and updated all the way up to current firmware …
Oops.
Still have cap ACs there
Updated to current firmware and just waited…
But the next morning I was getting complaints again about things not connecting.
Check caps-man and I see connected devices.
With all the yelling I didn’t bother… Disable all the radios for 10 seconds. Bring them back up. Everything connects again. Looks exactly the same to me. Then I moved over to Interfaces and actually saw traffic going out
“Wait .. whatever you did fixed it.”
Ugg…
Set a scheduler to disable the radios and renewable them every morning right before they open.
Which version of ROS do you run? I never had such issues with qcom-ac drivers. As at the beginning of this thread I had problems only with FT and WPA3.
And to not let this topic drift away, did anyone find some misconfiguration from me? Maybe with the connect-priority?
In general when having WPA3 enabled my phones do not roam between the APs. They stay connected even when having really poor connectivity. Ans switch over really late or even when re-enabling wifi on the phones.
Yeah, I don’t have such issues either with wifi-qcom-ac. But I do not have to deal with or support “enterprise” hardware. I have some devices that do not support FT (like an old ipad mini 2 or 3 with some iOS 9 or something) or devices that do not support enforced 802.11w. But no one sane would enforce either one in a “enterprise” environment either way. And I did not have a single case in over 6 months of wifi-qcom-ac where I had to “reboot the AP” so a client can connect again. Sounds more like a legend to be honest. But it may really have happened.
But gotsprings said: “was still needed”. So maybe this particular setup needed this daily reboots ever since. Even with legacy wireless. We don’t know and won’t find out. Let us know when you finally replaced the caps with Cambium gear.
With the old driver the CAPs would stop accepting clients. No amount of futzing fixed it.
Rebooting worked.
But I found years ago when caps would stop passing traffic to a printer… I could disable the radio and reenable it. That would reconnect the printer and allow other clients on the 2.4 again.
With this install as its been there for years… I put in a “blink radios” schedule. Everyday, before the staff comes in… all radios blink off and back on. Not a power cycle.
Updated to ACv2 drivers and turned off the blink. 2 days later getting the calls that nothing connects. Hit the blink button… everything got back on line.
Yes I have told them that when they move… those radios are not coming with them.
