aboutsummaryrefslogtreecommitdiffstats
path: root/check-routeros-update
AgeCommit message (Collapse)AuthorFilesLines
2020-02-26global-functions: $LogAndError: add severityGravatar Christian Hesse1-2/+2
2020-02-26check-routeros-update: use $LogAndErrorGravatar Christian Hesse1-4/+3
2020-01-16check-routeros-update: do not act if reboot is scheduledGravatar Christian Hesse1-0/+4
2020-01-01update copyright for 2020Gravatar Christian Hesse1-1/+1
2019-12-03check-routeros-update: use $ScriptFromTerminalGravatar Christian Hesse1-1/+2
2019-09-12global-functions: introduce and use $DeviceInfoGravatar Christian Hesse1-10/+2
2019-08-18check-routeros-update: make notifications silentGravatar Christian Hesse1-2/+3
2019-08-08check-routeros-update: fail on empty version stringGravatar Christian Hesse1-0/+5
2019-07-24check-routeros-update: get values into arrayGravatar Christian Hesse1-4/+3
2019-07-24check-routeros-update: get values into arrayGravatar Christian Hesse1-21/+19
2019-07-01check-routeros-update: link a changelog that opens in browserGravatar Christian Hesse1-1/+1
The old link was delivered with MIME type 'application/octet-stream', browsers wanted to download it as file.
2019-05-23check-routeros-update: drop literal 'notification'Gravatar Christian Hesse1-4/+4
2019-04-03always write warnings and errors to logGravatar Christian Hesse1-2/+4
2019-03-29check-routeros-update: link to changelog in notificationGravatar Christian Hesse1-1/+2
2019-02-22check-routeros-update: default in capital letterGravatar Christian Hesse1-1/+1
Also use square brackets as RouterOS does.
2019-02-21check-routeros-update: allow interactive update from terminalGravatar Christian Hesse1-6/+19
2019-02-19check-routeros-update: give board name and modelGravatar Christian Hesse1-1/+3
2019-02-19check-routeros-update: use new script 'packages-update'Gravatar Christian Hesse1-4/+5
2019-02-19check-routeros-update: run installation without-pagingGravatar Christian Hesse1-1/+1
2019-01-18check-routeros-update: run email-backup on auto-updateGravatar Christian Hesse1-0/+3
2019-01-04global: variable names are CamelCaseGravatar Christian Hesse1-28/+28
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ RouterOS has some odd behavior when it comes to variable names. Let's have a look at the interfaces: [admin@MikroTik] > / interface print where name=en1 Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 That looks ok. Now we use a script: { :local interface "en1"; / interface print where name=$interface; } And the result... [admin@MikroTik] > { :local interface "en1"; {... / interface print where name=$interface; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 ... still looks ok. We make a little modification to the script: { :local name "en1"; / interface print where name=$name; } And the result: [admin@MikroTik] > { :local name "en1"; {... / interface print where name=$name; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 1 S en2 ether 1500 1598 2 S en3 ether 1500 1598 3 S en4 ether 1500 1598 4 S en5 ether 1500 1598 5 R br-local bridge 1500 1598 Ups! The filter has no effect! That happens whenever the variable name ($name) matches the property name (name=). And another modification: { :local type "en1"; / interface print where name=$type; } And the result: [admin@MikroTik] > { :local type "en1"; {... / interface print where name=$type; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU Ups! Nothing? Even if the variable name ($type) matches whatever property name (type=) things go wrong. The answer from MikroTik support (in Ticket#2019010222000454): > This is how scripting works in RouterOS and we will not fix it. To get around this we use variable names in CamelCase. Let's hope Mikrotik never ever introduces property names in CamelCase... *fingers crossed*
2019-01-02check-routeros-update: be more verbose on errorGravatar Christian Hesse1-1/+1
2019-01-02check-routeros-update: do not fail if safe-update-url return errorGravatar Christian Hesse1-6/+11
We still want the notification...
2019-01-02update copyright for 2019Gravatar Christian Hesse1-1/+1
2018-11-28global-functions: add identity tag in $SendNotificationGravatar Christian Hesse1-2/+2
... and send subject in telegram message.
2018-11-09check-routeros-update: use 'print count-only'Gravatar Christian Hesse1-1/+1
2018-10-10global: remove unused variablesGravatar Christian Hesse1-2/+0
2018-10-10check-routeros-update: send notification on auto-updateGravatar Christian Hesse1-0/+3
2018-10-09check-routeros-update: use function for notificationGravatar Christian Hesse1-3/+4
2018-09-27start scripts with a magic token / shebangGravatar Christian Hesse1-1/+1
2018-09-20check-routeros-update: add missing space, break lineGravatar Christian Hesse1-1/+2
2018-09-19check-routeros-update: send versions to safe-update-urlGravatar Christian Hesse1-1/+2
2018-09-05check-routeros-update: enable auto update for safe versionGravatar Christian Hesse1-4/+15
2018-08-30check-routeros-update: resend notification if version changesGravatar Christian Hesse1-11/+9
2018-08-24add empty comment at first line...Gravatar Christian Hesse1-0/+1
... for better formatting in export.
2018-07-09check-routeros-update: make the checks fool-proofGravatar Christian Hesse1-2/+3
2018-07-05add scriptsGravatar Christian Hesse1-0/+42
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-15 23:09:39 +0000