|
The point my colleague is making is that in testing with Wi-Fi (which is fickle and fundamentally unreliable) you don't know whether you have an issue with Wi-Fi or an issue with you ISP link. If the latter, you can contact the ISP to sort it. If the former you are more or less on your own (though we can help.) By testing using ethernet, you take Wi-Fi out of the equation and can establish whether the ISP link is working reliably or not.
If your install is fairly new, it can take up to a fortnight for the equipment in the exchange to "train" the line to it's optimal performance and during that training period the ISP link could go up and down a bit.
The best place to get line stats is in the routers diagnostic pages if it has them (not all do.)
In Wi-Fi, it's not "the system" that decides which waveband to use if you use the same SSID, it's the client device. If your client is flapping between 2.4GHz and 5GHz, then there may be some reason it's doing so such as an interference or other poor signalling conditions.
So, on the back of my colleagues advice I suggest, 1st ensure the install has been in place long enough to train the line, 2nd monitor the router line stats and see how they behave, (in preference to speedtest sites) then 3rd if the line looks good, you can start investigating if you have Wi-FI issues. It sounds like you've got interference and/or coverage problems , but prove the ISP line is good first.
Of course, both your Wi-Fi air time and ISP link are finite resources, and if you are all competing for it (its anything but "fair") at once, performance for any individual could get funky. Whereas is everyone else is out, you may have it all to yourself. |
|