2020-09-18 09:00:27 +00:00
|
|
|
#!rsc by RouterOS
|
2018-12-27 00:51:43 +00:00
|
|
|
# RouterOS script: capsman-download-packages
|
2021-01-01 20:33:52 +00:00
|
|
|
# Copyright (c) 2018-2021 Christian Hesse <mail@eworm.de>
|
2019-01-01 20:19:19 +00:00
|
|
|
# Michael Gisbers <michael@gisbers.de>
|
2020-06-19 20:17:42 +00:00
|
|
|
# https://git.eworm.de/cgit/routeros-scripts/about/COPYING.md
|
2018-12-27 00:51:43 +00:00
|
|
|
#
|
|
|
|
# download and cleanup packages for CAP installation from CAPsMAN
|
2020-03-27 20:40:02 +00:00
|
|
|
# https://git.eworm.de/cgit/routeros-scripts/about/doc/capsman-download-packages.md
|
2018-12-27 00:51:43 +00:00
|
|
|
|
2021-02-18 13:52:47 +00:00
|
|
|
:global GlobalFunctionsReady;
|
|
|
|
:while ($GlobalFunctionsReady != true) do={ :delay 500ms; }
|
|
|
|
|
2019-02-13 08:44:45 +00:00
|
|
|
:global CleanFilePath;
|
2019-12-05 08:48:50 +00:00
|
|
|
:global DownloadPackage;
|
2020-04-06 09:51:33 +00:00
|
|
|
:global LogPrintExit;
|
|
|
|
:global MkDir;
|
2019-12-05 08:48:50 +00:00
|
|
|
:global ScriptLock;
|
2020-07-14 12:29:29 +00:00
|
|
|
:global WaitFullyConnected;
|
2019-12-05 08:48:50 +00:00
|
|
|
|
|
|
|
$ScriptLock "capsman-download-packages";
|
2020-07-14 12:29:29 +00:00
|
|
|
$WaitFullyConnected;
|
2018-12-27 00:51:43 +00:00
|
|
|
|
2019-02-13 08:44:45 +00:00
|
|
|
:local PackagePath [ $CleanFilePath [ / caps-man manager get package-path ] ];
|
global: 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*
2019-01-03 16:45:43 +00:00
|
|
|
:local InstalledVersion [ / system package update get installed-version ];
|
|
|
|
:local Updated false;
|
2018-12-27 00:51:43 +00:00
|
|
|
|
2020-08-26 07:23:56 +00:00
|
|
|
:if ([ :len [ / file find where name=$PackagePath type="directory" ] ] = 0) do={
|
2021-01-20 13:43:27 +00:00
|
|
|
:if ([ $MkDir $PackagePath ] = false) do={
|
|
|
|
$LogPrintExit warning ("Creating directory at package path (" . \
|
|
|
|
$PackagePath . ") failed!") true;
|
|
|
|
}
|
2020-04-06 09:51:33 +00:00
|
|
|
$LogPrintExit info ("Created directory at package path (" . $PackagePath . \
|
|
|
|
"). Please place your packages!") false;
|
|
|
|
}
|
|
|
|
|
global: 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*
2019-01-03 16:45:43 +00:00
|
|
|
:foreach Package in=[ / file find where type=package \
|
|
|
|
package-version!=$InstalledVersion name~("^" . $PackagePath) ] do={
|
2019-07-25 08:35:15 +00:00
|
|
|
:local File [ / file get $Package ];
|
|
|
|
:if ($File->"package-architecture" = "mips") do={
|
|
|
|
:set ($File->"package-architecture") "mipsbe";
|
2018-12-27 00:51:43 +00:00
|
|
|
}
|
2019-07-25 08:35:15 +00:00
|
|
|
:if ($File->"package-name" = "wireless@") do={
|
|
|
|
:set ($File->"package-name") "wireless";
|
2018-12-28 17:50:22 +00:00
|
|
|
}
|
2019-08-02 13:22:17 +00:00
|
|
|
:if ([ $DownloadPackage ($File->"package-name") $InstalledVersion ($File->"package-architecture") $PackagePath ] = true) do={
|
global: 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*
2019-01-03 16:45:43 +00:00
|
|
|
:set Updated true;
|
|
|
|
/ file remove $Package;
|
2018-12-28 18:30:15 +00:00
|
|
|
}
|
2018-12-27 00:51:43 +00:00
|
|
|
}
|
|
|
|
|
2019-02-14 19:49:05 +00:00
|
|
|
:if ($Updated = true) do={
|
2020-08-26 07:23:56 +00:00
|
|
|
:if ([ :len [ / system script find where name="capsman-rolling-upgrade" ] ] > 0) do={
|
2019-02-14 19:49:05 +00:00
|
|
|
/ system script run capsman-rolling-upgrade;
|
|
|
|
} else={
|
|
|
|
/ caps-man remote-cap upgrade [ find where version!=$InstalledVersion ];
|
2019-02-07 10:04:15 +00:00
|
|
|
}
|
2018-12-27 00:51:43 +00:00
|
|
|
}
|