No need to be left behind. They can already release WiFi 9 products. /s

They must. Otherwise it cannot be tested within the labs.

And producing chips before a standard is finalized is usually no problem at all: there are gates within the standardization process where the will be no more changes that are relevant for the silicon.

These 802.11n-draft APs were a singular fuckup regarding this.

They've been doing this since the dawn of wifi pretty much. I distinctly remember seeing "802.11 draft n" being printed an all the hot new and faster wifi cards back in the day.

Haven't had any wifi problems since. To the point I don't remember what wifi standard my home is on :)

Too bad they may or may not have given up on the cloud connectivity requirement. I've been told (even on here) they have, but I've also been told that you can disable it after setup instead of setting up without any stinking cloud.

Say, did Ubiquity stuff work during the AWS outage?

For wifi I have been using ASUS's AI Mesh. Not that impressed tbh so looking to change to something else in the next upgrade cycle.

I have "enterprise" TP-Link equipment for my house which I bought 3 years ago now and am very happy with it, in particular I'm using:

- 4x EAP245 Access Points

- 1x SG3428 Switch (the APs came with PoE injectors and I wanted a fan-less switch, hence why the switch is not PoE enabled)

I rent out a room on my property and have my tenant on a separate VLAN to the main house. I also have my IoT devices on a separate VLAN.

I use a generic PC with pfSense as my "router".

My only complaint is that their Omada Controller software doesn't want to run as a Windows Service (I'm not interested in trying to manage a Linux box). Fortunately, it's not required at all, but is useful for centralized configuration management and facilitation of handover of WiFi clients between APs.

Before I moved into my current large-ish place, I used "cheap" ISP supplied TP-Link routers with WiFi, and aside from limited speed capabilities, were 100% reliable for me, in particular I used the following two models:

- TL-WR840N

- Archer C20.

I also use a few cheap (but again fully reliable) 5 port and 8 port TP-Link 1GB/s switches, for example under my desk in my office to allow both my laptop and desktop to share the single CAT6 cable to the room.

Before buying the "enterprise" TP-Link equipment I considered Ubiquiti, but the TP-Link stuff was less expensive, I liked the controller being optional and considering all my past TP-Link equipment's reliability was a non-issue, I was happy "to take a risk".

Ubiquity stuff was giving me constant buffer bloat issues and it was a pain to do basic configuration for. Just too many options.

TP-LInk generally works just fine as long as the WiFi channel is clear.

Infrastructure side handovers are great for load balancing though, for enterprise networks with very high client density.

“Now More Reliable!” in a spiky red circle alongside the unchanged highly theoretical bandwidth numbers?