Quote:
Originally Posted by craigj2k11
the network is probably causing a lot of errors to be sent to you, and the superhub is trying to correct codewords, bearing in mind the performance of the superhub in general, then give it all those errors, its a recipe for disaster!
|
Unlikely.
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power SNR Docsis/EuroDocsis locked
Locked QAM256 91 55616000 Kbits/sec 315000000 Hz 4.9 dBmV 39.4 dB Hybrid
Locked QAM256 89 55616000 Kbits/sec 299000000 Hz 4.9 dBmV 39.8 dB Hybrid
Locked QAM256 90 55616000 Kbits/sec 307000000 Hz 5.0 dBmV 39.9 dB Hybrid
Locked QAM256 92 55616000 Kbits/sec 323000000 Hz 5.1 dBmV 39.5 dB Hybrid
---------- Post added at 17:30 ---------- Previous post was at 17:01 ----------
Looks like I owe the Superhub an apology. While the issue seemed to clear up after the reboot it looks like it was a coincidence and it's the network, specifically upstream.
These were done simultaneously:
Ping statistics for 194.168.4.100:
Packets:
Sent = 100, Received = 48, Lost = 52 (52% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 66ms, Average = 15ms
Ping statistics for 192.168.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 221ms, Average = 6ms
This packet loss has been replicated using the Superhub's own ping utility.