| Age | Commit message (Expand) | Author | Files | Lines |
|---|
| 2019-11-14 | dhcp-to-dns: act on hostname only if available |  Christian Hesse | 1 | -1/+3 |
| 2019-11-12 | dhcp-to-dns: set the temporary variable unconditionally | Christian Hesse | 1 | -4/+1 |
| 2019-11-12 | dhcp-to-dns: handle duplicate mac-address and host-name•••* several leases for one mac address (changed client id, different net):
-> take address from last lease
Most likely this is the same devices which booted different OS or
changed to different network.
* several leases for one host name:
-> take address from first lease
We see either different devices with same name or one device with
several network interfaces. Keep the first name to mitigate stealing
dns name.
| Christian Hesse | 1 | -3/+8 |
| 2019-09-11 | dhcp-to-dns: find duplicate leases by mac-address | Christian Hesse | 1 | -1/+1 |
| 2019-07-25 | dhcp-to-dns: get values into arrays, general rework | Christian Hesse | 1 | -29/+23 |
| 2019-02-08 | dhcp-to-dns: rework, fix cleanup with mac-address and more | Christian Hesse | 1 | -37/+29 |
| 2019-02-08 | dhcp-to-dns: use mac-address if hostname is empty | Christian Hesse | 1 | -0/+3 |
| 2019-02-08 | dhcp-to-dns: use $CharacterReplace | Christian Hesse | 1 | -6/+3 |
| 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 | -48/+48 |
| 2019-01-03 | dhcp-to-dns: give time in short format•••Note that a unit is required to make it a time value!
| Christian Hesse | 1 | -1/+1 |
| 2019-01-02 | update copyright for 2019 | Christian Hesse | 1 | -1/+1 |
| 2018-11-09 | dhcp-to-dns: use 'print count-only' | Christian Hesse | 1 | -1/+1 |
| 2018-09-27 | start scripts with a magic token / shebang | Christian Hesse | 1 | -1/+1 |
| 2018-08-24 | add empty comment at first line...•••... for better formatting in export.
| Christian Hesse | 1 | -0/+1 |
| 2018-07-05 | add scripts | Christian Hesse | 1 | -0/+75 |
Christian Hesse