| Age | Commit message (Expand) | Author | Files | Lines |
|---|
| 2019-06-25 | bridge-port-to-default: get bridge port values into array |  Christian Hesse | 1 | -8/+7 |
| 2019-01-04 | 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*
| Christian Hesse | 1 | -15/+15 |
| 2019-01-02 | update copyright for 2019 | Christian Hesse | 1 | -1/+1 |
| 2018-10-25 | bridge-port-to-default: delay only when required | Christian Hesse | 1 | -3/+5 |
| 2018-10-25 | bridge-port-to-default: delay for global-config•••All scripts scheduled with "start-time=startup interval=0" start
simultaneously, thus racing on global variables. So delay for
a second and give global-config time to finish.
| Christian Hesse | 1 | -0/+3 |
| 2018-10-25 | bridge-port-to-default: drop unused code, :toarray strips itself | Christian Hesse | 1 | -3/+0 |
| 2018-10-25 | bridge-port-to-default: fix variable name | Christian Hesse | 1 | -1/+1 |
| 2018-10-04 | bridge-port-to-default: strip leading blank from comment | Christian Hesse | 1 | -0/+3 |
| 2018-10-04 | bridge-port-to-default: support different configurations•••Just add something like this to your bridge ports:
comment="default:br-ext,alt:br-intern"
| Christian Hesse | 1 | -10/+18 |
| 2018-09-27 | start scripts with a magic token / shebang | Christian Hesse | 1 | -1/+1 |
| 2018-08-27 | rename ethernet-to-default -> bridge-port-to-default | Christian Hesse | 1 | -0/+18 |
Christian Hesse