50M Think Broadband Ping Monitor Results (POST YOURS) - Page 237

tdadyslexia · 28-03-2013, 16:36

My Graph

thenry · 01-04-2013, 14:44

mine..

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

Qtx · 01-04-2013, 16:00

Ewww!

GuestUK · 02-04-2013, 13:59

Not looking too good here!

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

Sephiroth · 02-04-2013, 15:53

Quote:

Originally Posted by thenry

mine..

I'm tempted to suggest that if you find a differenrt wireless solution than the SH itself, those perturbations and ramping will go away.

But you know this and may be waiting for other things to happen that might alleviate the problem.

Kushan · 02-04-2013, 16:03

Quote:

Originally Posted by GuestUK

Not looking too good here!

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

Looks fine.

craigj2k12 · 02-04-2013, 16:08

Hallelujah its REINing men

thenry · 02-04-2013, 16:38

Quote:

Originally Posted by Sephiroth

I'm tempted to suggest that if you find a differenrt wireless solution than the SH itself, those perturbations and ramping will go away.

But you know this and may be waiting for other things to happen that might alleviate the problem.

correct. its starting to get worse...

djstevie · 02-04-2013, 17:05

Quote:

Originally Posted by GuestUK

Not looking too good here!

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

That is one of the worst graphs i have ever seen. Shocking!!

Qtx · 02-04-2013, 17:27

Quote:

Originally Posted by GuestUK

Not looking too good here!

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

How do you get packetloss like that without the maximum latency increasing? Is it something to be with it being intermittent on and off over the course of every few seconds?

Looks the the start of a horror b-movie!

---------- Post added at 17:27 ---------- Previous post was at 17:17 ----------

Quote:

Originally Posted by Sephiroth

I'm tempted to suggest that if you find a differenrt wireless solution than the SH itself, those perturbations and ramping will go away.

But you know this and may be waiting for other things to happen that might alleviate the problem.

If memory serves correctly, they are finally due to fix the Croydon network this month which would cover thenry's area too. One could possibly assume that is a nod to those in the know about this. I left VM 4 months ago now, after waiting 7 months for them to fix my connection and then them telling me the new fix date was April 2013.

If those assumptions are correct, about time. The hardware must have been limping along like a lame one eyed dog just waiting to be put out of its misery.

Don't get what you are saying about the superhub though, unless more channels being added is causing problems with overloading the cpu of the hub?

Sephiroth · 02-04-2013, 18:08

Quote:

Originally Posted by Qtx

....
If memory serves correctly, they are finally due to fix the Croydon network this month which would cover thenry's area too. One could possibly assume that is a nod to those in the know about this. I left VM 4 months ago now, after waiting 7 months for them to fix my connection and then them telling me the new fix date was April 2013.

If those assumptions are correct, about time. The hardware must have been limping along like a lame one eyed dog just waiting to be put out of its misery.

Don't get what you are saying about the superhub though, unless more channels being added is causing problems with overloading the cpu of the hub?

TH ran some experiments and Ravenstar on the VM forum built on what TH had offered. Raven's experiments were well structured and it was possible to conclude that when wireless was ON (whether or not used) the ramping effect occurred; when wireless was OFF there was no ramping. We deduced (with no absolute proof) that the hib CPU was struggling, although why doesn't that happen to all SHs?

TH has more pronounced perturbations than Raven and that might be down to Croydon - I don't know.

thenry · 02-04-2013, 18:13

I can't vouch for Ravens experience. it happened here with or without wifi enabled. being in combo mode caused problems. modem mode was steady.

Qtx · 02-04-2013, 18:56

Quote:

Originally Posted by Sephiroth

TH ran some experiments and Ravenstar on the VM forum built on what TH had offered. Raven's experiments were well structured and it was possible to conclude that when wireless was ON (whether or not used) the ramping effect occurred; when wireless was OFF there was no ramping. We deduced (with no absolute proof) that the hib CPU was struggling, although why doesn't that happen to all SHs?

TH has more pronounced perturbations than Raven and that might be down to Croydon - I don't know.

Cheers, nice to know about these kinds of tests.

I would have thought that ping replies were so basic and low level that cpu load wouldn't affect them (or the silly low amount of ram) but im far from an expert in this area and have no idea how it actually works. Just did a quick google to see what chipset and if a single chip is used for all the functions but didn't find anything enlightening, except for a possibly too simple to be true way of bypassing the shubs security.

If ping replies are not dealt with by the chips own routines and is affected by firmware, that could be another avenue. But if its just a few people its unlikely unless something in that area creates a condition that brings it to light.

Interesting to say the least. If work on that area of the network is due or happening, it would be a simpler answer

GuestUK · 02-04-2013, 19:46

Quote:

Originally Posted by Qtx

How do you get packetloss like that without the maximum latency increasing? Is it something to be with it being intermittent on and off over the course of every few seconds?

Looks the the start of a horror b-movie!

That's exactly what I thought (with regards to all the blood!)

As for the traffic, it's really odd. Either a packet gets through perfectly fine, or it doesn't get through at all, there is no inbetween! As of 6pm, the blood all suddenly completely vanished. Hoping it stays like that, but a mystery as to what caused it!

Qtx · 02-04-2013, 20:21

Quote:

Originally Posted by GuestUK

As for the traffic, it's really odd. Either a packet gets through perfectly fine, or it doesn't get through at all, there is no inbetween! As of 6pm, the blood all suddenly completely vanished. Hoping it stays like that, but a mystery as to what caused it!

Could make a guess that the gateway was confused and thought it was overloaded when it wasn't, causing it to drop icmp echo packets. Only scenario that comes to mind that would part explain it.

Fingers crossed it stays working