1. 14 Oct, 2019 1 commit
  2. 12 Sep, 2019 1 commit
  3. 30 Aug, 2019 2 commits
  4. 27 Aug, 2019 1 commit
  5. 19 Jul, 2019 2 commits
  6. 14 Jun, 2019 1 commit
    • Christian Hesse's avatar
      backup: split off cloud-backup · 5101d57d
      Christian Hesse authored
      Currently backup to MikroTik cloud is pretty unreliable and script can
      not catch errors at runtime. Looks like this does not change any time
      soon (Ticket#2019052022003204).
      
      So let's just split off the cloud backup to make sure email backup works
      as expected.
      5101d57d
  7. 05 Apr, 2019 1 commit
  8. 02 Apr, 2019 1 commit
  9. 01 Apr, 2019 1 commit
  10. 04 Jan, 2019 2 commits
    • Christian Hesse's avatar
    • Christian Hesse's avatar
      global: variable names are CamelCase · 870f00bb
      Christian Hesse authored
                  ___  _         ___     __
                 / _ )(_)__ _   / _/__ _/ /_
                / _  / / _ `/  / _/ _ `/ __/
               /____/_/\_, /  /_/ \_,_/\__/
       _       __     /___/       _             __
      | |     / /___ __________  (_)___  ____ _/ /
      | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ /
      | |/ |/ / /_/ / /  / / / / / / / / /_/ /_/
      |__/|__/\__,_/_/  /_/ /_/_/_/ /_/\__, (_)
                                      /____/
      
      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*
      870f00bb
  11. 03 Jan, 2019 2 commits
  12. 02 Jan, 2019 3 commits
  13. 20 Dec, 2018 1 commit
  14. 19 Dec, 2018 2 commits
  15. 18 Dec, 2018 1 commit
  16. 14 Dec, 2018 1 commit
  17. 28 Nov, 2018 1 commit
  18. 26 Nov, 2018 1 commit
  19. 13 Nov, 2018 2 commits
  20. 10 Oct, 2018 1 commit
  21. 09 Oct, 2018 4 commits
  22. 04 Oct, 2018 3 commits
  23. 26 Sep, 2018 1 commit
  24. 13 Sep, 2018 2 commits
  25. 10 Sep, 2018 1 commit
  26. 05 Sep, 2018 1 commit