The preview bar on the right shows gaps where no ping response was received. A screenshot of a text file showing the results of a ping every minute. This is the result, and you can already see some outages in the preview strip in the right-hand side in Visual Studio Code. I'm pulling out the second line of the output (the important one), prepending the current time, and appending it to the pingtest.txt file. In short, I'm running a single ping of maximum size against. * * * * * ping -c 1 -s 65507 | head -n 2 | tail -n 1 | perl -nli 'print scalar(localtime), ": ", $_' > /home/pi/pingtest.txt I could do a speed test more often (and I might if I'm not getting the details I expect), but I figured a ping every minute would be enough to at least see those additional drops.Īgain, a straight ping will give me plenty of details, but they're not terribly parseable if appended to a file.Ī bit of google-binging led me to this solution: # large ping every minute I mentioned, however, that the dropouts were only for a few minutes at a time, so there's a good chance I'll miss some if I'm only testing every 15min. The result (after running it for a while) is a nicely parseable csv file! A screenshot of a spreadsheet showing details from an Ookla speed test every 15min # run this every 15minĠ,15,30,45 * * * * /usr/local/bin/speedtest -csv > /home/pi/speedtest-track.csv One sticking point I encountered (thanks Vaughan Knight for helping diagnose) - you'll need the full path to both the CLI and the output file in your cron job. You can set this up with the crontab -e command. Now to set up a cron job to do it every 15 minutes. Then, to test it out, I ran a speedtest with the -csv argument, appending to that file: speedtest-cli -csv > speedtest-track.csv Thankfully, the CLI has a couple of arguments that will help populate a CSV, and you can use standard shell features to append to a file.įirst, I created a new CSV file with headers using the -csv-header argument and piping to a new file: speedtest-cli -csv-header > speedtest-track.csv but it's not very parsable if you want to keep track over a period of time. Once installed, if you run speedtest from your commandline, you get a nice result. On my Pi running Rasbian, I installed that fairly simply with easy_install: sudo easy_install speedtest-cli I wanted something pretty simple, so I just set up a couple of cron jobs on a Raspberry Pi - using the Ookla Speedtest CLI, and a standard ping.įirst, I needed the Speedtest CLI. Presumably in a couple of days I'll be able to hand the files to so they can hound about mini dropouts.- Damian Brady □ #BLM September 7, 2020 Thanks to and others, I now have a raspberry pi set up to do a speed test every 15min, and a ping every 1min. Instead, I implemented something in the middle - albeit a bit closer to the former. Suggestions ranged from just keeping a ping running on a laptop, to setting up an end-to-end tracing solution using half a dozen Azure resources and client applications. This suggestion was echoed by a number of friends and colleagues. They know NBN won't do anything without proof. They can track outages, but there's only so much they can see from their end. An "outage" is something longer, and it's really only outages that matter.Īfter a swathe of other troubleshooting attempts, one of the representatives at Aussie Broadband (and I want to be clear - I love Aussie) suggested I keep my own records. The trouble is, I'm told NBN (Australia's National Broadband Network) doesn't see them as serious enough to trigger a response. I think Aussie Broadband (my provider) calls them "flaps", and according to their app, I've had 150 of them in the last 8 days. Just enough to stop me in my tracks and force me onto a tethered mobile phone connection. Only a handful of times per day, and usually only for a few minutes at a time. In summary, I've been getting really short drop-outs semi-regularly. I need to prove it.- Damian Brady □ #BLM September 3, 2020 but apparently not enough visible ones that will do anything. Time to get out a Raspberry Pi and set up some stuff to continuously test my Internet.īecause I'm getting dropouts. Update: I wrote a little script to do a regular HTTP GET and ran the tests again over a weekend. Why yes, I am in Australia! Funny you ask! Menu Tracking my Internet with a Raspberry Pi 08 September 2020 on Internet, NBN, RaspberryPi
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |