nanog mailing list archives
RE: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads)
From: "Eric Tykwinski" <eric-list () truenet com>
Date: Fri, 22 Jul 2016 15:42:49 -0400
Jim, No problems, I just knew you were one of the project founders. I found it on the website shortly after posting. My google-fu wasn’t up to par. https://www.bufferbloat.net/projects/cerowrt/wiki/Tests_for_Bufferbloat/ I’m assuming I used the script last time for netperf, but have downloaded Flent to give it a shot. Sincerely, Eric Tykwinski TrueNet, Inc. P: 610-429-8300 __________________________________________________________________________________________ From: gettysjim () gmail com [mailto:gettysjim () gmail com] On Behalf Of Jim Gettys Sent: Friday, July 22, 2016 3:23 PM To: Eric Tykwinski Cc: nanog list; jb; Toke Høiland-Jørgensen; Dave Taht Subject: Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) I don't read this list continually, but do archive it; your note was flagged for me to comment on. On Thu, Jul 21, 2016 at 8:11 PM, Eric Tykwinski <eric-list () truenet com> wrote: This is probably for Jim Gettys directly, but I’m sure most others have input. I could of sworn that that there was some test made to detect it directly on switches and routers? Sort of like iperf, but to test bufferbloat specifically given the OS stack which is going to have issues as well, as shown on bufferbloat.net <http://bufferbloat.net/>. We recommend Toke Høiland-Jørgensen's "flent" https://flent.org/ for testing connections/devices/gear. It uses "netperf" transfers to load the link (by default with 4 simultaneous TCP connections in both directions, IIRC), and then runs another test (by default "ping") at the same time to test the connection under load. Turning on a netperf server is just as easy as turning on an iperf server (and the results are better, and netperf's maintainer responsive). See the documentation/paper on Toke's web site. The "RRUL" test ("Real-Time Response Under Load") is the one we use most/is best shaken down. I'm sure Toke would love help with other tests. Gives you lots of useful graphs, will do diffserv marking, etc...
Current thread:
- Re: Speedtest.net not accessible in Chrome due to deceptive ads, (continued)
- Re: Speedtest.net not accessible in Chrome due to deceptive ads Rubens Kuhl (Jul 20)
- Re: Speedtest.net not accessible in Chrome due to deceptive ads Collin Anderson (Jul 20)
- Re: Speedtest.net not accessible in Chrome due to deceptive ads Antonio Querubin (Jul 20)
- Re: Speedtest.net not accessible in Chrome due to deceptive ads Collin Anderson (Jul 20)
- Re: Speedtest.net not accessible in Chrome due to deceptive ads Livingood, Jason (Jul 22)
- RE: Speedtest.net not accessible in Chrome due to deceptive ads Jacques Latour (Jul 22)
- Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Donn Lasher via NANOG (Jul 21)
- Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Eric Tykwinski (Jul 21)
- Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Jim Gettys (Jul 22)
- RE: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Eric Tykwinski (Jul 22)
- Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Baldur Norddahl (Jul 22)
- Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Jim Gettys (Jul 22)
- Re: I recommend dslreports.com/speedtest these days (was Speedtest.net not accessible in Chrome due to deceptive ads) Jim Gettys (Jul 26)