[MUD_Wizard]

Originally Posted by Deathcrush87

ok, i got my cat5EEEE, and i ran some tests yesterday and today.
the results were quite mixed.
I got very good ping, but suddenly the internet disconnected.
disconnection happened alot today. literally every 5 minutes the internet went off on cable, wifi, powerline everything.. and then again internet came back on after 1~2 minutes.

i thought the new cat5 was the cause, so i disconnected it and used wifi.. horrible ping i got. used powerline, same story as the solid cable.


you can also check the graph.
restarted the router a few times, did not help with the disconnections.

have not ran the superhub in modem mode yet, gonna do it tomorrow morning when everyone is away.

It's nothing to do with the CAT5 ethernet cable. The BQM graph below proves that as it only monitors the connection from the hub to Thinkbroadband.com and back. So it's a great way of proving that those disconnections today were not to do with your cat 5/wifi/or powerline.



However, if you look at the green (minimum latency) you can clearly see it ramping until you did the reboot at 5pm. That phenomena is due to the hub, as I've said before. The reboot proves that.

The red lines (packet loss and disconnections today) are most likely due to an additional network fault of some kind between the hub and VM's network. So you won't be able to influence that by rebooting the hub, as it's likely being caused by something far outside your house. These things happen from time to time. You'll need to ask VM to check your connection to find out what happened.

The two most common types of fault that look like that are: 1) what is called an SNR fault (due to noise) and 2) problems with power levels going out of range.

Posting your downstream, upstream and network log stats may indicate which of those two it was. Though the network log may be blank as the SH1 clears it whenever it reconnects to the network. The SH2/2ac have more memory and retain the logs over re-connections, which makes them a lot more useful for diagnosing faults.

p.s. The cat5 also proves that a lot of the high latency (after you've rebooted the hub and reduced the ramp) you're seeing is due to poor wifi and powerline.