Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2020-03-27 | add doc/email-backup.md | 1 | -0/+1 | ||
2020-02-28 | global-functions: sort alphabetically | 1 | -5/+5 | ||
2020-02-26 | global-functions: merge $LogAnd{Error,Put} to $LogPrintExit ... | 1 | -2/+2 | ||
... 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. | |||||
2020-02-26 | global-functions: $LogAndError: add severity | 1 | -1/+1 | ||
2020-02-26 | email-backup: use $LogAndError | 1 | -2/+2 | ||
2020-01-01 | update copyright for 2020 | 1 | -1/+1 | ||
2019-11-21 | {email,upload}-backup: update wording | 1 | -1/+2 | ||
2019-09-12 | global-functions: introduce and use $DeviceInfo | 1 | -13/+4 | ||
2019-07-24 | email-backup: get values into array | 1 | -4/+3 | ||
2019-07-24 | email-backup: get values into array | 1 | -4/+3 | ||
2019-07-18 | email-backup: no more than one dot in file name | 1 | -1/+3 | ||
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 | |||||
2019-06-14 | backup: split off cloud-backupchange-5 | 1 | -41/+16 | ||
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. | |||||
2019-05-09 | email-backup: make sure to act on first cloud backup | 1 | -2/+2 | ||
2019-04-03 | always write warnings and errors to log | 1 | -1/+2 | ||
2019-01-15 | email-backup: silence unwanted output | 1 | -1/+1 | ||
2019-01-14 | email-backup: give board name and model | 1 | -1/+3 | ||
2019-01-09 | email-backup: be more verbose about attached files and secret key | 1 | -4/+9 | ||
2019-01-04 | email-backup: print to update from cloud | 1 | -0/+3 | ||
2019-01-04 | global: variable names are CamelCase | 1 | -41/+41 | ||
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ 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-02 | update copyright for 2019 | 1 | -1/+1 | ||
2018-12-18 | email-backup: support cloud backup | 1 | -7/+29 | ||
2018-12-13 | email-backup: try without delay | 1 | -2/+0 | ||
2018-12-12 | email-backup: send backup and config export in one mail | 1 | -20/+23 | ||
2018-12-12 | email-backup: export terse | 1 | -2/+2 | ||
2018-09-27 | start scripts with a magic token / shebang | 1 | -1/+1 | ||
2018-08-24 | add empty comment at first line... | 1 | -0/+1 | ||
... for better formatting in export. | |||||
2018-07-05 | add scripts | 1 | -0/+51 | ||