mirror of
https://github.com/eworm-de/routeros-scripts.git
synced 2025-08-03 17:54:47 +02:00
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*
This commit is contained in:
parent
7d06a7e8c2
commit
870f00bb36
41 changed files with 770 additions and 777 deletions
|
@ -4,13 +4,13 @@
|
|||
#
|
||||
# enable or disable ip addresses based on bridge port state
|
||||
|
||||
:foreach bridge in=[ / interface bridge find ] do={
|
||||
:local brname [ / interface bridge get $bridge name ];
|
||||
:if ([ / interface bridge port print count-only where bridge=$brname ] > 0) do={
|
||||
:if ([ / interface bridge port print count-only where bridge=$brname and inactive=no ] = 0) do={
|
||||
/ ip address disable [ find where !dynamic interface=$brname ];
|
||||
:foreach Bridge in=[ / interface bridge find ] do={
|
||||
:local BrName [ / interface bridge get $Bridge name ];
|
||||
:if ([ / interface bridge port print count-only where bridge=$BrName ] > 0) do={
|
||||
:if ([ / interface bridge port print count-only where bridge=$BrName and inactive=no ] = 0) do={
|
||||
/ ip address disable [ find where !dynamic interface=$BrName ];
|
||||
} else={
|
||||
/ ip address enable [ find where !dynamic interface=$brname ];
|
||||
/ ip address enable [ find where !dynamic interface=$BrName ];
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue