There is no point to see an average of let’s say 98% in a 30-day period if I can’t see when the WAN was down and for how long. Currently we have a connection monitoring script that is not actually monitoring service disruptions and this is the most important piece of information.
Swapped over and ran ping test....got this. Bad number??
Code:
############################################################
## ___ ___ _ __ _ __ _ __ ___ ___ _ __ ##
## / __| / _ \ | '_ \ | '_ \ | '_ _ \ / _ \ | '_ \ ##
## | (__ | (_) || | | || | | || | | | | || (_) || | | | ##
## \___| \___/ |_| |_||_| |_||_| |_| |_| \___/ |_| |_| ##
## ##
## v2.1.1 on RT-AC86U ##
## ##
## https://github.com/jackyaz/connmon ##
## ##
############################################################
1. Check connection now
2. Set preferred ping server
Currently: 8.8.8.8
u. Check for updates
uf. Update connmon with latest version (force update)
e. Exit connmon
z. Uninstall connmon
############################################################
Choose an option: 1
connmon: 30 second ping test to 8.8.8.8 starting...
[: 24.900: bad number
[: 28.953: bad number
[: 24.900: bad number
[: 27.228: bad number
[: 28.953: bad number
[: 27.738: bad number
[: 27.228: bad number
[: 37.369: bad number
[: 27.738: bad number
[: 36.768: bad number
[: 37.369: bad number
[: 35.513: bad number
[: 36.768: bad number
[: 32.252: bad number
[: 35.513: bad number
[: 35.169: bad number
[: 32.252: bad number
[: 34.626: bad number
[: 35.169: bad number
[: 44.109: bad number
[: 34.626: bad number
[: 40.202: bad number
[: 44.109: bad number
[: 40.666: bad number
[: 40.202: bad number
[: 25.743: bad number
[: 40.666: bad number
[: 31.220: bad number
[: 25.743: bad number
[: 35.230: bad number
[: 31.220: bad number
[: 32.776: bad number
[: 35.230: bad number
[: 45.759: bad number
[: 32.776: bad number
[: 34.240: bad number
[: 45.759: bad number
[: 27.680: bad number
[: 34.240: bad number
[: 25.980: bad number
[: 27.680: bad number
[: 25.416: bad number
[: 25.980: bad number
[: 33.598: bad number
[: 25.416: bad number
[: 31.860: bad number
[: 33.598: bad number
[: 44.251: bad number
[: 31.860: bad number
[: 24.092: bad number
[: 44.251: bad number
[: 22.952: bad number
[: 24.092: bad number
[: 27.545: bad number
[: 22.952: bad number
[: 24.846: bad number
[: 27.545: bad number
[: 37.567: bad number
[: 24.846: bad number
connmon: Test results - Ping 32.541 ms - Jitter - 5.592 ms - Line Quality 100.00 0 %
The router crapped out. One day decided to boot loop for no reason. This thing is fragile. Running now bare bones, no scripts, no 3rd party software. So far so good. I'm sure people here will help you to make this script better. Thank you for sharing your work.
Swapped over and ran ping test....got this. Bad number??
Code:
############################################################
## ___ ___ _ __ _ __ _ __ ___ ___ _ __ ##
## / __| / _ \ | '_ \ | '_ \ | '_ _ \ / _ \ | '_ \ ##
## | (__ | (_) || | | || | | || | | | | || (_) || | | | ##
## \___| \___/ |_| |_||_| |_||_| |_| |_| \___/ |_| |_| ##
## ##
## v2.1.1 on RT-AC86U ##
## ##
## https://github.com/jackyaz/connmon ##
## ##
############################################################
1. Check connection now
2. Set preferred ping server
Currently: 8.8.8.8
u. Check for updates
uf. Update connmon with latest version (force update)
e. Exit connmon
z. Uninstall connmon
############################################################
Choose an option: 1
connmon: 30 second ping test to 8.8.8.8 starting...
[: 24.900: bad number
[: 28.953: bad number
[: 24.900: bad number
[: 27.228: bad number
[: 28.953: bad number
[: 27.738: bad number
[: 27.228: bad number
[: 37.369: bad number
[: 27.738: bad number
[: 36.768: bad number
[: 37.369: bad number
[: 35.513: bad number
[: 36.768: bad number
[: 32.252: bad number
[: 35.513: bad number
[: 35.169: bad number
[: 32.252: bad number
[: 34.626: bad number
[: 35.169: bad number
[: 44.109: bad number
[: 34.626: bad number
[: 40.202: bad number
[: 44.109: bad number
[: 40.666: bad number
[: 40.202: bad number
[: 25.743: bad number
[: 40.666: bad number
[: 31.220: bad number
[: 25.743: bad number
[: 35.230: bad number
[: 31.220: bad number
[: 32.776: bad number
[: 35.230: bad number
[: 45.759: bad number
[: 32.776: bad number
[: 34.240: bad number
[: 45.759: bad number
[: 27.680: bad number
[: 34.240: bad number
[: 25.980: bad number
[: 27.680: bad number
[: 25.416: bad number
[: 25.980: bad number
[: 33.598: bad number
[: 25.416: bad number
[: 31.860: bad number
[: 33.598: bad number
[: 44.251: bad number
[: 31.860: bad number
[: 24.092: bad number
[: 44.251: bad number
[: 22.952: bad number
[: 24.092: bad number
[: 27.545: bad number
[: 22.952: bad number
[: 24.846: bad number
[: 27.545: bad number
[: 37.567: bad number
[: 24.846: bad number
connmon: Test results - Ping 32.541 ms - Jitter - 5.592 ms - Line Quality 100.00 0 %
Swapped over and ran ping test....got this. Bad number??
Code:
############################################################
## ___ ___ _ __ _ __ _ __ ___ ___ _ __ ##
## / __| / _ \ | '_ \ | '_ \ | '_ _ \ / _ \ | '_ \ ##
## | (__ | (_) || | | || | | || | | | | || (_) || | | | ##
## \___| \___/ |_| |_||_| |_||_| |_| |_| \___/ |_| |_| ##
## ##
## v2.1.1 on RT-AC86U ##
## ##
## https://github.com/jackyaz/connmon ##
## ##
############################################################
1. Check connection now
2. Set preferred ping server
Currently: 8.8.8.8
u. Check for updates
uf. Update connmon with latest version (force update)
e. Exit connmon
z. Uninstall connmon
############################################################
Choose an option: 1
connmon: 30 second ping test to 8.8.8.8 starting...
[: 24.900: bad number
[: 28.953: bad number
[: 24.900: bad number
[: 27.228: bad number
[: 28.953: bad number
[: 27.738: bad number
[: 27.228: bad number
[: 37.369: bad number
[: 27.738: bad number
[: 36.768: bad number
[: 37.369: bad number
[: 35.513: bad number
[: 36.768: bad number
[: 32.252: bad number
[: 35.513: bad number
[: 35.169: bad number
[: 32.252: bad number
[: 34.626: bad number
[: 35.169: bad number
[: 44.109: bad number
[: 34.626: bad number
[: 40.202: bad number
[: 44.109: bad number
[: 40.666: bad number
[: 40.202: bad number
[: 25.743: bad number
[: 40.666: bad number
[: 31.220: bad number
[: 25.743: bad number
[: 35.230: bad number
[: 31.220: bad number
[: 32.776: bad number
[: 35.230: bad number
[: 45.759: bad number
[: 32.776: bad number
[: 34.240: bad number
[: 45.759: bad number
[: 27.680: bad number
[: 34.240: bad number
[: 25.980: bad number
[: 27.680: bad number
[: 25.416: bad number
[: 25.980: bad number
[: 33.598: bad number
[: 25.416: bad number
[: 31.860: bad number
[: 33.598: bad number
[: 44.251: bad number
[: 31.860: bad number
[: 24.092: bad number
[: 44.251: bad number
[: 22.952: bad number
[: 24.092: bad number
[: 27.545: bad number
[: 22.952: bad number
[: 24.846: bad number
[: 27.545: bad number
[: 37.567: bad number
[: 24.846: bad number
connmon: Test results - Ping 32.541 ms - Jitter - 5.592 ms - Line Quality 100.00 0 %
Had to do some changes recently, the router was reset.
First time installation, uninstall after, reinstall in few days - previous installation weekly and monthly logs are still there.
Had to do some changes recently, the router was reset.
First time installation, uninstall after, reinstall in few days - previous installation weekly and monthly logs are still there.
gotchya. it might be intended for those who wish to reinstall, but if you select to completely remove it should be completely removing them. @Jack Yaz This may be Jacks way for saving the number of read and writes on JFFS partition.... THINK green Jack think green.....
Idk if its possible, but could you add support for us to be able to monitor 2 or 3 ips at the same time with graphs? At least 2 instead of the only 1 that we have today... i would like to monitor one internal ip(in other words, from inside my country) and another one external ip(in other words, an overseas ip)
@Jack Yaz - would you consider having a prompt/option for the frequency of testing (similar to setting the ping server option)? Rather than every 5, I prefer every 15 or 30. I edit the script by hand (cru a line) but need to remember to do that with every update and then reboot (or restart cron). Best regards,
@Jack Yaz - would you consider having a prompt/option for the frequency of testing (similar to setting the ping server option)? Rather than every 5, I prefer every 15 or 30. I edit the script by hand (cru a line) but need to remember to do that with every update and then reboot (or restart cron). Best regards,
Idk if its possible, but could you add support for us to be able to monitor 2 or 3 ips at the same time with graphs? At least 2 instead of the only 1 that we have today... i would like to monitor one internal ip(in other words, from inside my country) and another one external ip(in other words, an overseas ip)
I know this was just updated, but will a future version of this include the ability to change the ping test duration and frequency? For me, 5-10s every 30-60min is plenty of data
I know this was just updated, but will a future version of this include the ability to change the ping test duration and frequency? For me, 5-10s every 30-60min is plenty of data
You can also 1) edit the script to make the frequency less-frequent (edit the cru a line) and restart or reboot
or 2) edit the cron job directly (this sets the job up to run every 15 minutes):
Terminate the current job: cru d connmon_daily
Create a new cron job: cru a connmon_daily "*/15 * * * * /jffs/scripts/connmon generate daily"
You can add these commands to one of the startup scripts if you want to automate it.
RMerlin tweeted just the other day that certain things are going to be GUI configurable in the nearish future, if I recall and understood correctly, with Diversion leading the way. I’m hoping Jack’s scripts will be as well.