> While some draft specifications could be released in 2027, the official Wi-Fi 8 standard is projected to be finalized only in mid-2028. Commercial products that officially support the new standard are not expected to reach the market until late 2028 at the earliest.
I bet companies will release WiFi 8 products even when it's still a draft, just as they did with WiFI 7.
I upgraded my home setup to WiFi 7 a few weeks ago, and after being a WiFi hater for so long, was actually surprised at how much better it was over my previous experiences with WiFi. With MLO clients get 2-3ms latency with 2.5Gbit links, I'm all for WiFi 8 trying to reduce the latency further, I don't need more speed.
> I bet companies will release WiFi 8 products even when it's still a draft, just as they did with WiFI 7.
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.
Similar transition for me. Basic dual AP setup that I took from first gen UAPs (wifi 4) to U7 Pro. I think I have only one client (a Lenovo laptop) that connects with wifi 7, but even the wifi 6 devices are screamers now; my phone can get 600mbps symmetric with line of sight or 200-300mbps from two floors away. Just bonkers.
I very much doubt it wills make any difference right now, especially in a home environment where it’s only a handful of clients and minimal real congestion.
I got the pros as a vanity move to be 6GHz ready but truthfully there’s zero reason for it.
This is part of what opening up the 6 GHz was about.
But there are also provisions in newer standards like Target Wake Time: the client can be told to sleep for a while, not using radio spectrum (and also saving battery).
I recently torrented a movie on a airport wifi while waiting for a plane and it worked so well, even when walking around the airport to the plane. I was impressed.
Without a personal opinion one way or the other, I would assume the gripe is with congesting the public network as opposed to the choice of public domain documentaries you downloaded.
> I bet companies will release WiFi 8 products even when it's still a draft, just as they did with WiFI 7.
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.
You can already make a MAP network, and any modern client will automatically hop between APs pretty fast, based on which one has the strongest signal. There's a common misconception that devices will cling to one AP while better ones are available, which hasn't been true in many years now from my experience.
Infrastructure side handovers are great for load balancing though, for enterprise networks with very high client density.
I have a lot of low bandwidth devices that love to connect to a router further away and congest it. Makes the devices I actually care around run much slower.
The only solution is restarting my network one-by-one so they have a better chance of getting the right device.
They seem to suffer from all the same issues of out-of-date unsupported software releases that all the other consumer AP manufacturers have. But I haven't read anything which suggests more deliberate backdoors. Perhaps another HNer has. Personally, I've always installed OpenWRT for the superior support and updated packages, and TP-Link devices have been reliable platforms for that.
If you want reliable Wifi at home, get yourself Ubiquity access points and throw away TP-Link. The issue is not the protocol. After many years of unplugging and plugging back in my TP-link router I know that they are cursed.
I think it's more a case of don't use cheap consumer grade hardware in any kind of remotely demanding scenario.
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".
It's tough. On one hand side, TP-Link has some weird issues. On the other, I spent a while debugging an issue with their engineers and they seem to actually care to improve things. Maybe the lower price is worth it sometimes.
Or better yet, Aruba Instant On. Enterprise hardware for SOHO money, truly plug and play, rock solid, no tinkering involved (which can be both good and bad depending on one's goals).
Can relate. I went through various consumer ish access points until I got tired of it and splurged on an Ubiquiti.
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?
As far as I know devices like Access Points only need the Controller to be configured or monitored. Once they are configured they work completely without it.
What does that mean, that the controller won't work without a cloud account? :)
It doesn't really matter which part in the chain requires the stinking cloud as long as they sneak it in somewhere.
Speaking of which, I just bought a Razer mouse again because I've read they gave up on the login requirement for configuring your blinkenlights. But they didn't. They invented a 'guest login' instead.
You can run the controller locally or from the cloud. When it is running locally you have the option to tunnel to it through the cloud. It runs completely locally.
AFAICT, the controller is needed for fast roaming of clients.
I have the UAP-AC-LR and if you only need basic AP functionality you can even configure it from the phone (no cloud). 99% sure no cloud stuff is needed when self-hosting the controller. May have changed since then, though.
Yes you can just not enable it. It is disabled by default. Maybe if you register everything through the app on your phone you need to be a bit careful. I think that makes it easy to enable the cloud tunnelling.
Indeed. You need the controller running first before you can configure AP, Switches, and gateways.
Better yet, buy actual enterprise gear even if it's a generation behind. You can find decent Aruba, Ruckus and Cisco kit on eBay going for decent prices.
Anecdote time - I've had their BE550 Wifi 7 router for over a year now and it's been rock solid. Easily does 2Gbps over wifi, never had to reset it once despite having 40+ devices connected to it all the time, the 4x 2.5Gbps ports are super useful.....it is one of their more expensive devices so maybe that's why, but generally it's been very very solid.
I own two consumer-grade Deco XE75 access points which I purchased several years ago as the most cost-effective 6E compatible access points available. They have proven to be exceptionally reliable.
Although I have previously encountered significant issues with WiFi, I now do not see a need to replace these devices despite the availability of WiFi 7.
My deco seems to be really poor at picking a channel at boot up. When I have performance issues running the optimizer almost always moves it to a different channel and solves my issues.
I just ran the optimiser after reading your post and it changed the 2.4GHz channel - I think the main reason I've been so happy is that the laptops and smartphones I primarily use support 6GHz where there is no interference and channel selection doesn't matter.
Seems to me its mostly a version focussed on the enterprise, just like wifi 6 was. I suspect many consumers will just skip it like they did wifi 6 as it brings very little for them. Wifi 7 is a big jump from wifi 5 (and 6) in performance but its still not complete, way too many devices that only support dual band and not supporting the various forms of MLO properly. Still no open source firmwares supporting it either.
Are there any such routers? And even if there are, are there any clients? The last 4x4 MIMO Wi-Fi client I can remember was the Asus PCE-AC88, a Wi-Fi 5 NIC from 2016.
I bet companies will release WiFi 8 products even when it's still a draft, just as they did with WiFI 7.
I upgraded my home setup to WiFi 7 a few weeks ago, and after being a WiFi hater for so long, was actually surprised at how much better it was over my previous experiences with WiFi. With MLO clients get 2-3ms latency with 2.5Gbit links, I'm all for WiFi 8 trying to reduce the latency further, I don't need more speed.