aboutsummaryrefslogtreecommitdiffstats
path: root/email-backup
AgeCommit message (Collapse)AuthorFilesLines
2020-02-28global-functions: sort alphabeticallyGravatar Christian Hesse1-5/+5
2020-02-26global-functions: merge $LogAnd{Error,Put} to $LogPrintExit ...Gravatar Christian Hesse1-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-26global-functions: $LogAndError: add severityGravatar Christian Hesse1-1/+1
2020-02-26email-backup: use $LogAndErrorGravatar Christian Hesse1-2/+2
2020-01-01update copyright for 2020Gravatar Christian Hesse1-1/+1
2019-11-21{email,upload}-backup: update wordingGravatar Christian Hesse1-1/+2
2019-09-12global-functions: introduce and use $DeviceInfoGravatar Christian Hesse1-13/+4
2019-07-24email-backup: get values into arrayGravatar Christian Hesse1-4/+3
2019-07-24email-backup: get values into arrayGravatar Christian Hesse1-4/+3
2019-07-18email-backup: no more than one dot in file nameGravatar Christian Hesse1-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-14backup: split off cloud-backupchange-5Gravatar Christian Hesse1-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-09email-backup: make sure to act on first cloud backupGravatar Christian Hesse1-2/+2
2019-04-03always write warnings and errors to logGravatar Christian Hesse1-1/+2
2019-01-15email-backup: silence unwanted outputGravatar Christian Hesse1-1/+1
2019-01-14email-backup: give board name and modelGravatar Christian Hesse1-1/+3
2019-01-09email-backup: be more verbose about attached files and secret keyGravatar Christian Hesse1-4/+9
2019-01-04email-backup: print to update from cloudGravatar Christian Hesse1-0/+3
2019-01-04global: variable names are CamelCaseGravatar Christian Hesse1-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-02update copyright for 2019Gravatar Christian Hesse1-1/+1
2018-12-18email-backup: support cloud backupGravatar Christian Hesse1-7/+29
2018-12-13email-backup: try without delayGravatar Christian Hesse1-2/+0
2018-12-12email-backup: send backup and config export in one mailGravatar Christian Hesse1-20/+23
2018-12-12email-backup: export terseGravatar Christian Hesse1-2/+2
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/+51
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-01 16:08:22 +0000