I was thinking of creating a package or something that ran on a Raspberry Pi that monitored your internet connection. Basically you would configure to say, monitoring your public school website, Google, your router, your server(s), email then it'll give you a simple status web page that would display if the services are ok or if they are degraded (poor response time\random packet loss).
It would be alerting, but that might be a bit difficult informing your ISP that your internet is down, if your internet down, but it could send an email for degrades and post-outages. I think the key thing would be reporting. I know from the support side, you have problems tracking down "random" issues if the customer is vague. Also it gives you a better position if you've got hard facts, ie it's not my switch, it's the LAN port on your router.
I think it's important it's a device on the network that could be plugged in anywhere as this will give you an actual real-world status, also it needs to be on a non-live system so it can't impact it. Benefit of the Raspberry Pi is that it's fairly cheap, low power and small - so you could hide it in some office at the other end of the school.
Good idea? Already been done?
Output the results of the BASH script to an auto refresh HTML page.
Sorry, was thinking user friendly as in easy to configure rather then output.
It's most likely going to be a bash script, it's about my limit when it comes to linux!! Unless I outsource it...
How would it get the data? SNMP? or were you thinking of actually plugging it into the network and having it monitor packets flowing though it? (Store and forward). If the later, the Pi will be seriously underpowered for this job.
fping google. (good bad ugly )
fping router ( good bad ugly )
fping website ( good bad ugly )
time download 4mb file from website.
Push to html.
Yer, like @twin--turbo, just basic ping, http responses, maybe a few others like dns. Wouldn't bother with SNMP, it'll only be good for your internal network as it'll be blocked outside of your network. If that's what you wanted you'd use nagios or something. Network traffic would be wireshark but that's pretty hardcore, I mean you don't need to sniff the network to know you've got loopback!! So that's out.
PS: Not sure, Pi is pretty good with streams of data, it's only an issue if you want to start capturing it.
There are currently 1 users browsing this thread. (0 members and 1 guests)