Quote:
Originally Posted by woob
What kind of WiFi6 issues have you had? I'm putting in Ubiquity U6 Pros at one of my field offices (about 8 APs) and your post has me a bit concerned. I haven't done any WiFi6 deployments yet.
|
The biggest and main issues I had were devices that had "company security settings" on them. The devices would think they're connected, but basically wouldn't get any transmission of data. I could do certain things to get them on and get data transmission (mainly restarting my whole system), then 24-36 hours later (or if they left wifi range and returned), the devices would do this #### all over again. This was happening to devices that weren't aware wifi 6 existed. I'd have to reset the system 2-3 times in a row to get all the free in-law laptops and phones (5-6 devices that they got through their work) to connect simultaneously and be able to receive and transmit data.
"Lol, DoubleF, your expensive set up doesn't work well."
"NO! Your ####ty company device settings don't work well! I have zero issues until your piece of #### devices show up!" (in my head)
Once I got another AP that did not have Wifi 6, I could get the devices on and then they'd be able to migrate over to the Wifi 6 AP and work as normal. But now I'm getting interference that I don't have time to diagnose and address. Same thing happened to one of my wife's computer that she got from work, but because it is not a device that leaves wifi range and it's a single device, it's not as big of a deal to reset the system once every few months to get it on. My inlaws have freaking like 5-6 of them and they taken them out of range all the time, so we'd be literally resetting the system like 4-6 times a day.
I'll take the 20-30% hit in speeds (still around 120-320 instead of 200+ everywhere) rather than having to debug or reset my entire system every time some "company security settings" device enters my household though.
TBH, now that I think of it, maybe I should just turn off or disable that non-wifi 6 AP and activate that AP only when those devices enter my home. That might be the easy "fix" without more hours of research. Based on what I understood, it was straight up some bug. But IMO, it's probably more some ####ing setting that those managed devices had that was causing the issue (and I cannot access those settings to fix it).