Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
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.9beta4routeros-7.9beta4-1 | Christian Hesse | 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 | Christian Hesse | 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 | 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 | Christian Hesse | 1 | -1/+1 | |
The other values *should* be unchanged... | |||||
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...change-97 | Christian Hesse | 3 | -12/+16 | |
... and an optional CNAME with host name. | |||||
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 | Christian Hesse | 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 | 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 | Christian Hesse | 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 | Christian Hesse | 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 | 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"change-95 | Christian Hesse | 125 | -5175/+5622 | |
No functional change for the user... The migration is done automatically. | |||||
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... | Christian Hesse | 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 | Christian Hesse | 1 | -8/+10 | |
2023-02-26 | global-functions: $MkDir: drop the compatibility workaroundrouteros-7.7 | Christian Hesse | 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 | Christian Hesse | 1 | -2/+2 | |
2023-02-26 | telegram-chat: ignore new messages after reboot | Christian Hesse | 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 | 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 | Christian Hesse | 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 | Christian Hesse | 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 | 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 | Christian Hesse | 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 | 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 | Christian Hesse | 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 | 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 ... | Christian Hesse | 1 | -2/+2 | |
... a simple change to root dir is sufficient. | |||||
2023-02-03 | telegram-chat: log with severity debug only... | Christian Hesse | 1 | -1/+1 | |
... as failed request are quite common. | |||||
2023-02-03 | telegram-chat: delay confirmation of updates | Christian Hesse | 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 | 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 | Christian Hesse | 1 | -1/+3 | |
For now this is a hidden settings... Do we want this to be documented? | |||||
2023-02-02 | global-functions: $WaitForFile: use delay instead of iterations | Christian Hesse | 2 | -6/+7 | |
2023-02-02 | telegram-chat: reply with a hint when untrusted... | Christian Hesse | 1 | -1/+6 | |
... but only when activating via identity. | |||||
2023-02-02 | telegram-chat: always reply to origin chat | Christian Hesse | 2 | -3/+4 | |
2023-02-02 | mod/notification-telegram: support sending to specific chatid | Christian Hesse | 1 | -1/+2 | |
2023-02-01 | doc/telegram-chat: give an example on how to work around command runtime | Christian Hesse | 1 | -0/+7 | |
2023-02-01 | doc/telegram-chat: add hint on output size | Christian Hesse | 1 | -0/+6 | |
2023-02-01 | telegram-chat: modify text if no output available | Christian Hesse | 1 | -1/+2 | |
2023-02-01 | telegram-chat: also give a hint on failed syntax validation | Christian Hesse | 1 | -1/+3 | |
... and drop the warning in log instead. | |||||
2023-02-01 | telegram-chat: ... and give a hint on failure | Christian Hesse | 1 | -1/+4 | |
2023-02-01 | telegram-chat: handle error in command... | Christian Hesse | 1 | -1/+2 | |
2023-02-01 | telegram-chat: give a hint if command is still running | Christian Hesse | 1 | -2/+3 | |
2023-02-01 | doc/telegram-chat: add hint on command runtime | Christian Hesse | 1 | -0/+6 | |
2023-02-01 | doc/telegram-chat: warn about changing group id | Christian Hesse | 1 | -0/+3 | |
2023-01-31 | doc/telegram-chat: allow bots to receive messages in a group | Christian Hesse | 1 | -0/+6 | |
2023-01-31 | daily-psk: make qr-code url configurablechange-92 | Christian Hesse | 6 | -4/+9 | |
2023-01-31 | check-routeros-update: drop check for capchange-91 | Christian Hesse | 5 | -11/+2 | |
This becomes complicated with legacy wireless and wifiwave2 package, old and new CAPsMAN. Let's just drop the check. | |||||
2023-01-31 | introduce telegram-chatchange-90 | Christian Hesse | 9 | -1/+222 | |
Druvis from Mikrotik produced a video "MikroTik Telegram bot - Chat with your Router?". He shows his script to chat with a Router via Telegram bot to send it commands: https://youtu.be/KLX6j3sLRIE This script is kind of limited and has several issues... ๐ฅด Let's make it robust, usable, multi-device capable and just fun! ๐ (Sadly Mikrotik has a policy to not allow links in Youtube comments. Thus my comment with several hints was removed immediately. If anybody is in contact with Druvis... Please tell him about this script!) | |||||
2023-01-31 | global-functions: $WaitForFile: allow to give iterations... | Christian Hesse | 1 | -1/+3 | |
... to increase timeout. Every iteration is about 100ms. | |||||
2023-01-26 | check-certificates: handle decryption failures and warn | Christian Hesse | 1 | -1/+10 | |
If a download succeeds at least one of the given passphrases is expected to decrypt a key in the file. | |||||
2023-01-26 | global-functions: $LogPrintExit2: always print the message... | Christian Hesse | 1 | -5/+5 | |
... even on error. Not sure why and when this broke. | |||||
2023-01-24 | update list of contributors | Christian Hesse | 1 | -0/+1 | |
2023-01-23 | check-certificates: make the warning time configurablechange-89 | Christian Hesse | 5 | -2/+7 | |
2023-01-23 | doc/check-certificates: document the renew time | Christian Hesse | 1 | -0/+1 | |
2023-01-23 | global-functions: $MkDir: catch error on creating tmpfs | Christian Hesse | 1 | -1/+7 | |