Doc Searls mentioned in passing that he uses a new speed test website. I checked it out, and it was very cool… www.speedof.me is an all-HTML5 website that seems to make accurate measurements of the up and download speeds of your internet connection. It’s also very attractive, and the real-time plots of the speed show
I posted a set of scripts that people can use to test, configure and debug their CeroWrt router installations. CeroWrt router firmware is a test bed for learning about and eliminating bufferbloat. The scripts are available on Github at https://github.com/richb-hanover/CeroWrtScripts. They include: betterspeedtest.sh – a script that emulates the famous (but limited) speedtest.net. This script
I created an InterMapper probe that detects whether a web server is vulnerable to the Heartbleed bug. You can read about it on my Blueberry Hill Software blog at: http://blueberryhillsoftware.com/heartbleed-probe-for-intermapper/
I took the time to incorporate the feedback from my previous post to load the newest CeroWrt firmware and re-run the tests. This image gallery shows the results of the RRUL performance tests. There’s a lot of analysis in the note on the CeroWrt-devel mailing list at: https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-March/002396.html
RRUL charts [Note: This is an earlier result. Check out the subsequent posting for CeroWrt 3.10.28-16 (above)] The postings below are a series of charts that were created by the netperf-wrapper program. Note: I don’t know why the upload charts show such fragmentary data. All charts made with default Queue Discipline: fq_codel, simple.qos script, ingress
Very close to sync rate (7600/800 kbps) on ge00. Two other variations – slightly below (7400/800) and slightly too high (7800/800)
95% readings (7325/821 kbps) on ge00.
90% readings (6854/777 kbps) on ge00.
90% down, 95% up (6473/777 kbps) on ge00.
Update: Good news! I am now able to get onto the 5GHz SSIDs. What changed? I rebooted my router, and it now seems OK. So I may have cried Wolf about this problem, and incorrectly blamed Mavericks. The problem seems to have gone away after the router reboot. Whew! I still don’t know why I got