mirror of
https://github.com/eworm-de/routeros-scripts.git
synced 2024-05-11 05:55:19 +00:00
870f00bb36
___ _ ___ __
/ _ )(_)__ _ / _/__ _/ /_
/ _ / / _ `/ / _/ _ `/ __/
/____/_/\_, / /_/ \_,_/\__/
_ __ /___/ _ __
| | / /___ __________ (_)___ ____ _/ /
| | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ /
| |/ |/ / /_/ / / / / / / / / / / /_/ /_/
|__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_)
/____/
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*
29 lines
1.0 KiB
Plaintext
29 lines
1.0 KiB
Plaintext
#!rsc
|
|
# RouterOS script: manage-umts
|
|
# Copyright (c) 2013-2019 Christian Hesse <mail@eworm.de>
|
|
#
|
|
# manage UMTS interface based on ethernet and wireless status
|
|
|
|
:local EtherInt "en1";
|
|
:local WlanInt "wl-station";
|
|
:local UmtsInt "t-mobile";
|
|
|
|
:local EtherStatus [ / interface ethernet get $EtherInt running ];
|
|
:local WlanStatus [ / interface wireless get $WlanInt running ];
|
|
|
|
:if ($EtherStatus = true || $WlanStatus = true) do={
|
|
:if ([ / interface get $UmtsInt disabled ] = false) do={
|
|
:log info ("Ethernet (" . $EtherInt . " / " . $EtherStatus . ") or " . \
|
|
"wireless (" . $WlanInt . " / " . $WlanStatus . ") is running, " . \
|
|
"UMTS interface " . $UmtsInt . " is enabled. Disabling...");
|
|
/ interface set disabled=yes $UmtsInt;
|
|
}
|
|
} else={
|
|
:if ([ / interface get $UmtsInt disabled ] = true) do={
|
|
:log info ("Neither ethernet (" . $EtherInt . ") nor wireless (" . \
|
|
$WlanInt . ") interface is running, UMTS interface " . $UmtsInt . \
|
|
" is disabled. Enabling...");
|
|
/ interface set disabled=no $UmtsInt;
|
|
}
|
|
}
|