aboutsummaryrefslogtreecommitdiffstats
path: root/sms-forward
AgeCommit message (Collapse)AuthorFilesLines
2020-07-17sms-forward: use $SymbolByUnicodeNameGravatar Christian Hesse1-1/+2
2020-07-16sms-forward: add symbolGravatar Christian Hesse1-1/+1
2020-07-14sms-forward: wait to be fully connectedGravatar Christian Hesse1-1/+3
2020-06-19explicitly name the licenseGravatar Christian Hesse1-0/+1
Copyright (C) 2013-2020 Christian Hesse <mail@eworm.de> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. https://www.gnu.org/licenses/#GPL https://www.gnu.org/licenses/gpl.html https://www.gnu.org/licenses/gpl.md
2020-05-17sms-forward: warn and exit if receiving is not enabledGravatar Christian Hesse1-0/+4
2020-04-03sms-forward: use $LogPrintExitGravatar Christian Hesse1-1/+1
2020-03-27add doc/sms-forward.mdGravatar Christian Hesse1-0/+1
2020-02-28global-functions: sort alphabeticallyGravatar Christian Hesse1-2/+2
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-26sms-forward: use $LogAndErrorGravatar Christian Hesse1-2/+2
2020-02-24sms-forward: use $MailServerIsUpGravatar Christian Hesse1-1/+2
2020-01-01update copyright for 2020Gravatar Christian Hesse1-1/+1
2019-08-08sms-forward: add sender in subjectGravatar Christian Hesse1-1/+1
2019-08-05sms-forward: fix array access in conditionGravatar Christian Hesse1-1/+2
2019-07-25sms-forward: get values into arraysGravatar Christian Hesse1-8/+5
2019-04-05sms-forward: group messages for same senderGravatar Christian Hesse1-15/+26
2019-04-03always write warnings and errors to logGravatar Christian Hesse1-1/+2
2019-01-04global: variable names are CamelCaseGravatar Christian Hesse1-15/+15
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ 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-11-28global-functions: add identity tag in $SendNotificationGravatar Christian Hesse1-1/+1
... and send subject in telegram message.
2018-10-10global: remove unused variablesGravatar Christian Hesse1-2/+0
2018-10-09sms-forward: use function for notificationGravatar Christian Hesse1-3/+4
2018-09-27start scripts with a magic token / shebangGravatar Christian Hesse1-1/+1
2018-09-23sms-forward: make handling of SMS with action more robustGravatar Christian Hesse1-9/+17
2018-08-24add empty comment at first line...Gravatar Christian Hesse1-0/+1
... for better formatting in export.
2018-08-06add script 'sms-action'Gravatar Christian Hesse1-1/+1
2018-08-06rename forward-sms -> sms-forwardGravatar Christian Hesse1-0/+29
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-18 15:35:18 +0000