Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
7 days | Merge branch 'check-health' into nextHEADnextmain | 4 | -13/+16 | ||
8 days | check-health.d/voltage: use script name for origin in notification | 1 | -4/+5 | ||
8 days | check-health.d/temperature: use script name for origin in notification | 1 | -3/+4 | ||
8 days | check-health.d/state: use script name for origin in notification | 1 | -3/+4 | ||
8 days | check-health: pass script name to plugin | 1 | -1/+1 | ||
8 days | check-health: fix variable name | 1 | -2/+2 | ||
2025-08-16 | global-functions: $CertificateAvailable: properly handle duplicate CN | 1 | -0/+5 | ||
There are CA certificates with identical CommonName out there... 🤪 Let's handle these. [admin@MikroTik] > /certificate/print proplist=common-name,skid where common-name="GlobalSign"; Flags: T - TRUSTED Columns: COMMON-NAME, SKID # COMMON-NAME SKID 0 T GlobalSign 8FF04B7FA82E4524AE4D50FA639A8BDEE2DD1BBC 1 T GlobalSign 3DE629489BEA07CA21444A26DE6EDED283D09F59 2 T GlobalSign AE6C05A39313E2A2E7E2D71CD6C7F07FC86753A0 3 T GlobalSign 54B07BAD45B8E2407FFB0A6EFBBE33C93CA384D5 | |||||
2025-07-28 | global-functions: $SymbolByUnicodeName: allow to add more symbols... | 1 | -2/+4 | ||
... for example from a module. Add a script `mod/symbols-extra` with something like: :global SymbolsExtra; :set ($SymbolsExtra->"rocket") "\F0\9F\9A\80"; | |||||
2025-07-21 | netwatch-notify: increase the address-list timeout even further | 1 | -2/+2 | ||
2025-07-21 | netwatch-notify: give the number of failures... | 1 | -1/+1 | ||
... to indicated this happened several times. | |||||
2025-07-07 | accesslist-duplicates: print without paging | 4 | -6/+6 | ||
2025-06-25 | netwatch-dns: fix indention | 1 | -1/+1 | ||
2025-06-25 | netwatch-dns: retry doh server... | 1 | -5/+7 | ||
... for more resilience on bad connectivity or saturated link. | |||||
2025-06-23 | Merge branch 'file' into nextrouteros-7.20beta4-1 | 1 | -4/+22 | ||
2025-06-23 | global-functions: $FileGet: mitigate race with file properties | 1 | -0/+6 | ||
RouterOS is suffering a race condition, where a file exists, but its properties are not (yet) available. This is handled in $WaitForFile. This passes an interval of zero to $WaitForFile, as does not wait for the file to exist, but wants to avoid the race only. | |||||
2025-06-23 | global-functions: $WaitForFile: (mostly) revert changes | 1 | -4/+16 | ||
This (mostly) reverts commits 0e00a228d67d77fadc80eee2df04c2cec25b8db8 and e08bb2192dfd22b25652553f28304818a3602331. This is required for RouterOS 7.20beta4. That fixed recursive find for files, and (again, or still?) suffers timing (and thus racing) issues getting file properties. This breaks RouterOS 7.20beta2 again, so that specific version is not supported. Just update... | |||||
2025-06-20 | packages-update: convert to time before comparing... | 1 | -2/+3 | ||
... to avoid: packages-update: Script 'packages-update' exited with error: Script Error: cannot compare if truth value is more than or equal to ip address | |||||
2025-06-11 | doc/fw-addr-lists: add a warning on possible subsystem crash | 1 | -1/+4 | ||
2025-06-11 | fw-addr-lists: delay on possible scripting subsystem crash | 1 | -0/+6 | ||
This happens in :convert when a list is way too large. Let's use $LogPrintOnce here. If the scripting subsystem really crashes the message will be purged from $LogPrintOnceMessages anyway (as all global variables are lost). | |||||
2025-06-11 | capsman-download-packages: revert changes for "new functionality" | 4 | -13/+13 | ||
(Though we keep the quoting for type.) Well, turned out this functionality is for `/file/print` only, but does not work with `/file/find`. 🫣🥴 This reverts commit 15fd522d3db507cc7c22af9cd59ff85d41a5be6f. | |||||
2025-06-04 | update list of contributors | 1 | -0/+1 | ||
2025-06-04 | check-routeros-update: remove a stale scheduler | 1 | -3/+9 | ||
2025-06-04 | packages-update: support deferred reboot with longer interval | 2 | -5/+10 | ||
2025-06-04 | Merge branch 'file' into nextrouteros-7.20beta2-1 | 9 | -67/+107 | ||
2025-06-04 | capsman-download-packages: adopt new functionality from file menu | 4 | -13/+13 | ||
2025-06-04 | capsman-download-packages: use $FileGet ... | 3 | -3/+6 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | telegram-chat: use $FileExists ... | 1 | -1/+2 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | mod/ssh-keys-import: use $FileExists ... | 1 | -2/+2 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | mod/notification-email: use $RmFile | 1 | -1/+2 | ||
2025-06-04 | mod/notification-email: use $FileExists ... | 1 | -1/+2 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | backup-email: add a comment why files are not removed | 1 | -0/+1 | ||
2025-06-04 | backup-email: check for .conf file | 1 | -1/+2 | ||
2025-06-04 | backup-email: use :retry and $FileExists ... | 1 | -10/+11 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | global-functions: $DownloadPackage: use $FileExists ... | 1 | -2/+3 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | global-functions: introduce $FileExists | 1 | -0/+24 | ||
2025-06-04 | global-functions: $WaitForFile: use :retry for simplification, ... | 1 | -8/+6 | ||
... and to work around restrictions in new file handling. | |||||
2025-06-04 | global-functions: $WaitForFile: drop the workaroundrouteros-7.18rc1-2 | 1 | -9/+0 | ||
This was fixed in RouterOS 7.18rc1, so should be ok to remove now. | |||||
2025-06-04 | global-functions: $RmFile: use $FileGet ... | 1 | -9/+10 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | global-functions: $RmDir: use $FileGet ... | 1 | -9/+10 | ||
... to work around restrictions in new file handling. | |||||
2025-06-04 | global-functions: $MkDir: use $FileGet ... | 1 | -1/+3 | ||
... to work around restrictions in new file handling. | |||||
2025-06-03 | global-functions: introduce $FileGet | 1 | -0/+13 | ||
2025-06-03 | Merge branch 'builtin-certs' into next | 3 | -11/+32 | ||
2025-06-03 | INITIAL-COMMANDS: use builtin certificates if possible | 1 | -10/+16 | ||
2025-05-28 | global-functions: $CertificateAvailable: try to use builtin certificates | 1 | -0/+5 | ||
The builtin certificates were introduced with RouterOS 7.19, so requires this hacky :parse workaround. | |||||
2025-05-28 | README: add a paragraph and link to jump | 1 | -2/+5 | ||
2025-05-28 | README: give a hint on builtin certificate store | 1 | -1/+8 | ||
I guess this should become the default any time in future... | |||||
2025-05-23 | telegram-chat: rename variable... | 1 | -2/+2 | ||
... to better describe the use. | |||||
2025-05-23 | telegram-chat: fix detection of replies | 1 | -1/+1 | ||
2025-05-23 | global-functions: $ScriptInstallUpdate: fix syntax error | 1 | -1/+1 | ||
2025-05-23 | fix the trust state for certificatesrouteros-7.19-1change-138 | 2 | -1/+3 | ||
RouterOS 7.19 is suffering an issue with certificate store, where the trust state is not available correctly. This effects certificates imported a long time ago, with RouterOS 7.4 or older. Fixing trust state for all certificates by re-setting the trust state... (Reported as SUP-188791...) | |||||
2025-05-22 | DEBUG: fix typo | 1 | -1/+1 | ||
2025-05-22 | telegram-chat: support debug output for updates in JSON | 1 | -0/+3 | ||
2025-05-22 | telegram-chat: support trusted group chat ids | 1 | -1/+3 | ||
But be warned: Adding a person to a trusted group will give her/him administrative control over the device(s) - without changes on the device itself! On the other hand... Removing permissions is easily done by removing a person from a group. Closes: https://github.com/eworm-de/routeros-scripts/issues/101 | |||||
2025-05-22 | mod/notification-telegram: fix indention | 1 | -1/+1 | ||
2025-05-22 | fw-addr-lists: for IPv6 the CIDR is always expected | 1 | -2/+2 | ||
2025-05-22 | mod/notification-email: add the link symbol | 1 | -1/+2 | ||
2025-05-22 | mod/notification-email: properly truncate the body | 1 | -3/+13 | ||
Truned out that the size limit for e-mail message/body is anywhere just below 64kB... So truncate at about 62.000 bytes. | |||||
2025-05-22 | mod/notification-email: add error handling when sending mail | 1 | -25/+30 | ||
2025-05-22 | mod/inspectvar: replace only when matching | 1 | -1/+6 | ||
2025-05-22 | mod/inspectvar: remove CR, replace LF | 1 | -0/+2 | ||
2025-05-22 | mod/inspectvar: print the length for strings | 1 | -0/+5 | ||
2025-05-22 | mod/inspectvar: use $CharacterMultiply | 1 | -5/+3 | ||
2025-05-22 | Merge branch 'onerror' into next | 23 | -174/+175 | ||
2025-05-22 | update-tunnelbroker: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-22 | unattended-lte-firmware-upgrade: :do ... on-error=... -> :onerror ... do=... | 1 | -6/+6 | ||
2025-05-22 | telegram-chat: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-22 | sms-forward: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-22 | netwatch-notify: :do ... on-error=... -> :onerror ... do=... | 1 | -6/+6 | ||
2025-05-22 | netwatch-dns: :do ... on-error=... -> :onerror ... do=... | 1 | -4/+4 | ||
2025-05-22 | mod/ssh-keys-import: :do ... on-error=... -> ... well... - fix condition 🥴 | 1 | -3/+1 | ||
2025-05-21 | mod/ssh-keys-import: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | mod/scriptrunonce: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | mode-button: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | mod/notification-gotify: :do ... on-error=... -> :onerror ... do=... | 1 | -6/+6 | ||
2025-05-21 | mod/notification-matrix: :do ... on-error=... -> :onerror ... do=... | 1 | -21/+21 | ||
2025-05-21 | mod/notification-ntfy: :do ... on-error=... -> :onerror ... do=... | 1 | -6/+6 | ||
2025-05-21 | mod/notification-telegram: :do ... on-error=... -> :onerror ... do=... | 1 | -9/+9 | ||
2025-05-21 | lease-script: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | gps-track: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-functions: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-functions: $ValidateSyntax: add debug output | 1 | -0/+3 | ||
2025-05-21 | global-functions: $ValidateSyntax: :do ... on-error=... -> :onerror ... do=... | 1 | -2/+2 | ||
2025-05-21 | global-functions: $ScriptInstallUpdate: :do ... on-error=... -> :onerror ... ↵ | 1 | -15/+13 | ||
do=... | |||||
2025-05-21 | global-functions: $RmFile: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-functions: $RmDir: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-functions: $MkDir: :do ... on-error=... -> :onerror ... do=... | 1 | -6/+6 | ||
2025-05-21 | global-functions: $GetMacVendor: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-functions: $FetchHuge: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-functions: $DownloadPackage: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | global-config: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | fw-addr-lists: adopt changes in wording... | 1 | -12/+12 | ||
... to match the changes from previous commit. | |||||
2025-05-21 | fw-addr-lists: :do ... on-error=... -> :onerror ... do=... | 1 | -8/+8 | ||
2025-05-21 | check-routeros-update: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | check-lte-firmware-upgrade: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | check-health: :do ... on-error=... -> :onerror ... do=... | 1 | -3/+3 | ||
2025-05-21 | backup-upload: :do ... on-error=... -> :onerror ... do=... | 1 | -9/+9 | ||
2025-05-21 | backup-partition: :do ... on-error=... -> :onerror ... do=... | 1 | -7/+9 | ||
2025-05-21 | global-functions: $DownloadPackage: reverse failure logic... | 1 | -14/+11 | ||
... and do not retry. | |||||
2025-05-13 | sms-forward: add error handling on message removal | 1 | -4/+12 | ||
2025-05-13 | sms-forward: delay after removal... | 1 | -0/+2 | ||
... to give the SIM card some time to succeed. Removing several messages one after another fails without this. |