Note to tech reports: do not EVER quote this metric as it is the most useless piece of information.
There is about 10m and a brick wall between my AP and my desk so yeah, a fancy new MCS that can theoretically deliver 25Gbps was just never gonna be useful to me.
Also I've worked on (other non-WiFi) 802.11 products where our competitive edge was all about interference motivation. Our competitors at trade shows would see the demos and say "that's fake, you guys are cheating". So I have the feeling that in general there might be alpha in more resilient wireless links.
Last year, I saw 1600 Mbit/s from the Internet at a normie's place with an ISP-provided router. Still have a cat 6 cable around the living room but haven't used it in the last 2 years. Not exactly wifi but I routinely get 600-800 Mbit on 5g networks in crowded areas.
Everything with an Ethernet port is wired, wifi is for phones and tablets only (a few UniFi WiFi 6 APS).
Works great!
Internet has never dropped for me while working, family loves the always working NAS streaming via wired Apple TV.
One of the core features (MLO) is currently mostly scam. APs/Clients negotiate the protocol (and it shows up in the status) but doesn't it to either increase robustness or bandwidth.
Also the driver quality is a huge mess.
(We tested it using the latest generation Cisco Enterprise gear but also with Prosumer stuff like Ubiquiti or TP-Link)
But honestly: we need WiFi-8. It finally brings infrastructure-controlled roaming which is super important for any VoIP service.
802.11 r/k/v exists
We basically miss all data (received stations/signal levels from both sides, Bit Rate errors, etc.) for making roaming decisions and then to softly steer them.
Enterprise WiFi is currently mostly "This is a list of APs you maybe can connect to.. have fun.. if you can connect we pre-seeded the AP with some crypto data, so it doesn't take ages to negotiate. Here's your (more or less friendly) disassoc.". It does somehow work for stationary setups - but as soon as you are mobile the quality hit the shitter.
Set your channels to 6/149/37 and the lag will probably vanish. Exactly because of this, I only run those channels, even across multiple APs.
In Europe, you may need to use 44 instead of 149.
There is currently no good way to keep AWDL off other than a script that just turns it off every 200ms, because of course Apple. Also, not always an option with work issued Macs.
Your router does not respond. Turn it off and on.
This comes close: https://www.getapp.com/all-software/a/breakdown/
Off topic, but that sounds sort of contradictory, or misleading at the very least.
Modern wifi is fast enough that using cables is often not required.
I would expect this crowd here to not make these mistakes as ofte. :-)
B is defacto for storage…
It’s also not really very common to talk about speeds that are 1.2Gbps, that’s a pretty unusually specific speed. I.e., I can buy 500Mbps, 1Gbps, or 2Gbps…not 1.2Gbps.
So when I first read your comment I totally thought you meant 150Mbps, which is just a whole different ball game of WiFi needs.
The 95th-percentile latency and packet-loss targets here seem much more meaningful than another 2x headline speed increase.
My only scepticism is how much of this survives real consumer hardware. Wi-Fi 6 had things like OFDMA that sounded great on paper, but support/implementation was pretty uneven.
I'm using 802.11ac and see no need for higher speeds.
Higher speeds automatically means less latency and that does matter, especially if you are into stuff like games where every millisecond matters.
There’s so much interference that the package dropout rate is around 40% at 2.4GHz usually.
In comparison, DECT has been flawless in the same space. Set and forget, just works. I always wondered if we could have a kind of DECT proxy on the LAN, and have the ERP application talk to that proxy using DECT... I mean, it's a few EANs and stuff, DECT could handle this easily.
Turns out the 2.4 GHz radio of my router had died (Fritzbox 7590, apparently a common issue), thus forcing 2.4 GHz-only clients to use those other APs.
Link: https://en.wikipedia.org/wiki/IEEE_802.11ah
The AP does not have visibility into what the client actually sees, and no, a coordinator that has knowledge what the APs see isn't that much better.
Imagine a situation with two APs and a client being in the middle of the two in a RF-impeded situation (i.e. your typical office building). AP1 may "hear" the client better (i.e. it gets a higher RSSI and SNR), but the client may reject it in favor of AP2 because the client sees a better signal coming from AP2 due to reflections, a powerful RF signal from a floor above interfering with the channel of AP1 or God knows what else.
RF is a weird world.
I do kind of want to play with this.