Quote:
Originally Posted by MaverickJesus
I did a traceroute while it was happening, it wasn't anywhere near Virgin's network. For once.
|
A traceroute that spikes outside of VM's network does not mean the fault causing it is not on VM's network. In other words, your traceroute proves nothing about where it is happening.
Quote:
|
Just because it didn't occur under BT's network doesn't automatically make it a problem on VM's network and you know it.
|
It didn't occur on
any of these other networks: BT, Sky, O2, Talktalk, Bulldog, OVH, JANET, Leaseweb, Goscomb, Vodafone, Be*.
It did occur on VM. Go figure...
---------- Post added at 12:41 ---------- Previous post was at 12:36 ----------
Quote:
Originally Posted by Kymmy
First thing I checked, same IP, same settings, rebooted SH, even disabled firewall and made sure that WAN ping was enabled before the reboot. Nothing has changed but from my post at the top of this page it looks like it happened in two stages..
Weird |
Firewall/flood detection on? Other people have reported having more than one device pinging the Superhub at a time can cause it to falsely trigger and stop responding.
That or the ping responder process is buggy, which has also happened, requiring a reboot.