Go to main Forum page »
THE GAP BETWEEN theory and practice will never be wider than in the world of networking. And you will not find a finer example of this hard reality than in the rollout of Wi-Fi 7, the latest version of wireless networking from the Wi-Fi Alliance and IEEE.
A quick web search today turns up no end of stories from bloggers and journalists who breathlessly repeat the same promises of Wi-Fi 7: higher bandwidth, lower latency, and resilience to interference, with full backwards compatibility. This is the theory.
Today, the practice looks quite different, so much so I recommend hitting the snooze button for a year or two before upgrading your home Wi-Fi router or access points (AP).
There are three reasons for this:
This last point is important and a bit complex, so please bear with me.
Your IoT devices (short for Internet of Things), those Wi-Fi gadgets which have access to the internet, are often not easily updateable like a smartphone, tablet or a Mac/PC. The makers of many IoT devices, especially inexpensive ones, don’t spend the time and money needed to achieve Wi-Fi Alliance certification. That certification can help find the kinds of bugs which often show up when low-level Wi-Fi protocols change, and in Wi-Fi 7 those protocols changed a lot.
Today, the list of IoT devices which have access to the internet in our house would boggle the mind a decade ago: the dishwasher, the washer & dryer, our cars, a home power monitor, music speakers, smoke/CO detectors, a lighting controller, and a lawn irrigation controller. If all of these could be easily updated to use new Wi-Fi stacks, a technology transition like this would happen more quickly. Some companies will never update the code which powers Wi-Fi on their device.
Because of that, delivering backwards compatibility with this gaggle of things tends to fall most heavily on the companies which make Wi-Fi routers or APs. Those manufacturers have to implement wonky work-arounds to non-compliant or buggy Wi-Fi behavior from IoT devices. That kind of work takes far more time than writing code to a clear, definitive standard Wi-Fi specification.
Networking is hard, as my old boss used to say. But when you finally upgrade to a Wi-Fi 7 router or APs, there’s one thing you can do to make this transition easier and more likely to succeed if you–not your internet provider–control your network. Create a second, new Wi-Fi network. Move your modern/updateable phones and Macs/PCs to that and configure your old Wi-Fi network with legacy settings to maximize IoT compatibility. Keep that legacy IoT network on just 2.4 GHz or 2.4 GHz + 5 GHz and use only WPA2 security. That should signal your new router or AP to avoid doing anything which might rock the boat with an old client device. Meanwhile, on your new Wi-Fi network you can optimize for performance and the best security over new 6 GHz channels for devices that use fancy new Wi-Fi 7 features.
Wi-Fi 7 is a big, important step forward for the industry. And eventually it will make a real difference in the quality of customer experiences running over Wi-Fi networks. But delivering on that promise, without aggravation from interoperability issues involving older devices, will take the industry at least a year or two. In theory.
Interesting. I agree that late adoption of tech is best unless it’s for security purposes (e.g., passkeys, 2fa, etc.) I’ve avoided IoT, partly for security reasons and partly for not needing it. I can’t imagine why I would need remote access to things in my home.
Wi-Fi7 – what would I need the extra bandwidth or lower latency for—gaming? Currently use less than 100mbs internet and everything works fine. I just don’t have the use case for more network.
If WiFi 7 were only about performance I wouldn’t care much either but it is also about more resilient networking.
WiFi uses a shared medium of radio waves over public frequencies defined in each country. It is somewhat like the old “party lines” from the early days of Bell Telephone landlines. If you have neighbors nearby, you may occasionally interfere with their WiFi network or they with yours, which affects the quality of both networks. Streaming movies or TV shows can hiccup when that happens. Gamers may see a hangup or spike of latency. A Zoom or FaceTime or Teams call might freeze or glitch. Sometimes devices will drop off the network when it happens.
Wifi 7 has a gaggle of new channels at 6 GHz which will cut down on interference.
It also has a feature called multilink operation (MLO). While people focus first on that for its speed potential the real win will be in better resilience, once companies get the feature right.
Thank you, David, this was something new to me, but guessing Spouse knows about it. We are usually late adapters to technology, too frugal I guess. LOL! Chris
I guess I’m old, because I don’t think I need all this. I really don’t want my dishwasher talking to my lawn mower – only bad things could result. 🙂
😂
Interesting. I have so far avoided the IoT. My CCRC planned to install Google Nest thermostats. Not wanting a spy in the apartment I got them to install a dumb one instead for me. Equally, I have never bought a “smart” speaker, and have no problem turning on lights and writing shopping lists myself. My car is so old it doesn’t even have a backup camera, although I am concerned about a new one snooping on me. Since I have unlimited talk and data my phone is not on wifi.
I am pleased to hear that security may be improved, although the firm responsible for the internet at my CCRC is still using WPA2, despite complaints from a number of us.
WPA3 adoption is broader on new devices than older ones. And there may be some issues with WPA2/WPA3 transition mode for some devices. I can understand their hesitation at this moment. Hope that changes in 2025.
Thanks for this David. I definitely learned something.
David, thanks very much for this informative article. I was unaware that Wi-Fi 7 was that close. i’ll have to keep an eye out for this. I like the idea of parallel networks for different devices.