|
If both wired and Wi-Fi are affected, potentially you've got something flooding your network with traffic, possibly even a "broadcast storm." For example, a device with what we (in IT) call a "jabbering" NIC (it's been decades since I'm seen one though) or something has caught some malware or a bot that's chucking out junk or the aforementioned broadcast storm.
Broadcast storms mostly occur if you create a "loop" in the topology of your network which means pretty quickly the network gets filled up with endlessly circling traffic which essentially blocks out everything else like a gridlock on the road network. Usually broadcast storms kill everything, but can manifest as erratic and slow performance. Of course the solution is to eliminate any such loop if you've got one.
It'll be a time consuming pain to do, but one way to assess whether any particular device is culpable is to disconnect (physically for wired devices, turn of Wi-Fi fr Wi-Fi devices) everything then test it all one by one.
I'd proceed by starting with the HH, check it with something (laptop would be ideal) then progressively reintroduce all the "infrastructure" components such as your switches and powerline and establish whether they are all good (which will tend to disprove a broadcast storm.)
If that proves OK, thence one by one, test all your clients. ie connect client, test it, disconnect client, rinse and repeat until you've tried them all and/or found what's culpable.
By "test" I mean run it for half a hour of so, not a couple of minutes (unless or until you've discovered any particular device that's culpable.) It can sometimes be a while before it kicks off.
It's a bit of a forlorn hope though.
Highly unlikely, but possible, is someone is "jamming" your Wi-Fi by injecting a load of "junk" traffic into it (which can the propagate onto the wires if it's broadcast) or someone nearby has hacked your Wi-Fi and is war-driving you. Testing wires only would give some indication whether these are potential issues.
I'm afraid for some issues, there's nothing for it but some methodical and forensic testing.
I've not stress tested one, but I'd be surprised if an HH6 couldn't cope with a couple of dozen devices in a SOHO use case, but it is wildly dependent on you traffic patterns and so forth and SOHO kit mostly doesn't have the facilities to let you look under the bonnet and see whats going on with (for example) CPU and RAM usage.
Many, many years ago I put up a cheap SOHO router on a network in a college (back before everyone had laptops and smartphones) and it was fine until we had getting on for a hundred devices simultaneously online which killed it. (That was an old 10/100 non-Wi-Fi router with "only" 16MB of RAM.)
If you've got a traffic problem, then splitting Wi-Fi bands will probably make no difference. Likewise, BT may wash there hands of it as anything "wrong" with your network as it's not there responsibility. It's "your" network, even if they supplied the router and they may defer once they've proved the equipment they supplied isn't faulty and the ISP link is OK (ie "their" bit.) |
|