routeros-scripts - RouterOS Scripts

Age	Commit message (Collapse)	Author	Files	Lines
2024-03-03	netwatch-notify: check one after another	Christian Hesse	1	-2/+5
	This can bring an extra delay, but saves a check in most cases.
2024-03-02	netwatch-notify: handle IPv6 / AAAA resolving	Christian Hesse	1	-1/+3

2024-03-01	netwatch-notify: (mis-)use firewall address-list for lookup...	Christian Hesse	1	-11/+5
	... and drop the racy code querying dns cache. 😁
2024-02-28	netwatch-notify: handle CNAME to multiple records	Christian Hesse	1	-0/+9

2024-02-28	netwatch-notify: move check in DNS cache to local function	Christian Hesse	1	-2/+14

2024-02-28	netwatch-notify: try another workaround	Christian Hesse	1	-4/+2
	The last one did not make it... Perhaps the cache just needs a moment to settle?
2024-02-28	netwatch-notify: work around race condition	Christian Hesse	1	-8/+12
	This used to crash every now and then with: > script;error script error: no such item (4) I guess this is caused by querying the dns cache just exactly when a record expires. The chance is maximized: The script is started by scheduler every minute, and the record's ttl is a multiple of a minute. Let's query records that are not about to expire immediately, and try again.
2024-02-28	netwatch-notify: restore the check 🥴	Christian Hesse	1	-1/+2
	This reverts commit 28da1da49e275fef6089a103edf6c158bbff317f. Chances are that we have to resolve a CNAME, that does not match when querying the cache. How to handle CNAME do multiple A records? 🤨
2024-02-28	netwatch-notify: simplify the check	Christian Hesse	1	-2/+1

2024-02-28	netwatch-notify: ... and switch state to "unknown" on host update	Christian Hesse	1	-0/+1

2024-02-28	netwatch-notify: handle status "down" in its own condition...	Christian Hesse	1	-1/+4
	... instead of else-branch. This makes sure to skip hosts that just became "unknown". (Possible soon!)
2024-02-28	netwatch-notify: use logical operator, no literal "and"	Christian Hesse	1	-1/+1
	Just like we do everywhere else.
2024-02-19	netwatch-notify: do not update with record in cache	Christian Hesse	1	-1/+2
	Using `:resolve` we have just one address, but chances are several records do exist. These end up in cache, so we are happy to find them there - no need to update then.
2024-01-30	netwatch-notify: use :jobname to get script name	Christian Hesse	1	-1/+3

2024-01-01	update copyright for 2024	Christian Hesse	1	-1/+1

2023-10-27	netwatch-notify: match on word boundary	Christian Hesse	1	-1/+1

2023-09-29	netwatch-notify: allow to give different origin for hosts...	Christian Hesse	1	-6/+4
	... to use differing notification settings. Add an origin name in netwatch configuration: /tool/netwatch/add comment="notify, name=dns-google, origin=netwatch-notify-google" address=8.8.8.8; /tool/netwatch/add comment="notify, name=dns-cloudflare, origin=netwatch-notify-cloudflare" address=1.1.1.1; Then configure the notification settings in `global-config-overlay`: :global EmailGeneralToOverride { "netwatch-notify-google"="google@example.com"; "netwatch-notify-cloudflare"="cloudflare@example.com"; } I think it is best to handle this as a hidden setting... Handle with care!
2023-08-18	netwatch-notify: drop RouterOS version dependency	Christian Hesse	1	-2/+0
	... as global-functions depend on RouterOS 7.9beta already.
2023-06-28	netwatch-notify: drop the delay on startup...routeros-7.9beta4-6	Christian Hesse	1	-4/+2
	... now that in RouterOS 7.9 netwatch itself comes with a startup-delay. Hosts in state 'unknown' are just ignored.
2023-05-31	netwatch-notify: ignore status 'unknown'	Christian Hesse	1	-1/+1

2023-03-20	netwatch-notify: support note in notificationchange-96	Christian Hesse	1	-0/+6

2023-03-07	rename scripts and add file extension ".rsc"change-95	Christian Hesse	1	-0/+186
	No functional change for the user... The migration is done automatically.