aboutsummaryrefslogtreecommitdiffstats
path: root/capsman-download-packages
AgeCommit message (Expand)AuthorFilesLines
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 CamelCase••• ___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ 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* Gravatar Christian Hesse1-18/+18
2019-01-02capsman-download-packages: use upgrade command to force remote-cap upgrade•••Signed-off-by: Michael Gisbers <michael@gisbers.de> Signed-off-by: Christian Hesse <mail@eworm.de> Gravatar Michael Gisbers1-1/+1
2019-01-02update copyright for 2019Gravatar Christian Hesse1-2/+2
2018-12-28global-functions: add $DownloadPackage•••... and make script 'capsman-download-packages' use it. Gravatar Christian Hesse1-8/+5
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...•••... but disconnect old CAPs and force reconnect with update. Gravatar Christian Hesse1-2/+2
2018-12-27capsman-download-packages: rewrite package-name from wireless@ to wireless•••Signed-off-by: Michael Gisbers <michael@gisbers.de> Signed-off-by: Christian Hesse <mail@eworm.de> Gravatar Michael Gisbers1-0/+4
2018-12-27add script 'capsman-download-packages'Gravatar Christian Hesse1-0/+34