The only devices on wifi should be cell phones and laptops if they can't be plugged in. Everything else, including TVs, should be ethernet.
When I moved into my last house with roommates their network was gaaarbage cuz everything was running off the same router. The 2.4ghz congestion slowed the 5ghz connections because the router was having to deal with so much 2.4ghz noise.
A good way of thinking about it is that every 2.4ghz device you add onto a network will slow all the other devices by a small amount. This compounds as you add more devices. So those smart lights? Yeaaahh
I don't know why you're saying, a 2.4 GHz device should not interfere with 5 GHz channels unless it's somehow emits some harmonics, which would most definitely make i noncompliant with various FC standards. Or do you mean the modem was so crappy it couldn't deal with processing noisy 2.4 GHz channels at the same time as 5GHz ones? That might be true, but I would assume the modems would run completely different DSP chains on different asics, so this would be surprising.
Your assumption is sometimes incorrect as cheap devices can share some RF front end. Also apparently resource contention can also occur due to CPU, thermal, and memory issues.
https://chatgpt.com/share/68e9d2ee-01a4-8004-b27b-01e9083f7e... (Note that Prof is one "character" I have defined in the prompt customisation)
Or:
Please allow me to proffer the following retort: The answer to having a shitty, incapable router is to use one that is not shitty, and is capable.
(The routing-bits have no clue what RF spectrum is being utilized, and never have. They just deal with packets. The packets are all shaped the same way regardless of the physical interface on which they arrive, or which they are destined for.)
cycomanic knows stuff but their answer was basically contradicting chrneu, which nobody likes. It is counterintuitive to me (and I'm guessing cycomanic too) that the different bands should interact so much.
The AI answers passed my shit-detector... And I think it is the same as trying to be helpful but providing a search link in the past. Other HN users can make their own decision about reading the prompt or reply (although using links does make me wonder about cross account tracking and doxing myself).
It's all quite well-worded, and yet is still completely unrelated to what is being discussed.
Real people: "Hey, let's talk about networks!"
Eventually: "Cool, I like networks! Did you know that down is actually up, and up is actually down? In fact, I asked a sycophant bot to demonstrate this fiction with its wily words, and it did so with with wonderful articulation. Here's a link!"
Having tolerance towards this kind of make-believe anti-truth is not something that I would consider to be a healthy human function. Especially when this nonsense has deflected through a third party that is completely absent from the discourse and isolated from the context, such as a sycophant bot, and particularly so when there's an implied appeal to authority for that absent third party.
(I have no intention of considering whether this kind of action is deliberate or not. I simply recognize this move for how consistently successful it is at poisoning a discussion amongst a group of people.)
---
If you were to ask me, a person, the following question:
> "What is the most likely reason that a cheap router/AP would slow down servicing clients on 5GHz when also servicing clients on a congested 2.4GHz spectrum"
...then I would not have responded to that question with a single confidently-stated and presumptive answer, but instead by opening a dialogue.
And I would begin this dialogue by asking about the reasons that lead you to believe that this would ever be true in the first place.
(But that's not the path that was chosen here.)
As for the extracting of data, yes that happens on a massive scale. In free products that no one is forced to use. And I would argue that, by now, almost everyone should know that comes at a price, it's just not monetary to the user. At that point it's a choice people make and should be allowed to make.
If something is free, you're the product. But if it isn't free, you're paying to be the product.
A measured compromise would entail the meticulous profiling of the TV’s network traffic, followed by the imposition of complete blocking at the DNS level (via Pi-hole, NextDNS and alike) first, whilst blacklisting the outgoing CIDR's on the router itself at the same time.
This course of action shall not eliminate the privacy invasion risk in its entirety – for a mere firmware update may well redirect the TV traffic to novel hosts – yet it shall transform a reckless exposure into a calculated and therefore manageable risk.
As a broad concept: Ever since my last Sonos device [that they didn't deliberately brick] died, I don't have any even vaguely bandwidth-intensive devices left in my world that are 2.4GHz-only.
Whatever laptop I have this year prefers the 5GHz network, and has for 20 years. My phone, whatever it is today, does as well and has for 15 years. My CCwGTV Chromecast would also prefer hanging out on the 5GHz network if it weren't plugged into the $12 ethernet switch behind the TV.
Even things like the Google Home Mini speakers that I buy on the used market for $10 or $15 seem to prefer using 5GHz 802.11ac, and do so at a reasonably-quick (read: low-airtime) modulation rate.
The only time I spend with my phone or tablet or whatever on the singular 2.4GHz network I have is when I'm at the edge of what I can reach with my access points -- like, when I visit the neighbors or something, where range is more important than speed and 2.4GHz tends to go a wee bit further.
So the only things I have left in normal use that requires a 2.4GHz network are IoT things like smart plugs and light bulbs and other small stuff like my own little ESP/Pi Zero W projects that require so little bandwidth that the contention doesn't matter. (I mean... the ye olde Wii console and PSP handheld only do 2.4GHz, but they don't have much to talk about on the network anymore and never really did even in the best of times.)
It's difficult to imagine that others' wifi devices aren't in similar form, because there's just not much stuff left out there in the world that's both not IoT and that can't talk at 5GHz.
I can see some merit to having a separate IoT VLAN with its own SSID where that's appropriate (just to prevent their little IoT fingers from ever reaching out to the rest of the stuff on my LAN and discovering how insecure it may be), but that's a side-trip from your suggestion wherein the impetus is just logical isolation -- not spectral isolation.
So yes, of course: Build out a robust wireless network. Make it awesome -- and use it for stuff.
But unless I'm missing something, it sounds like building two separate-but-parallel 2.4GHz networks is just an exercise in solving a problem that hasn't really existed for a number of years.
My dev laptop is about 10 m (30 ft) away from the wifi access point, but goes through about 6 walls diagonally, due to some weird layout, and 2.4 GHz is way faster.
The house has some thick walls.
Same with phones. As soon as I'm in a different room, 2.4 GHz is faster. So I just keep things on 2.4.
Yeah, I've been planning to wire the house with Cat-6 into every room and add some access points. It's been on the backlog for 6 years..
My last house, which was rather small (by midwestern American standards, anyway) had some interior walls that were very good at blocking 5GHz transmissions. (I never took them apart to look, but I suspect that some of them had plaster with metal lath as one or more layers.)
I started with one access point downstairs at the front (because that's where the cable modem lived) but it didn't work so well upstairs, at the back (diagonally) in the room I was using as an office.
So I added another access point upstairs at the back and that fixed it: Wifi became solid-enough both upstairs and down, and also covered the entire back yard, and also worked great for the neighbors when they asked if they could borrow a cup of Internet. It took some literal gymnastics in some very weird normally-unseen spaces to accomplish that run, but it got done. :)
As an side: It's interesting that being blocked by walls is also part of what makes 5GHz wifi so speedy indoors (in addition to having a lot more spectrum to use), for many [not all] people. By being attenuated so well by walls, the co-channel interference from the neighbors is reduced rather dramatically. With neighbors nearby, the RF environment tends to be a lot quieter at 2.4GHz than at 5GHz.
---
Present-day house is a bit lucky: All of the thirsty tech is on the first floor, and it's very simple to get ethernet cables routed 'round in the basement (it's all utility space). I was able to find enough pre-existing holes in the floor (from old cable TV installs and also floor-mounted outlets that have been removed and covered) that getting ethernet to every useful area of every first-floor room with tech in it was a very simple ordeal that did not require a drill. (Yeah, that means that there's a wire poking up through the floor behind the desk I'm sitting at right now instead of a tidy RJ45 receptacle on a wall plate with a nice port designation label. I'm over it; it works perfectly and inertia is a hell of a drug.)
But I'm not completely "lucky." The present house has aluminum siding and low-E windows. It's a great house that is amazingly inexpensive to heat and cool for how old it is, but it has aluminum siding and low-E windows and approximates a somewhat-leaky Faraday cage.
Thus, my cell phone barely works indoors, but it works great outside. And wifi barely works outside on the porch (front or back, doesn't matter), and really not at all beyond the porch (but things like my phone think that it should work, which is problematic).
I worked around that well-enough for the detached garage and back yard area by adding another access point in the garage, configured as a wireless repeater. Its advantage is that it has antennas that are optimized to work well, instead of some that are optimized to be very small (like those inside my phone, or my laptop). It's identical to the one inside the house and gets OK signal to/from the main AP, which it has a visual line-of-sight to through a couple of windows.
As an impromptu solution made from stuff I already had leftover from the last place, it works. I'm not winning any speed records with that remote access point... but it seems to be reliable, and reliability is good.
(Maybe some day I'll actually get around to upgrading the electricity to the garage to support some easy-to-access rooftop solar and/or car charging and/or welding and/or something, and when that trenching happens I'll also drop in some single-mode fiber. A single run of pre-terminated fiber is very cheap to buy, the "optics" at the endpoints are very inexpensive, and it is very safe with its essentially-absolute electrical isolation. It feels like overkill, but it's also once and done.)
As I understand, low-E reflects solar thermal infrared radiation (3-8 microns, 37-100 THz), while letting through visible light. I don't think it affects 5 GHz radio waves very much.
But yeah, it would be very satisfying to finally wire the house with ethernet.
So true!
Other tips I’ve found useful:
Separate 2.4ghz network for only IoT devices. They tend to have terrible WiFi chipsets and use older WiFi standards. Slower speed = more airtime used for the same amount of data. This way the “slow” IoT devices don’t interfere with your faster devices which…
Faster devices such as laptops and phones belong on 5ghz only network, if you’re able to get enough coverage. Prefer wired backhaul and more access points, as you’re better off with a device talking on another channel to an ap closer to it rather than tieing up airtime with lots of retries to a far away ap (which impacts all the other clients also trying to talk to that ap)
WiFi is super solid at our house but it took some tweaking and wiring everything that doesn’t move.