aboutsummaryrefslogtreecommitdiffstats
path: root/dhcp-to-dns
AgeCommit message (Collapse)AuthorFilesLines
2019-11-12dhcp-to-dns: handle duplicate mac-address and host-nameGravatar Christian Hesse1-3/+8
* 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.
2019-09-11dhcp-to-dns: find duplicate leases by mac-addressGravatar Christian Hesse1-1/+1
2019-07-25dhcp-to-dns: get values into arrays, general reworkGravatar Christian Hesse1-29/+23
2019-02-08dhcp-to-dns: rework, fix cleanup with mac-address and moreGravatar Christian Hesse1-37/+29
2019-02-08dhcp-to-dns: use mac-address if hostname is emptyGravatar Christian Hesse1-0/+3
2019-02-08dhcp-to-dns: use $CharacterReplaceGravatar Christian Hesse1-6/+3
2019-01-04global: variable names are CamelCaseGravatar Christian Hesse1-48/+48
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ 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*
2019-01-03dhcp-to-dns: give time in short formatGravatar Christian Hesse1-1/+1
Note that a unit is required to make it a time value!
2019-01-02update copyright for 2019Gravatar Christian Hesse1-1/+1
2018-11-09dhcp-to-dns: use 'print count-only'Gravatar Christian Hesse1-1/+1
2018-09-27start scripts with a magic token / shebangGravatar Christian Hesse1-1/+1
2018-08-24add empty comment at first line...Gravatar Christian Hesse1-0/+1
... for better formatting in export.
2018-07-05add scriptsGravatar Christian Hesse1-0/+75
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-14 16:16:08 +0000