| Age | Commit message (Expand) | Author | Files | Lines |
|---|
| 2020-03-27 | add doc/email-backup.md |  Christian Hesse | 1 | -0/+1 |
| 2020-02-28 | global-functions: sort alphabetically | Christian Hesse | 1 | -5/+5 |
| 2020-02-26 | global-functions: merge $LogAnd{Error,Put} to $LogPrintExit ...•••... and fix logging.
Logging with severity from variable (:log $severity ...) is not
possible, this is considered a syntax error. Also the 'workaround' with
parsing code failed with missing message in log.
The reliable code is a lot longer, so merge the two functions to save a
lot of duplicate code.
| Christian Hesse | 1 | -2/+2 |
| 2020-02-26 | global-functions: $LogAndError: add severity | Christian Hesse | 1 | -1/+1 |
| 2020-02-26 | email-backup: use $LogAndError | Christian Hesse | 1 | -2/+2 |
| 2020-01-01 | update copyright for 2020 | Christian Hesse | 1 | -1/+1 |
| 2019-11-21 | {email,upload}-backup: update wording | Christian Hesse | 1 | -1/+2 |
| 2019-09-12 | global-functions: introduce and use $DeviceInfo | Christian Hesse | 1 | -13/+4 |
| 2019-07-24 | email-backup: get values into array | Christian Hesse | 1 | -4/+3 |
| 2019-07-24 | email-backup: get values into array | Christian Hesse | 1 | -4/+3 |
| 2019-07-18 | email-backup: no more than one dot in file name•••Looks like some providers do not allow more than one dot in attachment's
file name to mitigate something like `holiday.png.exe`.
Let's just replace dots with underscores.
Fixes #2
Reported-by: @Kampfwurst
| Christian Hesse | 1 | -1/+3 |
| 2019-06-14 | backup: split off cloud-backup•••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.
change-5 | Christian Hesse | 1 | -41/+16 |
| 2019-05-09 | email-backup: make sure to act on first cloud backup | Christian Hesse | 1 | -2/+2 |
| 2019-04-03 | always write warnings and errors to log | Christian Hesse | 1 | -1/+2 |
| 2019-01-15 | email-backup: silence unwanted output | Christian Hesse | 1 | -1/+1 |
| 2019-01-14 | email-backup: give board name and model | Christian Hesse | 1 | -1/+3 |
| 2019-01-09 | email-backup: be more verbose about attached files and secret key | Christian Hesse | 1 | -4/+9 |
| 2019-01-04 | email-backup: print to update from cloud | Christian Hesse | 1 | -0/+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 | -41/+41 |
| 2019-01-02 | update copyright for 2019 | Christian Hesse | 1 | -1/+1 |
| 2018-12-18 | email-backup: support cloud backup | Christian Hesse | 1 | -7/+29 |
| 2018-12-13 | email-backup: try without delay | Christian Hesse | 1 | -2/+0 |
| 2018-12-12 | email-backup: send backup and config export in one mail | Christian Hesse | 1 | -20/+23 |
| 2018-12-12 | email-backup: export terse | Christian Hesse | 1 | -2/+2 |
| 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/+51 |
Christian Hesse