Age | Commit message (Expand) | Author | Files | Lines |
2023-04-06 | README: add badge to hint required RouterOS version | Christian Hesse | 1 | -0/+1 |
2023-04-06 | check-certificates: show CommonName only if available | Christian Hesse | 1 | -1/+1 |
2023-04-06 | check-certificates: format information in a local function | Christian Hesse | 1 | -20/+24 |
2023-04-04 | mod/scriptrunonce: link documentation | Christian Hesse | 1 | -0/+3 |
2023-04-04 | mod/notification-telegram: link documentation | Christian Hesse | 1 | -0/+3 |
2023-04-04 | mod/notification-matrix: link documentation | Christian Hesse | 1 | -0/+3 |
2023-04-04 | mod/notification-email: link documentation | Christian Hesse | 1 | -0/+3 |
2023-04-04 | mod/ipcalc: link documentation | Christian Hesse | 1 | -0/+3 |
2023-04-04 | mod/inspectvar: link documentation | Christian Hesse | 1 | -0/+3 |
2023-03-31 | doc/check-health: use an unusual interval | Christian Hesse | 1 | -1/+5 |
2023-03-30 | global-functions: $VersionToNum: support "alpha" in version string | Christian Hesse | 1 | -3/+6 |
2023-03-30 | global-functions: $RequiredRouterOS: accept "alpha" in version string | Christian Hesse | 1 | -1/+1 |
2023-03-29 | dhcp-to-dns: use better condition•••The condition worked, but could match others (AAAA, NXDOMAIN, ...) as
well (though these should not exist).
The problem is that matching with `type=A` does not return any results.
For historical reasons A records have no type, thus can be matched with
`!type`. I opened an issue to fix this... (SUP-111312)
So let's assum `!type` works and `type=A` could become valid...
| Christian Hesse | 1 | -1/+1 |
2023-03-29 | contrib/notification.html: add and load the script | Christian Hesse | 2 | -0/+7 |
2023-03-29 | contrib/notification.html: fix warnings and errors•••Checked with W3C validator: https://validator.w3.org/
| Christian Hesse | 2 | -5/+6 |
2023-03-29 | Merge branch 'mkdir' into next | Christian Hesse | 1 | -34/+64 |
2023-03-28 | global-functions: $MkDir: make directory by adding file•••This is new functionality in RouterOS 7.9beta4, where new file can be
added with `/file/add ...`. This also creates directories for the full
path.
routeros-7.9beta4-2 | Christian Hesse | 1 | -1/+18 |
2023-03-28 | global-functions: $MkDir: add extra block for indention...•••... to make the next commit cleaner. No functional change.
| Christian Hesse | 1 | -30/+32 |
2023-03-28 | dhcp-to-dns: support host name from dhcp lease comment•••The lease comment is supposed to be a human readable string... But we
could allow parsable information.
| Christian Hesse | 2 | -1/+16 |
2023-03-28 | global-functions: $MkDir: create tmpfs in local function | Christian Hesse | 1 | -10/+22 |
2023-03-28 | global-functions: $MkDir: return false on error | Christian Hesse | 1 | -1/+1 |
2023-03-28 | global-functions: $MkDir: drop unused function | Christian Hesse | 1 | -1/+0 |
2023-03-28 | dhcp-to-dns: add cname if host name appears for existing record | Christian Hesse | 1 | -0/+4 |
2023-03-28 | doc/dhcp-to-dns: mention A record and optional CNAME record | Christian Hesse | 1 | -1/+3 |
2023-03-28 | sms-forward: check that the interface is running | Christian Hesse | 1 | -0/+4 |
2023-03-24 | sms-forward: disable workaround for ROS 7.9beta4•••The issue has been acknowledged by Mikrotik, but the cause is still
unknown as the sms code did not change since RouterOS 7.6...
Well, looks like the behavior changes again with RouterOS 7.9beta4, and
everything works as expected again. So disable the workaround there.
routeros-7.9beta4-1 | Christian Hesse | 1 | -1/+2 |
2023-03-23 | sms-forward: add workaround to fix removal of messages•••Removal of messages is broken in RouterOS 7.8:
[admin@MikroTik] > /tool/sms/inbox/remove [ find ]
failure: Interface not running!
Of course the interface is running. Toggling the auto-erase setting
fixes this until next boot. So let's add a workaround...
Reported to support (SUP-110828), but not (yet) acknowledged. ๐คจ
routeros-7.8 | Christian Hesse | 1 | -0/+10 |
2023-03-22 | Merge branch 'dhcp-to-dns' into next | Christian Hesse | 3 | -24/+28 |
2023-03-22 | dhcp-to-dns: update cname record on changed host name | Christian Hesse | 1 | -0/+6 |
2023-03-22 | dhcp-to-dns: just update the address•••The other values *should* be unchanged...
| Christian Hesse | 1 | -1/+1 |
2023-03-22 | dhcp-to-dns: add debug message on duplicate leases | Christian Hesse | 1 | -0/+1 |
2023-03-22 | dhcp-to-dns: do not update records based on host name | Christian Hesse | 1 | -7/+0 |
2023-03-22 | dhcp-to-dns: always create A record with mac address...•••... and an optional CNAME with host name.
change-97 | Christian Hesse | 3 | -12/+16 |
2023-03-22 | dhcp-to-dns: split fqdn to host name and domain | Christian Hesse | 1 | -7/+7 |
2023-03-22 | lease-script: add script name in order•••This makes sure scripts with the same order can not conflict.
| Christian Hesse | 1 | -1/+1 |
2023-03-22 | dhcp-to-dns: match comment on beginning of line | Christian Hesse | 1 | -1/+1 |
2023-03-22 | dhcp-to-dns: allow the matching separator string in name | Christian Hesse | 1 | -4/+4 |
2023-03-22 | ipsec-to-dns: match comment on beginning of line | Christian Hesse | 1 | -1/+1 |
2023-03-22 | ipsec-to-dns: allow the matching separator string in name | Christian Hesse | 1 | -4/+4 |
2023-03-20 | README: badge in style flat and with color | Christian Hesse | 1 | -3/+3 |
2023-03-20 | doc/netwatch-notify: prevent escaping code in hook by creating a script | Christian Hesse | 1 | -0/+3 |
2023-03-20 | doc/netwatch-notify: move hint on notification settings up | Christian Hesse | 1 | -5/+5 |
2023-03-20 | netwatch-notify: support note in notificationchange-96 | Christian Hesse | 4 | -1/+16 |
2023-03-10 | drop dummy scripts used for migration•••This now causes expected warnings on first run of $ScriptInstallUpdate.
The migration still works, as we keep `global-config.changes` and
`global-functions`.
| Christian Hesse | 57 | -169/+1 |
2023-03-10 | global-functions: $ScriptInstallUpdate: add proper version in user agent•••This allows me to identify what RouterOS versions are run on devices
fetching my scripts, which may helps to decide what incompatible changes
to push.
| Christian Hesse | 1 | -2/+5 |
2023-03-07 | lease-script: make sure not to match self | Christian Hesse | 1 | -1/+1 |
2023-03-07 | global-functions: $ScriptInstallUpdate: make sure not to match self | Christian Hesse | 1 | -1/+1 |
2023-03-07 | rename scripts and add file extension ".rsc"•••No functional change for the user... The migration is done
automatically.
change-95 | Christian Hesse | 125 | -5175/+5622 |
2023-03-06 | add the notification generator | Christian Hesse | 2 | -0/+72 |
2023-03-06 | ... and update the logo in notifications | Christian Hesse | 23 | -1/+1 |
2023-03-06 | use a new logo | Christian Hesse | 3 | -20/+26 |
2023-03-06 | check-routeros-update: allow to install all updates automatically...•••... but with extra hurdle for more awareness of danger.
Let's not send a new notification, intentionally. This feature is
dangerous, and we should not advertise it.
| Christian Hesse | 3 | -0/+18 |
2023-03-03 | doc/check-routeros-update: update wording and details | Christian Hesse | 1 | -8/+10 |
2023-02-26 | global-functions: $MkDir: drop the compatibility workaround•••If you are still running RouterOS 7.6 or older add this in your
global-config-overlay:
:global ScriptUpdatesUrlSuffix "\?h=routeros-7.7~1";
... and remeber to revert that change once updated.
routeros-7.7 | Christian Hesse | 1 | -3/+3 |
2023-02-26 | telegram-chat: get the uptime just once | Christian Hesse | 1 | -2/+2 |
2023-02-26 | telegram-chat: ignore new messages after reboot•••This script supports multiple devices, and sending offset to discard
messages is delayed to third fetch to make sure all devices get the
message.
This can cause trouble, though: Sending a device a reboot command can
make that device reboot multiple times ๐ฅด or - even worse - make it
enter an infinite boot loop ๐ณ if it is the only device.
So let's ignore first messages after reboot.
| Christian Hesse | 1 | -1/+2 |
2023-02-26 | telegram-chat: send messages in reply | Christian Hesse | 1 | -3/+4 |
2023-02-24 | mod/notification-telegram: support sending in reply | Christian Hesse | 1 | -1/+4 |
2023-02-24 | netwatch-notify: support sending silent notifications | Christian Hesse | 1 | -2/+2 |
2023-02-17 | INITIAL-COMMANDS: link to new paragraphs | Christian Hesse | 1 | -3/+3 |
2023-02-17 | README: add a paragraph for scheduled automatic updates | Christian Hesse | 1 | -2/+4 |
2023-02-17 | README: move configuration down, make it a separate paragraph | Christian Hesse | 11 | -21/+33 |
2023-02-16 | packages-update: put reboot into a function•••Make the logic even simpler... Let's put the reboot code into a
function. That is volatile, so device does not reboot if it is
rebooted already.
| Christian Hesse | 1 | -2/+6 |
2023-02-16 | packages-update: check version before reboot from scheduler•••Chances are that the device was rebooted manually... Do not reboot then.
| Christian Hesse | 1 | -2/+3 |
2023-02-14 | telegram-chat: log command with failed syntax validation | Christian Hesse | 1 | -0/+1 |
2023-02-14 | telegram-chat: never decrease the local offset | Christian Hesse | 1 | -1/+1 |
2023-02-14 | telegram-chat: add debug message for handled updates | Christian Hesse | 1 | -0/+2 |
2023-02-14 | telegram-chat: add updateid in log messages | Christian Hesse | 1 | -3/+4 |
2023-02-14 | check-health: wording: load -> utilization•••The load is defined as something different...
https://en.wikipedia.org/wiki/Load_(computing)
So let's update the wording and use 'utilization' instead.
---- โ๏ธ ----
๐งฎ๏ธ๐๏ธ Health warning: CPU utilization
The average CPU utilization on MikroTik is at 76%!
---- โ๏ธ ----
๐งฎ๏ธ๐๏ธ Health recovery: CPU utilization
The average CPU utilization on MikroTik decreased to 64%.
---- โ๏ธ ----
| Christian Hesse | 7 | -19/+19 |
2023-02-13 | doc/check-health: make the voltage limit a separate point | Christian Hesse | 1 | -1/+2 |
2023-02-13 | doc/check-health: add line break between screenshots | Christian Hesse | 1 | -2/+2 |
2023-02-13 | README: give hint about converting line endings | Christian Hesse | 1 | -0/+5 |
2023-02-13 | global-functions: $PrettyPrint: use $Unix2Dos | Christian Hesse | 1 | -2/+2 |
2023-02-13 | global-functions: introduce $Dos2Unix | Christian Hesse | 1 | -0/+10 |
2023-02-13 | global-functions: introduce $Unix2Dos | Christian Hesse | 1 | -0/+11 |
2023-02-10 | ipv6-update: support host addresses in address-listchange-94 | Christian Hesse | 4 | -5/+22 |
2023-02-09 | ipv6-update: accept a single prefix only | Christian Hesse | 1 | -6/+9 |
2023-02-09 | ipv6-update: rename variable | Christian Hesse | 1 | -5/+5 |
2023-02-09 | ipv6-update: use identical parameters to find address | Christian Hesse | 1 | -2/+2 |
2023-02-08 | doc/backup-upload: new option $BackupSendGlobalConfig | Christian Hesse | 1 | -0/+1 |
2023-02-08 | doc/backup-email: new option $BackupSendGlobalConfig | Christian Hesse | 1 | -0/+1 |
2023-02-08 | backup-upload: use :use inside :execute for global-config-overlay | Christian Hesse | 1 | -2/+2 |
2023-02-08 | backup-email: use :use inside :execute for global-config-overlay•••This will add carriage return and line feed, but works around the
limitation of reading just four kilobytes from file.
| Christian Hesse | 1 | -2/+2 |
2023-02-07 | global-functions: $ScriptInstallUpdate: use complete property name | Christian Hesse | 1 | -1/+1 |
2023-02-07 | telegram-chat: use complete property name | Christian Hesse | 1 | -1/+1 |
2023-02-07 | Merge branch 'backup-g-c-o' into next | Christian Hesse | 5 | -4/+40 |
2023-02-07 | notify about backup for global-config-overlaychange-93 | Christian Hesse | 2 | -1/+2 |
2023-02-07 | backup-upload: support uploading global-config-overlay | Christian Hesse | 1 | -2/+24 |
2023-02-07 | backup-email: support sending global-config-overlay | Christian Hesse | 1 | -1/+13 |
2023-02-07 | global-config: new option to backup global-config-overlay | Christian Hesse | 1 | -0/+1 |
2023-02-04 | telegram-chat: handle exceeded file read size | Christian Hesse | 1 | -1/+2 |
2023-02-03 | telegram-chat: no need to :put ...•••... a simple change to root dir is sufficient.
| Christian Hesse | 1 | -2/+2 |
2023-02-03 | telegram-chat: log with severity debug only...•••... as failed request are quite common.
| Christian Hesse | 1 | -1/+1 |
2023-02-03 | telegram-chat: delay confirmation of updates•••Several devices can communicate with the same bot, and we want all of
them to receive their updates. However this can be tricky, as...
* ... sometimes internet connection can be unreliable or saturated.
* ... device can be busy with long running command.
* ... the Telegram bot api servers seem to implement what ever kind of
rate limiting. Anybody can give details?
So let's confirm the update id after third request only. ๐ This gives
delayed devices some extra chances to catch up.
| Christian Hesse | 1 | -6/+8 |
2023-02-03 | telegram-chat: log warning only when trying to activate | Christian Hesse | 1 | -2/+5 |
2023-02-03 | telegram-chat: handle missing username | Christian Hesse | 1 | -1/+3 |
2023-02-02 | backup-email: wait for the mail to be sent | Christian Hesse | 1 | -0/+10 |
2023-02-02 | telegram-chat: discard messages without text | Christian Hesse | 1 | -1/+1 |
2023-02-02 | telegram-chat: allow to modify the time to wait for command•••For now this is a hidden settings... Do we want this to be documented?
| Christian Hesse | 1 | -1/+3 |
2023-02-02 | global-functions: $WaitForFile: use delay instead of iterations | Christian Hesse | 2 | -6/+7 |