on 02-12-2016 05:31
Good Day Ladies and Gentlemen,
Greetings from the other side of the pond, so to speak. Over the last few weeks I've been perusing various user forums across North America and Europe for issues related to Intel Puma 6 modem latency. Of those forums, your Hub 3 stands out as yet another Puma 6 based modem where users see continuous latency no matter what site is used or what online game is played. Considering all of the problems that are on the go, the following information should be of interest to all Hub 3, Compal CH7465-LG and Hitron CGNV4 modem users. There is much more to post regarding this, so this is a start, to alert VM users as to the real cause of the latency and hopefully engage the VM engineering staff, via the forum staff, with Arris. I am surprised to see that there has been no mention on this board of users from other ISPs who are suffering the exact same issues with their modems, so, this may come as a surprise to some, and possibly old news to others.
So, the short story ........
The Hub 3 / Compal CH7465-LG (TG2492LG) & Hiton CGNV4 modems are Intel Puma 6 / 6 Media Gateway (MG) based modems. These modems exhibit high latency to the modem and high latency thru the modem. The latency affects all IPV4 and IPV6 protocols, so it will be seen on every internet application and game. The basic cause is the processing of the data packets thru a CPU software based process instead of thru the hardware processor / accelerator. It appears that a higher priority task runs periodically, causing the packet processing to halt, and then resume. This is observed as latency in applications and in ping tests to the modem and beyond. For the last several weeks, Hitron, along with Intel and Rogers Communications in Canada have been addressing the latency issue within the Hitron CGNxxx series modems. To date, only the IPV4 ICMP latency has been resolved. Although this is only one protocol, it does show that a Puma 6MG modem is capable of using the hardware processor / accelerator with good results. Currently Rogers is waiting for further firmware updates from Hitron which should include an expanded list of resolved protocol latency issues. For Arris modems, "Netdog" an Arris engineer indicated last week that Arris was onboard to address the issue for the Arris SB6190 modem. That should be considered as good news for any Arris modem (read Hub 3) user as Arris should be able to port those changes over to other Puma 6/6MG modems fairly quickly. This is not a trivial exercise and will probably take several weeks to accomplish. Note that there is no guarantee at this point that it is possible to shift all packet processing to the hardware processor / accelerator without suffering from any packet loss side effects. Time will tell if all of the technical issues can be resolved with the current hardware included in the Puma 6/6MG chipset. Last night, Netdog loaded beta firmware on selected test modems on the Comcast Communications network. As this was only done last night, it's too soon to tell what this version resolves and if it was successful or not. Netdog has contacts with staff at Comcast, Rogers, Charter and Cox Communications to fan out beta versions and modifications for testing. I'd say its time to add Virgin Media and/or Liberty Global to that group as well.
Recent activity:
Approx three weeks ago a DSLReports user, xymox1 started a thread where he reported high latency to an Arris SB6190 and illustrated that with numerous MultiPing plots. This is the same latency that I and other users with Rogers communications have been dealing with for months so it came as no surprise. As well as reporting via that thread, xymox1 took it upon himself to email several staff members at Arris, Intel, Cablelabs and others. The result of that campaign was Netdog's announcement, last week, that Arris was fully engaged at resolving the issue. That has led to last nights release of beta firmware, although as I indicated its too early to determine what the beta firmware resolves, if anything.
The original thread that xymox1 started is here:
Yesterday, DSLReports issued a news story covering the thread:
Today, Arris responded:
That response was also picked by Multichannel.com
http://www.multichannel.com/news/distribution/intel-arris-working-firmware-fix-sb6190-modem/409379
This is more news likely to appear in the next few days as additional tech and news staff pick up on this issue.
Hub 3 observations:
Like many others using a Puma 6/6MG modem, Hub 3 users are experiencing latency when they ping the modem, or ping a target outside of the home, game online or use low latency applications. The common misconception is that this is Buffer Bloat. It's not. Its most likely a case of the packet processing stopping while the CPU processes a higher priority task. The packet processing is done via the CPU no matter what mode the modem is operating in, modem mode or router mode and no matter what IPV4 or IPV6 protocol is used. Normally, the latency is just that, latency. The exception are UDP packets. In this case there is latency and packet loss. The result of that is delayed and failed DNS lookups, and poor game performance for games that use UDP for player/server comms or player/player comms.
Can this be fixed?
So far, it appears that the answer is yes. Rogers Communications issued beta firmware to a small group of test modems in October. This version shifted the IPV4 ICMP processing from the CPU to the hardware processor / accelerator, resulting in greatly improved performance in ping latency. At the present time we are waiting for the next version firmware which should shift other protocols over to the hardware processor / accelerator. That can be seen in the following post:
The details and results of last nights beta release to the Comcast group have yet to be seen.
At this point there is enough reading to keep most staff and users busy. My intention is to post some of the history leading up to this point and instructions on how to detect the latency and packet loss. This is not thru the use of a BQM. I had hoped to post this all at once but events are moving much faster than I had thought they would. For now this should suffice to get the ball rolling.
Below is a link to a post with a couple of HrPing plots from my 32 channel modem to the connected CMTS. This shows the latency that is observed and reflects what others have posted in this forum using Pingplotter and HrPing.
https://www.dslreports.com/forum/r31106550-
HrPing is one of the freebie applications that can be used to monitor the latency to and thru the modem.
Pingplots with Pingplotter which show the latency from my modem to the CMTS can be found in the first two to three rows of my online image library at Rogers Communications, located below. They are essentially what the BQM would look like if you were able to zoom into the plot to the point where you could see the individual ping spikes. Those ping spikes are common to Puma 6 and Puma 6MG modems.
http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158
[MOD EDIT: Subject heading changed to assist community]
on 03-05-2018 23:59
Ahh bummer.
I’m on the 100mbps package. 24channels. Guess will have to wait then 😕
on 04-05-2018 02:18
I'm living in a Project lighting area, but I think there must have been some sort of additional work done on the Network because after my daily restart I now suddenly have 4 bonded upload channels for whatever reason, which has also bumped down the minimum latency for whatever reason its hard to see until you put your mouse over just before the red hits then comparing it to when the connection starts again, why would that happen ;o? Blue spikes are speedtests.
Why would 4 bonded upload channels change the latency slightly? Why do we even have 4 bonded upload channels o.-
on 04-05-2018 07:07
@Touhoufan wrote:I'm living in a Project lighting area, but I think there must have been some sort of additional work done on the Network because after my daily restart I now suddenly have 4 bonded upload channels for whatever reason, which has also bumped down the minimum latency for whatever reason its hard to see until you put your mouse over just before the red hits then comparing it to when the connection starts again, why would that happen ;o? Blue spikes are speedtests.
Why would 4 bonded upload channels change the latency slightly? Why do we even have 4 bonded upload channels o.- [SEPH]: The bonding of channels is the method used by DOCSIS 3 to balance load across different radio frequencies. You share your channels with between 200 & 500 people. So when you rise from 2 channels to 4, additional capacity is available. In a previously heavily utilised upstream situation, if capacity is doubled, then latency must fall. That said, as the night progresses, users go to sleep and the segment/node load falls anyway.
Your graph:
g
on 04-05-2018 15:19
Post split across three due to text limit with several pictures inbound, but well worth the read...
Well, I finally got the time to grab a Windows laptop and re-run all the tests and the results were... well, I'll leave it for you all to see. The setup for this, was a Windows 10 laptop - i5, 4GB RAM cabled into to an R7800 in Modem Mode, Hub 3 on .603 firmware. iPerf was run using the latest 3.5 version, ping plotter is running the pro version (trial).
Firstly, the usual Puma 6 test on DSLReports. As good as you can get really for a DOCSIS network:
Secondly the UDP iPerf3 tests using the settings posted by Phil John:
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-1.00 sec 128 KBytes 1.05 Mbits/sec 2.892 ms 0/90 (0%) (omitted) [ 5] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 0.200 ms 0/90 (0%) (omitted) [ 5] 0.00-1.00 sec 128 KBytes 1.05 Mbits/sec 0.254 ms 0/90 (0%) [ 5] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 0.243 ms 0/90 (0%) [ 5] 2.00-3.00 sec 127 KBytes 1.04 Mbits/sec 0.252 ms 0/89 (0%) [ 5] 3.00-4.00 sec 128 KBytes 1.05 Mbits/sec 0.285 ms 0/90 (0%) [ 5] 4.00-5.00 sec 128 KBytes 1.05 Mbits/sec 0.248 ms 0/90 (0%) [ 5] 5.00-6.00 sec 128 KBytes 1.05 Mbits/sec 0.237 ms 0/90 (0%) [ 5] 6.00-7.00 sec 127 KBytes 1.04 Mbits/sec 0.270 ms 0/89 (0%) [ 5] 7.00-8.00 sec 128 KBytes 1.05 Mbits/sec 0.256 ms 0/90 (0%) [ 5] 8.00-9.00 sec 128 KBytes 1.05 Mbits/sec 0.221 ms 0/90 (0%) [ 5] 9.00-10.00 sec 128 KBytes 1.05 Mbits/sec 0.202 ms 0/90 (0%) [ 5] 10.00-11.00 sec 128 KBytes 1.05 Mbits/sec 0.243 ms 0/90 (0%) [ 5] 11.00-12.00 sec 127 KBytes 1.04 Mbits/sec 0.201 ms 0/89 (0%) [ 5] 12.00-13.00 sec 128 KBytes 1.05 Mbits/sec 0.239 ms 0/90 (0%) [ 5] 13.00-14.00 sec 128 KBytes 1.05 Mbits/sec 0.240 ms 0/90 (0%) [ 5] 14.00-15.00 sec 128 KBytes 1.05 Mbits/sec 0.255 ms 0/90 (0%) [ 5] 15.00-16.00 sec 127 KBytes 1.04 Mbits/sec 0.283 ms 0/89 (0%) [ 5] 16.00-17.00 sec 128 KBytes 1.05 Mbits/sec 0.240 ms 0/90 (0%) [ 5] 17.00-18.00 sec 128 KBytes 1.05 Mbits/sec 0.272 ms 0/90 (0%) [ 5] 18.00-19.00 sec 128 KBytes 1.05 Mbits/sec 0.221 ms 0/90 (0%) [ 5] 19.00-20.00 sec 128 KBytes 1.05 Mbits/sec 0.265 ms 0/90 (0%) [ 5] 20.00-21.00 sec 127 KBytes 1.04 Mbits/sec 0.232 ms 0/89 (0%) [ 5] 21.00-22.00 sec 128 KBytes 1.05 Mbits/sec 0.209 ms 0/90 (0%) [ 5] 22.00-23.00 sec 128 KBytes 1.05 Mbits/sec 0.219 ms 0/90 (0%) [ 5] 23.00-24.00 sec 128 KBytes 1.05 Mbits/sec 0.264 ms 0/90 (0%) [ 5] 24.00-25.00 sec 127 KBytes 1.04 Mbits/sec 0.247 ms 0/89 (0%) [ 5] 25.00-26.00 sec 128 KBytes 1.05 Mbits/sec 0.253 ms 0/90 (0%) [ 5] 26.00-27.00 sec 128 KBytes 1.05 Mbits/sec 0.280 ms 0/90 (0%) [ 5] 27.00-28.00 sec 128 KBytes 1.05 Mbits/sec 0.197 ms 0/90 (0%) [ 5] 28.00-29.00 sec 128 KBytes 1.05 Mbits/sec 0.247 ms 0/90 (0%) [ 5] 29.00-30.00 sec 127 KBytes 1.04 Mbits/sec 0.252 ms 0/89 (0%) [ 5] 30.00-31.00 sec 128 KBytes 1.05 Mbits/sec 0.271 ms 0/90 (0%) [ 5] 31.00-32.00 sec 128 KBytes 1.05 Mbits/sec 0.245 ms 0/90 (0%) [ 5] 32.00-33.00 sec 128 KBytes 1.05 Mbits/sec 0.240 ms 0/90 (0%) [ 5] 33.00-34.00 sec 127 KBytes 1.04 Mbits/sec 0.234 ms 0/89 (0%) [ 5] 34.00-35.00 sec 128 KBytes 1.05 Mbits/sec 0.258 ms 0/90 (0%) [ 5] 35.00-36.00 sec 128 KBytes 1.05 Mbits/sec 0.246 ms 0/90 (0%) [ 5] 36.00-37.00 sec 128 KBytes 1.05 Mbits/sec 0.238 ms 0/90 (0%) [ 5] 37.00-38.00 sec 128 KBytes 1.05 Mbits/sec 0.254 ms 0/90 (0%) [ 5] 38.00-39.00 sec 127 KBytes 1.04 Mbits/sec 0.262 ms 0/89 (0%) [ 5] 39.00-40.00 sec 128 KBytes 1.05 Mbits/sec 0.264 ms 0/90 (0%) [ 5] 40.00-41.00 sec 128 KBytes 1.05 Mbits/sec 0.236 ms 0/90 (0%) [ 5] 41.00-42.00 sec 128 KBytes 1.05 Mbits/sec 0.222 ms 0/90 (0%) [ 5] 42.00-43.00 sec 127 KBytes 1.04 Mbits/sec 0.185 ms 0/89 (0%) [ 5] 43.00-44.00 sec 128 KBytes 1.05 Mbits/sec 0.229 ms 0/90 (0%) [ 5] 44.00-45.00 sec 128 KBytes 1.05 Mbits/sec 0.240 ms 0/90 (0%) [ 5] 45.00-46.00 sec 128 KBytes 1.05 Mbits/sec 0.219 ms 0/90 (0%) [ 5] 46.00-47.00 sec 128 KBytes 1.05 Mbits/sec 0.233 ms 0/90 (0%) [ 5] 47.00-48.00 sec 127 KBytes 1.04 Mbits/sec 0.249 ms 0/89 (0%) [ 5] 48.00-49.00 sec 128 KBytes 1.05 Mbits/sec 0.234 ms 0/90 (0%) [ 5] 49.00-50.00 sec 128 KBytes 1.05 Mbits/sec 0.254 ms 0/90 (0%) [ 5] 50.00-51.00 sec 128 KBytes 1.05 Mbits/sec 0.199 ms 0/90 (0%) [ 5] 51.00-52.00 sec 127 KBytes 1.04 Mbits/sec 0.315 ms 0/89 (0%) [ 5] 52.00-53.00 sec 128 KBytes 1.05 Mbits/sec 0.240 ms 0/90 (0%) [ 5] 53.00-54.00 sec 128 KBytes 1.05 Mbits/sec 0.248 ms 0/90 (0%) [ 5] 54.00-55.00 sec 128 KBytes 1.05 Mbits/sec 0.258 ms 0/90 (0%) [ 5] 55.00-56.00 sec 127 KBytes 1.04 Mbits/sec 0.255 ms 0/89 (0%) [ 5] 56.00-57.00 sec 128 KBytes 1.05 Mbits/sec 0.269 ms 0/90 (0%) [ 5] 57.00-58.00 sec 128 KBytes 1.05 Mbits/sec 0.241 ms 0/90 (0%) [ 5] 58.00-59.00 sec 128 KBytes 1.05 Mbits/sec 0.259 ms 0/90 (0%) [ 5] 59.00-60.00 sec 128 KBytes 1.05 Mbits/sec 0.254 ms 0/90 (0%) [ 5] 60.00-61.00 sec 127 KBytes 1.04 Mbits/sec 0.214 ms 0/89 (0%) [ 5] 61.00-62.00 sec 128 KBytes 1.05 Mbits/sec 0.256 ms 0/90 (0%) - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-62.00 sec 7.76 MBytes 1.05 Mbits/sec 0.000 ms 0/5566 (0%) sender [ 5] 0.00-62.00 sec 7.75 MBytes 1.05 Mbits/sec 0.256 ms 0/5566 (0%) receiver [ ID] Interval Transfer Bitrate Total Datagrams [ 5] 0.00-1.00 sec 128 KBytes 1.05 Mbits/sec 90 (omitted) [ 5] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 90 (omitted) [ 5] 0.00-1.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 2.00-3.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 3.00-4.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 4.00-5.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 5.00-6.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 6.00-7.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 7.00-8.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 8.00-9.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 9.00-10.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 10.00-11.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 11.00-12.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 12.00-13.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 13.00-14.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 14.00-15.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 15.00-16.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 16.00-17.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 17.00-18.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 18.00-19.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 19.00-20.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 20.00-21.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 21.00-22.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 22.00-23.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 23.00-24.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 24.00-25.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 25.00-26.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 26.00-27.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 27.00-28.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 28.00-29.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 29.00-30.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 30.00-31.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 31.00-32.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 32.00-33.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 33.00-34.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 34.00-35.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 35.00-36.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 36.00-37.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 37.00-38.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 38.00-39.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 39.00-40.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 40.00-41.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 41.00-42.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 42.00-43.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 43.00-44.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 44.00-45.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 45.00-46.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 46.00-47.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 47.00-48.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 48.00-49.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 49.00-50.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 50.00-51.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 51.00-52.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 52.00-53.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 53.00-54.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 54.00-55.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 55.00-56.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 56.00-57.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 57.00-58.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 58.00-59.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 59.00-60.00 sec 128 KBytes 1.05 Mbits/sec 90 [ 5] 60.00-61.00 sec 127 KBytes 1.04 Mbits/sec 89 [ 5] 61.00-62.00 sec 128 KBytes 1.05 Mbits/sec 90 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-62.00 sec 7.75 MBytes 1.05 Mbits/sec 0.000 ms 0/5566 (0%) sender [ 5] 0.00-62.00 sec 7.76 MBytes 1.05 Mbits/sec 1.917 ms 2/5566 (0.036%) receiver
on 04-05-2018 15:20
Following feedback from Datalink, I then run the test with the UDP iPerf settings he provided:
Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 2 seconds, 62 second test, tos 0 [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-1.00 sec 12.2 MBytes 102 Mbits/sec 0.108 ms 29943/42416 (71%) (omitted) [ 5] 1.00-2.00 sec 12.3 MBytes 103 Mbits/sec 0.028 ms 30052/42619 (71%) (omitted) [ 5] 0.00-1.00 sec 12.1 MBytes 102 Mbits/sec 0.092 ms 30853/43251 (71%) [ 5] 1.00-2.00 sec 12.1 MBytes 102 Mbits/sec 0.034 ms 29002/41426 (70%) [ 5] 2.00-3.00 sec 12.6 MBytes 106 Mbits/sec 0.098 ms 31599/44550 (71%) [ 5] 3.00-4.00 sec 15.3 MBytes 128 Mbits/sec 0.027 ms 25660/41286 (62%) [ 5] 4.00-5.00 sec 16.0 MBytes 134 Mbits/sec 0.023 ms 24357/40722 (60%) [ 5] 5.00-6.00 sec 17.2 MBytes 144 Mbits/sec 0.019 ms 25023/42642 (59%) [ 5] 6.00-7.00 sec 16.9 MBytes 142 Mbits/sec 0.018 ms 25461/42798 (59%) [ 5] 7.00-8.00 sec 16.4 MBytes 137 Mbits/sec 0.020 ms 25684/42446 (61%) [ 5] 8.00-9.00 sec 18.3 MBytes 154 Mbits/sec 0.053 ms 25917/44688 (58%) [ 5] 9.00-10.00 sec 16.8 MBytes 141 Mbits/sec 0.018 ms 24135/41382 (58%) [ 5] 10.00-11.00 sec 17.7 MBytes 148 Mbits/sec 0.046 ms 24960/43081 (58%) [ 5] 11.00-12.00 sec 17.2 MBytes 144 Mbits/sec 0.039 ms 24529/42094 (58%) [ 5] 12.00-13.00 sec 17.9 MBytes 150 Mbits/sec 0.023 ms 24229/42531 (57%) [ 5] 13.00-14.00 sec 16.7 MBytes 140 Mbits/sec 0.019 ms 25769/42872 (60%) [ 5] 14.00-15.00 sec 17.2 MBytes 144 Mbits/sec 0.024 ms 25269/42880 (59%) [ 5] 15.00-16.00 sec 17.8 MBytes 149 Mbits/sec 0.034 ms 25403/43602 (58%) [ 5] 16.00-17.00 sec 16.7 MBytes 140 Mbits/sec 0.020 ms 24965/42083 (59%) [ 5] 17.00-18.00 sec 17.2 MBytes 144 Mbits/sec 0.028 ms 26879/44477 (60%) [ 5] 18.00-19.00 sec 16.7 MBytes 140 Mbits/sec 0.026 ms 26043/43191 (60%) [ 5] 19.00-20.00 sec 16.6 MBytes 139 Mbits/sec 0.032 ms 24506/41482 (59%) [ 5] 20.00-21.00 sec 15.9 MBytes 133 Mbits/sec 0.021 ms 25043/41301 (61%) [ 5] 21.00-22.00 sec 17.1 MBytes 143 Mbits/sec 0.019 ms 25639/43123 (59%) [ 5] 22.00-23.00 sec 17.3 MBytes 145 Mbits/sec 0.020 ms 24620/42361 (58%) [ 5] 23.00-24.00 sec 16.6 MBytes 139 Mbits/sec 0.020 ms 25753/42732 (60%) [ 5] 24.00-25.00 sec 17.0 MBytes 142 Mbits/sec 0.023 ms 25446/42836 (59%) [ 5] 25.00-26.00 sec 16.5 MBytes 138 Mbits/sec 0.024 ms 25502/42354 (60%) [ 5] 26.00-27.00 sec 18.0 MBytes 151 Mbits/sec 0.020 ms 27112/45505 (60%) [ 5] 27.00-28.00 sec 16.9 MBytes 142 Mbits/sec 0.021 ms 25909/43220 (60%) [ 5] 28.00-29.00 sec 16.4 MBytes 138 Mbits/sec 0.026 ms 24663/41469 (59%) [ 5] 29.00-30.00 sec 16.4 MBytes 137 Mbits/sec 0.024 ms 24376/41135 (59%) [ 5] 30.00-31.00 sec 17.3 MBytes 145 Mbits/sec 0.023 ms 26184/43881 (60%) [ 5] 31.00-32.00 sec 16.2 MBytes 136 Mbits/sec 0.048 ms 25725/42352 (61%) [ 5] 32.00-33.00 sec 17.2 MBytes 145 Mbits/sec 0.029 ms 26226/43885 (60%) [ 5] 33.00-34.00 sec 15.9 MBytes 133 Mbits/sec 0.065 ms 24266/40497 (60%) [ 5] 34.00-35.00 sec 16.8 MBytes 141 Mbits/sec 0.022 ms 25668/42856 (60%) [ 5] 35.00-36.00 sec 17.2 MBytes 144 Mbits/sec 0.022 ms 25539/43124 (59%) [ 5] 36.00-37.00 sec 17.2 MBytes 144 Mbits/sec 0.019 ms 26697/44297 (60%) [ 5] 37.00-38.00 sec 16.9 MBytes 142 Mbits/sec 0.022 ms 25369/42672 (59%) [ 5] 38.00-39.00 sec 16.4 MBytes 138 Mbits/sec 0.021 ms 24422/41214 (59%) [ 5] 39.00-40.00 sec 17.0 MBytes 142 Mbits/sec 0.024 ms 26116/43509 (60%) [ 5] 40.00-41.00 sec 16.3 MBytes 137 Mbits/sec 0.018 ms 24947/41633 (60%) [ 5] 41.00-42.00 sec 16.6 MBytes 139 Mbits/sec 0.021 ms 25585/42569 (60%) [ 5] 42.00-43.00 sec 17.5 MBytes 147 Mbits/sec 0.070 ms 27066/44974 (60%) [ 5] 43.00-44.00 sec 16.1 MBytes 135 Mbits/sec 0.019 ms 24152/40608 (59%) [ 5] 44.00-45.00 sec 17.0 MBytes 143 Mbits/sec 0.040 ms 26457/43902 (60%) [ 5] 45.00-46.00 sec 17.0 MBytes 143 Mbits/sec 0.020 ms 25807/43250 (60%) [ 5] 46.00-47.00 sec 16.4 MBytes 138 Mbits/sec 0.022 ms 24954/41779 (60%) [ 5] 47.00-48.00 sec 16.5 MBytes 139 Mbits/sec 0.056 ms 26345/43268 (61%) [ 5] 48.00-49.00 sec 16.5 MBytes 138 Mbits/sec 0.022 ms 24720/41575 (59%) [ 5] 49.00-50.00 sec 16.5 MBytes 138 Mbits/sec 0.022 ms 25667/42552 (60%) [ 5] 50.00-51.00 sec 17.0 MBytes 143 Mbits/sec 0.024 ms 25717/43159 (60%) [ 5] 51.00-52.00 sec 16.5 MBytes 139 Mbits/sec 0.021 ms 25119/42031 (60%) [ 5] 52.00-53.00 sec 17.6 MBytes 147 Mbits/sec 0.061 ms 27338/45343 (60%) [ 5] 53.00-54.00 sec 15.8 MBytes 132 Mbits/sec 0.034 ms 24260/40415 (60%) [ 5] 54.00-55.00 sec 17.5 MBytes 147 Mbits/sec 0.090 ms 27466/45351 (61%) [ 5] 55.00-56.00 sec 15.7 MBytes 131 Mbits/sec 0.022 ms 23613/39662 (60%) [ 5] 56.00-57.00 sec 17.2 MBytes 144 Mbits/sec 0.021 ms 25759/43385 (59%) [ 5] 57.00-58.00 sec 17.6 MBytes 148 Mbits/sec 0.039 ms 26184/44224 (59%) [ 5] 58.00-59.00 sec 17.1 MBytes 143 Mbits/sec 0.039 ms 25165/42639 (59%) [ 5] 59.00-60.00 sec 17.1 MBytes 143 Mbits/sec 0.035 ms 25107/42587 (59%) [ 5] 60.00-61.00 sec 16.5 MBytes 139 Mbits/sec 0.022 ms 24500/41414 (59%) [ 5] 61.00-62.00 sec 16.9 MBytes 142 Mbits/sec 0.031 ms 26566/43878 (61%) - - - - - - - - - - - - - - - - - - - - - - - - - Test Complete. Summary Results: [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-62.00 sec 2.53 GBytes 351 Mbits/sec 0.000 ms 0/2648005 (0%) sender [ 5] 0.00-62.00 sec 1.01 GBytes 139 Mbits/sec 0.031 ms 1593012/2648005 (60%) receiver CPU Utilization: local/receiver 41.6% (15.0%u/26.7%s), remote/sender 19.9% (2.1%u/17.8%s) Server output: Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 2 seconds, 62 second test [ ID] Interval Transfer Bandwidth Total Datagrams [ 5] 0.00-2.00 sec 80.2 MBytes 336 Mbits/sec 82132 (omitted) [ 5] 0.00-2.00 sec 83.4 MBytes 350 Mbits/sec 85406 [ 5] 2.00-4.00 sec 83.4 MBytes 350 Mbits/sec 85452 [ 5] 4.00-6.00 sec 83.6 MBytes 350 Mbits/sec 85568 [ 5] 6.00-8.00 sec 83.3 MBytes 349 Mbits/sec 85261 [ 5] 8.00-10.00 sec 83.5 MBytes 350 Mbits/sec 85489 [ 5] 10.00-12.00 sec 83.7 MBytes 351 Mbits/sec 85747 [ 5] 12.00-14.00 sec 83.3 MBytes 350 Mbits/sec 85338 [ 5] 14.00-16.00 sec 83.4 MBytes 350 Mbits/sec 85431 [ 5] 16.00-18.00 sec 83.4 MBytes 350 Mbits/sec 85374 [ 5] 18.00-20.00 sec 83.3 MBytes 350 Mbits/sec 85330 [ 5] 20.00-22.00 sec 83.5 MBytes 350 Mbits/sec 85469 [ 5] 22.00-24.00 sec 83.5 MBytes 350 Mbits/sec 85546 [ 5] 24.00-26.00 sec 83.3 MBytes 349 Mbits/sec 85311 [ 5] 26.00-28.00 sec 83.7 MBytes 351 Mbits/sec 85679 [ 5] 28.00-30.00 sec 83.4 MBytes 350 Mbits/sec 85357 [ 5] 30.00-32.00 sec 83.3 MBytes 349 Mbits/sec 85281 [ 5] 32.00-34.00 sec 83.5 MBytes 350 Mbits/sec 85499 [ 5] 34.00-36.00 sec 83.5 MBytes 350 Mbits/sec 85504 [ 5] 36.00-38.00 sec 83.6 MBytes 350 Mbits/sec 85570 [ 5] 38.00-40.00 sec 83.5 MBytes 350 Mbits/sec 85494 [ 5] 40.00-42.00 sec 83.3 MBytes 350 Mbits/sec 85331 [ 5] 42.00-44.00 sec 83.5 MBytes 350 Mbits/sec 85520 [ 5] 44.00-46.00 sec 83.5 MBytes 350 Mbits/sec 85488 [ 5] 46.00-48.00 sec 83.4 MBytes 350 Mbits/sec 85358 [ 5] 48.00-50.00 sec 83.5 MBytes 350 Mbits/sec 85505 [ 5] 50.00-52.00 sec 83.3 MBytes 349 Mbits/sec 85284 [ 5] 52.00-54.00 sec 83.5 MBytes 350 Mbits/sec 85532 [ 5] 54.00-56.00 sec 83.3 MBytes 349 Mbits/sec 85293 [ 5] 56.00-58.00 sec 83.5 MBytes 350 Mbits/sec 85536 [ 5] 58.00-60.00 sec 83.5 MBytes 350 Mbits/sec 85512 [ 5] 60.00-62.00 sec 83.3 MBytes 350 Mbits/sec 85328 [ 5] 62.00-62.07 sec 4.31 MBytes 491 Mbits/sec 4410 - - - - - - - - - - - - - - - - - - - - - - - - - Test Complete. Summary Results: [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 5] 0.00-62.07 sec 2.53 GBytes 350 Mbits/sec 0.000 ms 0/2653203 (0%) CPU Utilization: local/sender 19.9% (2.1%u/17.8%s), remote/receiver 0.2% (0.1%u/0.1%s) Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 2 seconds, 62 second test, tos 0 [ ID] Interval Transfer Bitrate Total Datagrams [ 5] 0.00-1.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 (omitted) [ 5] 1.00-2.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 (omitted) [ 5] 0.00-1.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 1.00-2.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 2.00-3.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 3.00-4.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 4.00-5.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 5.00-6.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 6.00-7.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 7.00-8.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 8.00-9.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 9.00-10.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 10.00-11.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 11.00-12.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 12.00-13.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 13.00-14.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 14.00-15.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 15.00-16.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 16.00-17.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 17.00-18.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 18.00-19.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 19.00-20.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 20.00-21.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 21.00-22.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 22.00-23.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 23.00-24.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 24.00-25.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 25.00-26.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 26.00-27.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 27.00-28.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 28.00-29.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 29.00-30.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 30.00-31.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 31.00-32.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 32.00-33.00 sec 2.38 MBytes 20.0 Mbits/sec 2439 [ 5] 33.00-34.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 34.00-35.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 35.00-36.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 36.00-37.00 sec 2.38 MBytes 20.0 Mbits/sec 2438 [ 5] 37.00-38.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 38.00-39.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 39.00-40.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 40.00-41.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 41.00-42.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 42.00-43.00 sec 2.39 MBytes 20.0 Mbits/sec 2444 [ 5] 43.00-44.00 sec 2.38 MBytes 20.0 Mbits/sec 2438 [ 5] 44.00-45.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 45.00-46.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 46.00-47.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 47.00-48.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 48.00-49.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 49.00-50.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 50.00-51.00 sec 2.38 MBytes 20.0 Mbits/sec 2439 [ 5] 51.00-52.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 52.00-53.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 53.00-54.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 54.00-55.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 55.00-56.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 56.00-57.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 57.00-58.00 sec 2.38 MBytes 20.0 Mbits/sec 2442 [ 5] 58.00-59.00 sec 2.38 MBytes 20.0 Mbits/sec 2440 [ 5] 59.00-60.00 sec 2.38 MBytes 20.0 Mbits/sec 2441 [ 5] 60.00-61.00 sec 2.39 MBytes 20.0 Mbits/sec 2443 [ 5] 61.00-62.00 sec 2.38 MBytes 20.0 Mbits/sec 2439 - - - - - - - - - - - - - - - - - - - - - - - - - Test Complete. Summary Results: [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams [ 5] 0.00-62.00 sec 148 MBytes 20.0 Mbits/sec 0.000 ms 0/151367 (0%) sender [ 5] 0.00-62.00 sec 148 MBytes 20.0 Mbits/sec 0.437 ms 28/151347 (0.019%) receiver CPU Utilization: local/sender 0.2% (0.0%u/0.2%s), remote/receiver 2.4% (0.3%u/2.1%s) Server Output: Starting Test: protocol: UDP, 1 streams, 1024 byte blocks, omitting 2 seconds, 62 second test [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 5] 0.00-2.00 sec 4.58 MBytes 19.2 Mbits/sec 0.484 ms 2/4693 (0.043%) (omitted) [ 5] 0.00-2.00 sec 4.77 MBytes 20.0 Mbits/sec 0.543 ms 0/4887 (0%) [ 5] 2.00-4.00 sec 4.77 MBytes 20.0 Mbits/sec 0.488 ms 0/4885 (0%) [ 5] 4.00-6.00 sec 4.77 MBytes 20.0 Mbits/sec 0.482 ms 0/4886 (0%) [ 5] 6.00-8.00 sec 4.77 MBytes 20.0 Mbits/sec 0.533 ms 0/4880 (0%) [ 5] 8.00-10.00 sec 4.76 MBytes 20.0 Mbits/sec 0.749 ms 3/4877 (0.062%) [ 5] 10.00-12.00 sec 4.77 MBytes 20.0 Mbits/sec 0.543 ms 0/4884 (0%) [ 5] 12.00-14.00 sec 4.77 MBytes 20.0 Mbits/sec 0.429 ms 0/4889 (0%) [ 5] 14.00-16.00 sec 4.76 MBytes 20.0 Mbits/sec 0.429 ms 0/4878 (0%) [ 5] 16.00-18.00 sec 4.76 MBytes 20.0 Mbits/sec 0.503 ms 3/4881 (0.061%) [ 5] 18.00-20.00 sec 4.77 MBytes 20.0 Mbits/sec 0.500 ms 3/4888 (0.061%) [ 5] 20.00-22.00 sec 4.77 MBytes 20.0 Mbits/sec 0.539 ms 2/4882 (0.041%) [ 5] 22.00-24.00 sec 4.76 MBytes 20.0 Mbits/sec 0.470 ms 0/4878 (0%) [ 5] 24.00-26.00 sec 4.77 MBytes 20.0 Mbits/sec 0.548 ms 3/4891 (0.061%) [ 5] 26.00-28.00 sec 4.76 MBytes 20.0 Mbits/sec 0.743 ms 0/4876 (0%) [ 5] 28.00-30.00 sec 4.77 MBytes 20.0 Mbits/sec 0.515 ms 2/4885 (0.041%) [ 5] 30.00-32.00 sec 4.77 MBytes 20.0 Mbits/sec 0.487 ms 0/4889 (0%) [ 5] 32.00-34.00 sec 4.76 MBytes 20.0 Mbits/sec 0.693 ms 0/4875 (0%) [ 5] 34.00-36.00 sec 4.76 MBytes 20.0 Mbits/sec 0.499 ms 3/4880 (0.061%) [ 5] 36.00-38.00 sec 4.78 MBytes 20.0 Mbits/sec 0.545 ms 0/4894 (0%) [ 5] 38.00-40.00 sec 4.76 MBytes 20.0 Mbits/sec 0.480 ms 0/4877 (0%) [ 5] 40.00-42.00 sec 4.76 MBytes 20.0 Mbits/sec 0.448 ms 0/4879 (0%) [ 5] 42.00-44.00 sec 4.77 MBytes 20.0 Mbits/sec 0.536 ms 0/4889 (0%) [ 5] 44.00-46.00 sec 4.76 MBytes 20.0 Mbits/sec 0.432 ms 3/4879 (0.061%) [ 5] 46.00-48.00 sec 4.77 MBytes 20.0 Mbits/sec 0.576 ms 0/4885 (0%) [ 5] 48.00-50.00 sec 4.77 MBytes 20.0 Mbits/sec 0.430 ms 2/4883 (0.041%) [ 5] 50.00-52.00 sec 4.76 MBytes 20.0 Mbits/sec 0.451 ms 2/4878 (0.041%) [ 5] 52.00-54.00 sec 4.77 MBytes 20.0 Mbits/sec 0.426 ms 0/4880 (0%) [ 5] 54.00-56.00 sec 4.78 MBytes 20.0 Mbits/sec 0.470 ms 0/4895 (0%) [ 5] 56.00-58.00 sec 4.76 MBytes 20.0 Mbits/sec 0.676 ms 0/4873 (0%) [ 5] 58.00-60.00 sec 4.77 MBytes 20.0 Mbits/sec 0.467 ms 0/4884 (0%) [ 5] 60.00-62.00 sec 4.78 MBytes 20.0 Mbits/sec 0.485 ms 0/4891 (0%) [ 5] 62.00-62.07 sec 159 KBytes 18.6 Mbits/sec 0.437 ms 0/159 (0%) - - - - - - - - - - - - - - - - - - - - - - - - - Test Complete. Summary Results: [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 5] 0.00-62.07 sec 0.00 Bytes 0.00 bits/sec 0.437 ms 26/151537 (0.017%) CPU Utilization: local/receiver 2.4% (0.3%u/2.1%s), remote/sender 41.6% (15.0%u/26.7%s)
on 04-05-2018 15:23
So far, things are looking good, but it's back to PingPlotter for better or worse!
I start with ICMP, given that we know this is fixed, it gives us a 'best case' scenario for TCP. (sorry, the information view was missing, I didn't realise when I screenshotted, but the latency timeline is there)
I then hit TCP, held onto the chair and click start. I set port to 80 and pointed again at google, this time using the 0.03 timing settings posted by Xymox:
As you can see the huge spikes are nowhere to be seen.
To make sure I wasn't just missing the spikes with my timings, I run it at 0.01
I'm not sure what else I can run, but as you can see, things look... well about as normal as they can be! Whilst the screenshot is of a 60 second period I looked at this over 10 minutes (yeah, I know it's short, but so is my time).
So... despite people posting round the forums stating that this would never be fixed as fact, it shows that Horseman's favourite saying 'absence of proof isn't proof of absence' seems to have prevailed, or at least looks that way.
I quickly scanned and I don't believe any personal data to be on the screenshots and I removed bits from iPerf, but let a mod know if I missed anything.
Enjoy!
P.S. I'm yet to test the DoS on .603
on 04-05-2018 16:00
04-05-2018 17:43 - edited 04-05-2018 17:44
on 04-05-2018 18:33
04-05-2018 21:21 - edited 04-05-2018 21:25
@Guybrush85 wrote:So... despite people posting round the forums stating that this would never be fixed as fact, it shows that Horseman's favourite saying 'absence of proof isn't proof of absence' seems to have prevailed, or at least looks that way.
God bless America. Nothing stimulates proper quality like good old class action lawsuit.
Thanks for the exhaustive testing. Hopefully this will put speculations on dslreports to rest (but who am I kidding 😉 )