My quality Graph History
-
Fun to look at one's history.
Monitoring my link got boring, so I switched to Google's public servers. They were quite noisy, which was annoying, but towards the end there was those two large bursts of loss. The was the end of my limit. My connection was fine, just their servers or my path to them was unstable. I looked for a more stable alternative that was a public server. That's when I noticed Level3's DNS servers.
About once a year, my ISP does unannounced maintenance that lasts 5-15 minutes around 1am-3am, causing my link to go down. When this happens, DPinger throws a fit and doesn't restart itself. I hadn't looked at my quality graphs in a long while before I noticed the issue. Restarted the service.
-
I never have to restart dpinger.
-
I don't know the exact events that occur that lead to this situation, all I know is the Internet is working but dpinger effectively stopped.
-
Is it still running in Status > Services ?
-
I think so. Which is why it shows 100% loss and not nothing.
-
hmm. I would expect to see sendto errors in the system log or something in that case.
-
Not sure the best way to search back to July in the logs via the UI, assuming the data is still there. pfSense has ~245 days of uptime, so if the data is in memory…..
-
245 days uptime… So not current version then... Running 2.3? with no updates?
-
Nice catch.
