I feel people have only used badly configured crappy consumer APs on crappy laptops (without MIMO) and don't understand that wifi doesn't have to be slow and unreliable.
"A deep dive into why Wi-Fi kind of sucks": https://arstechnica.com/information-technology/2017/03/802-e...
Good routers can go over 100Mbps, easily, and I would never think that 'less' speed is 'okay' in a world where increased speeds are just a requirement of technology over time, and usage, of said technology.
Note that I said 800-1100Mbps.
> but the problem has always been variable latency
Symptom of crappy consumer equipment.
> Any kind of interfere from the dozens of other Wi-Fi networks in the area seems to have an effect
Well yeah, that is why I use 5GHz which doesn't penetrate walls very well so I don't get any interference.
The power used is very low. More power just means more interference. The bottleneck is the transmit power on the client, which is very low. More power on the AP just make everything louder. I've set up power level based on this document: https://support.apple.com/en-us/HT203068. Unfortunately only Apple documents this stuff, but works pretty well for everything AFAICT.
I don't have any special antennas. If you need to cover a large space with a single AP you might need one, but the best philosophy on 5GHz is to have many smaller APs.
All my APs are connected through ethernet (actually everything is PoE powered). I don't use any mesh stuff (although Mikrotik can be used in that configuration, I don't recommend it). All my APs are simple bridges, I don't use the Mikrotik tunnel stuff.
I don't use 802.11r because Mikrotik can't do it yet. I am not sure if anyone except Cisco can do it. I wish I had 802.11r, this is my Achilles' heel.
Everything works very well, but you get what you pay for. Mikrotik is really cheap compared to the real stuff out there, which means much less polish, more bugs, and no real documentation. If I were to do it again I might chose Unifi[2] instead. Don't get me wrong, this all works very well, but the level of polish is what you'd expect out of a GitHub project compared to some real commercial product. For example while you can set antenna gain in standalone AP mode, you can't do it in managed AP mode. Minor stuff like that.
I also run a RADIUS server and I create user accounts for all my wireless users (WPA2 Enterprise). At different locations users have the same credentials.
I use all kinds of clients (Linux/BSD/macOS), but the ones where I'm most interested in speed are the Macbooks.
Even with 802.11ad (that I don't have) there's a huge difference between having to plug in when you reach a "fast area" and not having to.
Going wired->wifi is like going desktop->laptop. I'll admit to being slow to go to both laptop and wifi years ago, but at least to me they're clearly superior.
service restart netif lagg0
And sometimes also service restart dhclient lagg0
But it might also be that I was to impatient and that it would have reconnected to wifi by itself if I gave it more time. How long does yours take to get back on wifi?Still I think it is awful.
I hear it is because the spectrum is jammed but I almost cannot believe it: I have a big garden and so have my neighbours.
What do you guys do to get fast, stable wireless?
The ubquiti has a spectrum survey mode that will tell you what sort of interference it sees on each channel. It takes 10's of minutes to run, and seems pretty thorough.
The real winning feature is that it is designed to be ceiling mounted, so I could place it in the center of my house, a few feet away from the nearest wall. There is also a mesh mode, where you buy more than one. If your house is big, and interference isn't the problem, that might help. I haven't tried it. They have newer / different models that do a better job of this than the UAP-Pro.
Later, I replaced my router with a pc engines apu2 running openbsd. Ubiquiti has a highly recommended cheap router (edgerouter lite) that works out of the box, if you aren't looking for a hobby project. People have gotten openbsd to run on it too.