mirror of
https://github.com/eworm-de/routeros-scripts
synced 2024-05-14 08:04: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*
26 lines
792 B
Text
26 lines
792 B
Text
#!rsc
|
|
# RouterOS script: gps-track
|
|
# Copyright (c) 2018-2019 Christian Hesse <mail@eworm.de>
|
|
#
|
|
# track gps data by sending json data to http server
|
|
|
|
:global Identity;
|
|
:global GpsTrackUrl;
|
|
|
|
:local Gps [ / system gps monitor once as-value ];
|
|
|
|
if ($Gps->"valid" = true) do={
|
|
:tool fetch mode=https check-certificate=yes-without-crl \
|
|
$GpsTrackUrl keep-result=no \
|
|
http-method=post http-content-type="application/json" \
|
|
http-data=("{" . \
|
|
"\"lat\":\"" . ($Gps->"latitude") . "\"," . \
|
|
"\"lon\":\"" . ($Gps->"longitude") . "\"," . \
|
|
"\"identity\":\"" . $Identity . "\"" . \
|
|
"}");
|
|
:log debug ("Sending GPS data for tracking: " . \
|
|
"lat: " . ($Gps->"latitude") . " " . \
|
|
"lon: " . ($Gps->"longitude"));
|
|
} else={
|
|
:log debug ("GPS data not valid.");
|
|
}
|