Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2023-04-07 | check-certificates: download and import in a local function | 1 | -31/+41 | ||
2023-04-07 | check-certificates: include SANs in information | 2 | -0/+11 | ||
2023-04-06 | check-certificates: show CommonName only if available | 1 | -1/+1 | ||
2023-04-06 | check-certificates: format information in a local function | 1 | -20/+24 | ||
2023-04-06 | README: add badge to hint required RouterOS version | 1 | -0/+1 | ||
2023-04-04 | mod/scriptrunonce: link documentation | 1 | -0/+3 | ||
2023-04-04 | mod/notification-telegram: link documentation | 1 | -0/+3 | ||
2023-04-04 | mod/notification-matrix: link documentation | 1 | -0/+3 | ||
2023-04-04 | mod/notification-email: link documentation | 1 | -0/+3 | ||
2023-04-04 | mod/ipcalc: link documentation | 1 | -0/+3 | ||
2023-04-04 | mod/inspectvar: link documentation | 1 | -0/+3 | ||
2023-03-31 | doc/check-health: use an unusual interval | 1 | -1/+5 | ||
2023-03-30 | global-functions: $VersionToNum: support "alpha" in version string | 1 | -3/+6 | ||
2023-03-30 | global-functions: $RequiredRouterOS: accept "alpha" in version string | 1 | -1/+1 | ||
2023-03-29 | dhcp-to-dns: use better condition | 1 | -1/+1 | ||
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... | |||||
2023-03-29 | contrib/notification.html: add and load the script | 2 | -0/+7 | ||
2023-03-29 | contrib/notification.html: fix warnings and errors | 2 | -5/+6 | ||
Checked with W3C validator: https://validator.w3.org/ | |||||
2023-03-29 | Merge branch 'mkdir' into next | 1 | -34/+64 | ||
2023-03-28 | global-functions: $MkDir: make directory by adding filerouteros-7.9beta4-2 | 1 | -1/+18 | ||
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. | |||||
2023-03-28 | global-functions: $MkDir: add extra block for indention... | 1 | -30/+32 | ||
... to make the next commit cleaner. No functional change. | |||||
2023-03-28 | dhcp-to-dns: support host name from dhcp lease comment | 2 | -1/+16 | ||
The lease comment is supposed to be a human readable string... But we could allow parsable information. | |||||
2023-03-28 | global-functions: $MkDir: create tmpfs in local function | 1 | -10/+22 | ||
2023-03-28 | global-functions: $MkDir: return false on error | 1 | -1/+1 | ||
2023-03-28 | global-functions: $MkDir: drop unused function | 1 | -1/+0 | ||
2023-03-28 | dhcp-to-dns: add cname if host name appears for existing record | 1 | -0/+4 | ||
2023-03-28 | doc/dhcp-to-dns: mention A record and optional CNAME record | 1 | -1/+3 | ||
2023-03-28 | sms-forward: check that the interface is running | 1 | -0/+4 | ||
2023-03-24 | sms-forward: disable workaround for ROS 7.9beta4routeros-7.9beta4-1 | 1 | -1/+2 | ||
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. | |||||
2023-03-23 | sms-forward: add workaround to fix removal of messagesrouteros-7.8 | 1 | -0/+10 | ||
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. ๐คจ | |||||
2023-03-22 | Merge branch 'dhcp-to-dns' into next | 3 | -24/+28 | ||
2023-03-22 | dhcp-to-dns: update cname record on changed host name | 1 | -0/+6 | ||
2023-03-22 | dhcp-to-dns: just update the address | 1 | -1/+1 | ||
The other values *should* be unchanged... | |||||
2023-03-22 | dhcp-to-dns: add debug message on duplicate leases | 1 | -0/+1 | ||
2023-03-22 | dhcp-to-dns: do not update records based on host name | 1 | -7/+0 | ||
2023-03-22 | dhcp-to-dns: always create A record with mac address...change-97 | 3 | -12/+16 | ||
... and an optional CNAME with host name. | |||||
2023-03-22 | dhcp-to-dns: split fqdn to host name and domain | 1 | -7/+7 | ||
2023-03-22 | lease-script: add script name in order | 1 | -1/+1 | ||
This makes sure scripts with the same order can not conflict. | |||||
2023-03-22 | dhcp-to-dns: match comment on beginning of line | 1 | -1/+1 | ||
2023-03-22 | dhcp-to-dns: allow the matching separator string in name | 1 | -4/+4 | ||
2023-03-22 | ipsec-to-dns: match comment on beginning of line | 1 | -1/+1 | ||
2023-03-22 | ipsec-to-dns: allow the matching separator string in name | 1 | -4/+4 | ||
2023-03-20 | README: badge in style flat and with color | 1 | -3/+3 | ||
2023-03-20 | doc/netwatch-notify: prevent escaping code in hook by creating a script | 1 | -0/+3 | ||
2023-03-20 | doc/netwatch-notify: move hint on notification settings up | 1 | -5/+5 | ||
2023-03-20 | netwatch-notify: support note in notificationchange-96 | 4 | -1/+16 | ||
2023-03-10 | drop dummy scripts used for migration | 57 | -169/+1 | ||
This now causes expected warnings on first run of $ScriptInstallUpdate. The migration still works, as we keep `global-config.changes` and `global-functions`. | |||||
2023-03-10 | global-functions: $ScriptInstallUpdate: add proper version in user agent | 1 | -2/+5 | ||
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. | |||||
2023-03-07 | lease-script: make sure not to match self | 1 | -1/+1 | ||
2023-03-07 | global-functions: $ScriptInstallUpdate: make sure not to match self | 1 | -1/+1 | ||
2023-03-07 | rename scripts and add file extension ".rsc"change-95 | 125 | -5175/+5622 | ||
No functional change for the user... The migration is done automatically. | |||||
2023-03-06 | add the notification generator | 2 | -0/+72 | ||
2023-03-06 | ... and update the logo in notifications | 23 | -1/+1 | ||
2023-03-06 | use a new logo | 3 | -20/+26 | ||
2023-03-06 | check-routeros-update: allow to install all updates automatically... | 3 | -0/+18 | ||
... 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. | |||||
2023-03-03 | doc/check-routeros-update: update wording and details | 1 | -8/+10 | ||
2023-02-26 | global-functions: $MkDir: drop the compatibility workaroundrouteros-7.7 | 1 | -3/+3 | ||
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. | |||||
2023-02-26 | telegram-chat: get the uptime just once | 1 | -2/+2 | ||
2023-02-26 | telegram-chat: ignore new messages after reboot | 1 | -1/+2 | ||
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. | |||||
2023-02-26 | telegram-chat: send messages in reply | 1 | -3/+4 | ||
2023-02-24 | mod/notification-telegram: support sending in reply | 1 | -1/+4 | ||
2023-02-24 | netwatch-notify: support sending silent notifications | 1 | -2/+2 | ||
2023-02-17 | INITIAL-COMMANDS: link to new paragraphs | 1 | -3/+3 | ||
2023-02-17 | README: add a paragraph for scheduled automatic updates | 1 | -2/+4 | ||
2023-02-17 | README: move configuration down, make it a separate paragraph | 11 | -21/+33 | ||
2023-02-16 | packages-update: put reboot into a function | 1 | -2/+6 | ||
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. | |||||
2023-02-16 | packages-update: check version before reboot from scheduler | 1 | -2/+3 | ||
Chances are that the device was rebooted manually... Do not reboot then. | |||||
2023-02-14 | telegram-chat: log command with failed syntax validation | 1 | -0/+1 | ||
2023-02-14 | telegram-chat: never decrease the local offset | 1 | -1/+1 | ||
2023-02-14 | telegram-chat: add debug message for handled updates | 1 | -0/+2 | ||
2023-02-14 | telegram-chat: add updateid in log messages | 1 | -3/+4 | ||
2023-02-14 | check-health: wording: load -> utilization | 7 | -19/+19 | ||
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%. ---- โ๏ธ ---- | |||||
2023-02-13 | doc/check-health: make the voltage limit a separate point | 1 | -1/+2 | ||
2023-02-13 | doc/check-health: add line break between screenshots | 1 | -2/+2 | ||
2023-02-13 | README: give hint about converting line endings | 1 | -0/+5 | ||
2023-02-13 | global-functions: $PrettyPrint: use $Unix2Dos | 1 | -2/+2 | ||
2023-02-13 | global-functions: introduce $Dos2Unix | 1 | -0/+10 | ||
2023-02-13 | global-functions: introduce $Unix2Dos | 1 | -0/+11 | ||
2023-02-10 | ipv6-update: support host addresses in address-listchange-94 | 4 | -5/+22 | ||
2023-02-09 | ipv6-update: accept a single prefix only | 1 | -6/+9 | ||
2023-02-09 | ipv6-update: rename variable | 1 | -5/+5 | ||
2023-02-09 | ipv6-update: use identical parameters to find address | 1 | -2/+2 | ||
2023-02-08 | doc/backup-upload: new option $BackupSendGlobalConfig | 1 | -0/+1 | ||
2023-02-08 | doc/backup-email: new option $BackupSendGlobalConfig | 1 | -0/+1 | ||
2023-02-08 | backup-upload: use :use inside :execute for global-config-overlay | 1 | -2/+2 | ||
2023-02-08 | backup-email: use :use inside :execute for global-config-overlay | 1 | -2/+2 | ||
This will add carriage return and line feed, but works around the limitation of reading just four kilobytes from file. | |||||
2023-02-07 | global-functions: $ScriptInstallUpdate: use complete property name | 1 | -1/+1 | ||
2023-02-07 | telegram-chat: use complete property name | 1 | -1/+1 | ||
2023-02-07 | Merge branch 'backup-g-c-o' into next | 5 | -4/+40 | ||
2023-02-07 | notify about backup for global-config-overlaychange-93 | 2 | -1/+2 | ||
2023-02-07 | backup-upload: support uploading global-config-overlay | 1 | -2/+24 | ||
2023-02-07 | backup-email: support sending global-config-overlay | 1 | -1/+13 | ||
2023-02-07 | global-config: new option to backup global-config-overlay | 1 | -0/+1 | ||
2023-02-04 | telegram-chat: handle exceeded file read size | 1 | -1/+2 | ||
2023-02-03 | telegram-chat: no need to :put ... | 1 | -2/+2 | ||
... a simple change to root dir is sufficient. | |||||
2023-02-03 | telegram-chat: log with severity debug only... | 1 | -1/+1 | ||
... as failed request are quite common. | |||||
2023-02-03 | telegram-chat: delay confirmation of updates | 1 | -6/+8 | ||
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. | |||||
2023-02-03 | telegram-chat: log warning only when trying to activate | 1 | -2/+5 | ||
2023-02-03 | telegram-chat: handle missing username | 1 | -1/+3 | ||
2023-02-02 | backup-email: wait for the mail to be sent | 1 | -0/+10 | ||
2023-02-02 | telegram-chat: discard messages without text | 1 | -1/+1 | ||