Quote:
Originally Posted by Ignitionnet
Well here you go, the red lines are where the PoS needed resetting due to getting unstable.
 |
is there a reason you can think off why it looks like congestion building up at 3am then suddenly dissapears in an instant? I wonder if it had switched to qpsk on upstream and then back again. Also the rugged min latency that starts after midnight post shaping, I also wonder if you also have downstream congestion.
---------- Post added at 16:24 ---------- Previous post was at 16:18 ----------
Quote:
Originally Posted by craigj2k11
okay whatever, it would be pretty tough to prove in court i suppose lol
|
pinging in that it denies service eg. a DOS or DDOS yes but something like the TBB monitor is perfectly legal.
People ping services like bbc.co.uk all the time without specific permission.
---------- Post added at 16:28 ---------- Previous post was at 16:24 ----------
Quote:
Originally Posted by craigj2k11
whats with the ups and downs? if it was permanently in the low bit, it would be amazing
|
I commented on this in a previous post in this thread. In my view its to do with the vmng300 it seems to jump in between 2 modes in how it handles pings. If I run tests during a jump it is no significant difference from when it is really low, and is actually usually slightly better than when its low.
I can have tbb showing jitter of about 10ms then run pingtest.net and get 1ms, and I have posted pings on this forum numerous times lately showing very low jitter like on ignition's thread. So in my view when it jumps down thats the real jitter, and when it jumps up the operational mode changes to deprioritise the packets. What I have no idea on is if its the dir615 or the vmng300 as the vmng300 should simply be passing through the packets with no processing at all. However when I used the dir615 with my old 20mbit modem I did not see this pattern.