aboutsummaryrefslogtreecommitdiffstats
path: root/capsman-download-packages
AgeCommit message (Collapse)AuthorFilesLines
2023-01-02update copyright for 2023Gravatar Christian Hesse1-1/+1
2022-07-21capsman-download-packages: use proper array syntaxGravatar Christian Hesse1-1/+1
2022-05-11capsman-download-packages: RouterOS v7 path syntaxGravatar Christian Hesse1-13/+13
2022-04-07capsman-download-packages: break long linesGravatar Christian Hesse1-2/+4
2022-04-07capsman-download-packages: try to warn about missing logsGravatar Christian Hesse1-3/+9
2022-03-25capsman-download-packages: get info from logGravatar Christian Hesse1-0/+19
Relying on older packages in local storage may be problematic due to size constraints. Let's check the log for required packages.
2022-02-10capsman-download-packages: wireless package does no longer existGravatar Christian Hesse1-3/+0
This is a RouterOS v7 only change!
2022-01-01update copyright for 2022Gravatar Christian Hesse1-1/+1
2021-02-24global: use $0 for $ScriptLockGravatar Christian Hesse1-1/+1
2021-02-24global: give script or function name in log messagesGravatar Christian Hesse1-4/+5
2021-02-21capsman-download-packages: give more context in outputGravatar Christian Hesse1-2/+2
2021-02-21capsman-download-packages: complain on undefined pathGravatar Christian Hesse1-0/+4
2021-02-18global: drop script 'global-wait'change-44Gravatar Christian Hesse1-0/+3
All scripts wait for the global functions on their own now.
2021-01-20capsman-download-packages: handle error when creating directoryGravatar Christian Hesse1-1/+4
2021-01-01update copyright for 2021Gravatar Christian Hesse1-1/+1
2020-09-18extend magic pattern with "by RouterOS"Gravatar Christian Hesse1-1/+1
This matches the string included in export.
2020-08-26[ ... print count-only ...] -> [ :len [ ... find ... ] ]Gravatar Christian Hesse1-2/+2
Using 'print count-only' always prints a number to terminal, even if the value is evaluated in a condition or assigned to a variable. This can be quite annoying. Behavior will not chance (SUP-25503), so replacing the code...
2020-07-14capsman-download-packages: wait to be fully connectedGravatar Christian Hesse1-0/+2
2020-06-19explicitly name the licenseGravatar Christian Hesse1-0/+1
Copyright (C) 2013-2020 Christian Hesse <mail@eworm.de> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. https://www.gnu.org/licenses/#GPL https://www.gnu.org/licenses/gpl.html https://www.gnu.org/licenses/gpl.md
2020-04-06capsman-download-packages: create package pathGravatar Christian Hesse1-0/+8
2020-03-27add doc/capsman-download-packages.mdGravatar Christian Hesse1-0/+1
2020-01-01update copyright for 2020Gravatar Christian Hesse1-1/+1
2019-12-05capsman-download-packages: lock against multiple invocationGravatar Christian Hesse1-1/+4
2019-08-02capsman-download-packages: syntax error with missing parenthesisGravatar Christian Hesse1-1/+1
2019-07-25capsman-download-packages: get values into arrayGravatar Christian Hesse1-7/+6
2019-07-18capsman-download-packages: do not require extra permissionGravatar Christian Hesse1-2/+0
The idea was to run capsman-download-packages from netwatch when upgrade.mikrotik.com is up. Instead run it from scheduler at startup, but add a delay: / system scheduler add name=capsman-download-packages \ on-event=":delay 2m; capsman-download-packages" start-time=startup
2019-02-14capsman-download-packages: split off capsman-rolling-upgradeGravatar Christian Hesse1-8/+5
2019-02-13capsman-download-packages: use $CleanFilePathGravatar Christian Hesse1-4/+2
2019-02-07capsman-download-packages: upgrade CAPs one after another with delayGravatar Christian Hesse1-2/+9
2019-01-04global: variable names are CamelCaseGravatar Christian Hesse1-18/+18
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ 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-02capsman-download-packages: use upgrade command to force remote-cap upgradeGravatar Michael Gisbers1-1/+1
Signed-off-by: Michael Gisbers <michael@gisbers.de> Signed-off-by: Christian Hesse <mail@eworm.de>
2019-01-02update copyright for 2019Gravatar Christian Hesse1-2/+2
2018-12-28global-functions: add $DownloadPackageGravatar Christian Hesse1-8/+5
... and make script 'capsman-download-packages' use it.
2018-12-28capsman-download-packages: move condition to loopGravatar Christian Hesse1-17/+16
2018-12-27capsman-download-packages: act in package-path onlyGravatar Christian Hesse1-1/+4
2018-12-27capsman-download-packages: do not restart service...Gravatar Christian Hesse1-2/+2
... but disconnect old CAPs and force reconnect with update.
2018-12-27capsman-download-packages: rewrite package-name from wireless@ to wirelessGravatar Michael Gisbers1-0/+4
Signed-off-by: Michael Gisbers <michael@gisbers.de> Signed-off-by: Christian Hesse <mail@eworm.de>
2018-12-27add script 'capsman-download-packages'Gravatar Christian Hesse1-0/+34