aboutsummaryrefslogtreecommitdiffstats
path: root/script-updates
AgeCommit message (Expand)AuthorFilesLines
2019-04-01script-updates: add changelog for global configurationchange-2change-1Gravatar Christian Hesse1-1/+22
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-44/+44
2019-01-03script-updates: add configuration versioningGravatar Christian Hesse1-0/+13
2019-01-02update copyright for 2019Gravatar Christian Hesse1-1/+1
2018-10-16script-updates: run global-functions on updateGravatar Christian Hesse1-0/+3
2018-10-12script-updates: allow to set dont-require-permissions=yes•••This requires the new script to contain a line: # requires: dont-require-permissions=yes Gravatar Christian Hesse1-1/+4
2018-09-28script-updates: make sure new script starts with magicGravatar Christian Hesse1-5/+9
2018-09-27start scripts with a magic token / shebangGravatar Christian Hesse1-1/+1
2018-09-14script-updates: add error handling back in•••We have to make sure the script does not terminate on first error... Gravatar Christian Hesse1-7/+9
2018-09-13script-updates: check and warn about policiesGravatar Christian Hesse1-0/+10
2018-09-03script-updates: fetch into variablerouteros-6.43Gravatar Christian Hesse1-13/+16
2018-08-27script-updates: add support for url suffix•••This allows to fetch from different branch... Gravatar Christian Hesse1-1/+2
2018-08-24add empty comment at first line...•••... for better formatting in export. Gravatar Christian Hesse1-0/+1
2018-07-10script-updates: always accept updates from fileGravatar Christian Hesse1-33/+25
2018-07-09script-updates: handle error on fetchGravatar Christian Hesse1-4/+8
2018-07-09script-updates: check certificate on fetchGravatar Christian Hesse1-1/+3
2018-07-09script-updates: support fetch from urlGravatar Christian Hesse1-9/+40
2018-07-05add scriptsGravatar Christian Hesse1-0/+17