1. 13 Jun, 2019 1 commit
  2. 30 Apr, 2019 1 commit
    • Christian Hesse's avatar
      global-functions: add $WaitForFile, wait for file on fetch · 7f96e5c9
      Christian Hesse authored
      The fetch command is asynchronous, the file is not guaranteed to be
      available when command terminates.
      
      I opened an issue at Mikrotik support (Ticket#2019041722004999),
      their answer:
      
      > You should perform a check in a loop.
      > :delay until file exist
      >
      > That can happen also with any configuration not just files.
      
      So add a function to wait for a file with given name.
      
      I have not seen this with other configuration, though.
      7f96e5c9
  3. 09 Apr, 2019 1 commit
  4. 03 Apr, 2019 1 commit
  5. 06 Mar, 2019 2 commits
  6. 09 Jan, 2019 1 commit
  7. 04 Jan, 2019 1 commit
    • 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
  8. 02 Jan, 2019 1 commit
  9. 12 Dec, 2018 1 commit
  10. 28 Nov, 2018 1 commit
  11. 15 Oct, 2018 1 commit
  12. 12 Oct, 2018 1 commit
  13. 10 Oct, 2018 3 commits
  14. 09 Oct, 2018 1 commit
  15. 26 Sep, 2018 1 commit
  16. 24 Aug, 2018 1 commit
  17. 05 Jul, 2018 1 commit