50M Installed Finally But... - Page 8

craigj2k12 · 12-05-2011, 15:32

the network up your end looks amazing

Ignitionnet · 12-05-2011, 15:44

VM aren't rebuilding it for nothing, Telewest should have done it years ago.

I wonder if the packet loss is being caused by the Superhub or the packet loss is causing the Superhub to throw a wobbly. Firmly inclined to blame the Superhub as loss stopped when reloaded.

craigj2k12 · 12-05-2011, 15:46

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!

Ignitionnet · 12-05-2011, 16:30

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.

craigj2k12 · 12-05-2011, 17:59

Quote:

Maximum = 221ms

ping of 221ms to the hub????? wtf? anything more than 1 is suspicious in my opinion

Chrysalis · 12-05-2011, 18:40

to the dns seerver craig

I had ignition's pain before the vmng300, when you have a device so broken it becomes too easy to blame it for 'any' problem.

craigj2k12 · 12-05-2011, 18:41

Quote:

Originally Posted by Chrysalis

to the dns seerver craig

Ping statistics for 192.168.0.1

Chrysalis · 12-05-2011, 18:46

ahh yeah I see now he did 2 lots of pings, what the ....

Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

vmng300 seems ok.

Ignitionnet · 12-05-2011, 18:50

Quote:

Originally Posted by craigj2k11

ping of 221ms to the hub????? wtf? anything more than 1 is suspicious in my opinion

I don't really care about latency to the Superhub, I've had routers that can't be bothered to respond to pings unless they feel like it, doesn't worry me. It was purely there to prove that the packet loss wasn't local.

It's gone now and stuff is working.

craigj2k12 · 12-05-2011, 20:54

iv never had a ping to the modem or router, my old belkin, and even the superhub has response times never more than 1 or 2ms

looks like you have a very dodgy superhub, you should put it through its paces when the network problem is sorted

Chrysalis · 12-05-2011, 20:57

Quote:

Originally Posted by Ignitionnet

I don't really care about latency to the Superhub, I've had routers that can't be bothered to respond to pings unless they feel like it, doesn't worry me. It was purely there to prove that the packet loss wasn't local.

It's gone now and stuff is working.

I have seen it when the router isnt the endpoint, eg. my speedtouch will have around 99ms on its hop in a tracert but when I pinged it direct as an endpoint was sub 1ms.

Ignitionnet · 12-05-2011, 21:27

This was done over wifi - not bothered by latency purely interested in packet loss

Chrysalis · 12-05-2011, 21:35

fair enough.

Ignitionnet · 13-05-2011, 18:10

Bah wondered why I was failing at X-Box, now I've been given an excuse!

[img]Download Failed (1)[/img]

Not peak time for another couple of hours here yet, sweet. Will have a couple of rum and cokes and see if that balances out the jitter

craigj2k12 · 13-05-2011, 18:31

Quote:

Originally Posted by Ignitionnet

Bah wondered why I was failing at X-Box, now I've been given an excuse!

Not peak time for another couple of hours here yet, sweet. Will have a couple of rum and cokes and see if that balances out the jitter

wait till the jitter dies down, you will be jittering at the game lol