From my experience in IT, it’s almost always a local network issue in the end. That’s not to say, the user’s fault. But the distance a little education on home networking could go to save a technician having to come to your house a day or two later just to fix something that could be done in a few minutes is not insignificant.
The issue with “a little education” is that it has to be the right little bit.
For most people who don’t make a career or a hobby out of it, it’s like being pointed at a library and told “if you just read one book, you wouldn’t have this problem.”
If you have anything larger than a home installation you easily get some horribly mistuned antennae that let phones receive wifi but don’t catch the response at the same dbm, leading to phones hanging in their now broken wifi when walking out, or repeating connection attempts when walking in.
I had to block the wifi of my university for that, as it would regularly drop my internet if I went past any of their buildings. Also made me disable wifi calls
This a WiFi channel issue. People often leave WiFi on auto channel mode. Like you said, this is fine for a single point network. For bigger networks, you’re supposed to set your channels to static and spread your bandwidth.
For example, 2.4 GHz WiFi has channels 1, 6 and 11. The in-between channels are just blending these 3. You would have one end of the network set to 1, the midpoint set to 6, and the far end set to 11. Your client device will do the work of choose the strong signal and jump between them.
If these were in Auto, they would constantly detect each other and regularly channel hop, dropping connections in the process.
I’m talking about persistent outages, that can remain for minutes or hours if you don’t move out of the affected area.
The setups shouldn’t cgange channels, both because they are a large commercial setup and because there is no other interference in some spots.
The dead zones are persistent over years in some spots.
From my experience in IT, it’s almost always a local network issue in the end. That’s not to say, the user’s fault. But the distance a little education on home networking could go to save a technician having to come to your house a day or two later just to fix something that could be done in a few minutes is not insignificant.
The issue with “a little education” is that it has to be the right little bit.
For most people who don’t make a career or a hobby out of it, it’s like being pointed at a library and told “if you just read one book, you wouldn’t have this problem.”
Okay. Which book?
If you have anything larger than a home installation you easily get some horribly mistuned antennae that let phones receive wifi but don’t catch the response at the same dbm, leading to phones hanging in their now broken wifi when walking out, or repeating connection attempts when walking in.
I had to block the wifi of my university for that, as it would regularly drop my internet if I went past any of their buildings. Also made me disable wifi calls
This a WiFi channel issue. People often leave WiFi on auto channel mode. Like you said, this is fine for a single point network. For bigger networks, you’re supposed to set your channels to static and spread your bandwidth.
For example, 2.4 GHz WiFi has channels 1, 6 and 11. The in-between channels are just blending these 3. You would have one end of the network set to 1, the midpoint set to 6, and the far end set to 11. Your client device will do the work of choose the strong signal and jump between them.
If these were in Auto, they would constantly detect each other and regularly channel hop, dropping connections in the process.
I’m talking about persistent outages, that can remain for minutes or hours if you don’t move out of the affected area.
The setups shouldn’t cgange channels, both because they are a large commercial setup and because there is no other interference in some spots.
The dead zones are persistent over years in some spots.
Yeah then someone fucked up ¯\_(ツ)_/¯.
No it’s usually DNS
DNSes don’t cause this issue
It’s always dns tho
Except in that particular issue.