i made a script that do log up/down message using netwatch, that can be used to monitor various thing. Eks WireGuard.
http://forum.mikrotik.com/t/tool-using-splunk-to-analyse-mikrotik-logs-4-0-graphing-everything/153043/3
@rextended posted:
The post I read said this:
This script has been created in ROS 5.12, tested on a 450G
It should work on other devices, and probably other ROS versions too, but I can't say which.
Key words here being "Should work on other devices". In any case I'm just asking if anyone else is using this or if they could shed light on how to troubleshoot this script.
In my case I manually executed the ping command that the script does and it's timing out even though the connection is back up so for some reason the ping is not working through the primary connection when the secondary is active. If I switch the metric manually back from 3 to 1 the primary comes up and works fine so I know it's up. It must be something with the way the routes are set up.
This is the specific line in the script where it pings the host through the primary interface:
:set vPingReturns [/ping $vPingDest interface=$vPrimaryInterface interval=$vPingInterval count=$vPingCount size=$vPingSize];
So I attempted to do the same ping manually by entering this in terminal:
/ping 4.2.2.2 interface=Internet1 interval=300ms count=6 size=64
All pings timed out when secondary is active but are successful when primary is active.
Rich
Anyone?
“Should work on other devices”
Is perfectly obvious that the author, with that, mean also >same RouterOS version<
and
“and probably other ROS versions too”
Is perfectly obvious that the author, with that, mean RouterOS 5.x
last modified, Mar 25 2012 , v1.0.2.4
Tested with ROS 5.12 ONLY, and on a RB450G
The script have just 10 years and 3 months, and is maded for another near completly different RouterOS decades ago…
No one want resume works from another user for corrects obsolete script of which the internal mechanism is knowed only from the original author.
Try to contact the original author, e-mail is inside the file: gregs@sloop.net
If you have nothing constructive to add to the conversation then please just keep your post to yourself. If there is another better way to handle it then I’m all ears - just telling me that the current script is old and won’t work is not helpful.
Anyone ELSE?
Nothing constructive?
I found the author’s email, who can give better support?
After evaluating your reaction, I will directly give you the solution you deserve: install RouterOS 5.12!!! Brilliant isn’t it?
You win.. you got the last word!
Anyone else?
You like waiting, from 26 may to now, and over…
Only bumping this topic you have sufficient visibility to hope that someone do that work for you.
Do not worry, now that I have answered you in that way, for sure there is someone who looks at it…
Well, @rextended always likes to have the last word but I’m not that kind of guy! 