Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2023-10-16 | update list of contributors | 1 | -0/+1 | ||
2023-10-06 | mod/notification-email: handle new property name...routeros-7.12rc1-1 | 1 | -2/+3 | ||
... which changed in RouterOS 7.12rc1. | |||||
2023-10-05 | log-forward: add 'raw' in default filter... | 1 | -1/+1 | ||
... which is used when logging raw packets or commands. | |||||
2023-10-05 | collect-wireless-mac: ignore remote aps... | 2 | -2/+2 | ||
... which are listed here in station mode. | |||||
2023-09-29 | netwatch-notify: allow to give different origin for hosts... | 1 | -6/+4 | ||
... to use differing notification settings. Add an origin name in netwatch configuration: /tool/netwatch/add comment="notify, name=dns-google, origin=netwatch-notify-google" address=8.8.8.8; /tool/netwatch/add comment="notify, name=dns-cloudflare, origin=netwatch-notify-cloudflare" address=1.1.1.1; Then configure the notification settings in `global-config-overlay`: :global EmailGeneralToOverride { "netwatch-notify-google"="google@example.com"; "netwatch-notify-cloudflare"="cloudflare@example.com"; } I think it is best to handle this as a hidden setting... Handle with care! | |||||
2023-09-22 | collect-wireless-mac: filter on dns type | 4 | -4/+4 | ||
2023-09-20 | collect-wireless-mac: add CNAME(s) in notification | 4 | -8/+24 | ||
2023-09-18 | global-functions: split off $FormatMultiLines ... | 2 | -8/+23 | ||
... to format multiple lines from an array. | |||||
2023-09-15 | telegram-chat: create status files with /file/addrouteros-7.9beta4-9 | 1 | -4/+4 | ||
We have no content, thus no issues with file size. | |||||
2023-09-15 | telegram-chat: use the full command name :execute | 1 | -1/+1 | ||
2023-09-15 | global-functions: $EitherOr: properly handle time values | 1 | -0/+3 | ||
2023-09-13 | drop dummy scripts used for wifiwave2 migration | 4 | -12/+0 | ||
This now causes expected warnings on first run of $ScriptInstallUpdate. | |||||
2023-09-13 | check-routeros-update: do not match the channel on neighbor update | 1 | -1/+1 | ||
While this works for stable, it does not for testing: The testing channel can have "testing" in the string for rc releases, but also "development" for beta releases... and possibly more. Instead match on version string only, with word boundary. | |||||
2023-09-13 | lease-script: match on word boundary | 1 | -2/+1 | ||
2023-09-13 | packages-update: match on word boundary | 1 | -2/+1 | ||
2023-09-13 | doc/packages-update: mention and link all backup scripts | 1 | -3/+7 | ||
2023-09-13 | packages-update: drop order from message | 1 | -1/+1 | ||
2023-09-13 | packages-update: implement backup script order | 5 | -8/+18 | ||
2023-09-06 | fw-addr-lists: no (mixed) capitalization in message | 1 | -1/+1 | ||
2023-08-31 | check-routeros-update: show neighbor's identity in message and notification | 1 | -9/+13 | ||
2023-08-31 | check-routeros-update: support update from specific neighbor(s)change-105 | 5 | -2/+8 | ||
... by matching the identity property. | |||||
2023-08-30 | backup-upload: revert changes, add comment with warning | 1 | -21/+13 | ||
Turned out that using `/file/add ...` introduced a regression. Accessing (reading and writing) file contents is limited to 4095 bytes. This limitation does not exist for `:execute script=... file=...`, so keep the old code. Also add a comment with warning. | |||||
2023-08-30 | backup-email: revert changes, add comment with warning | 1 | -23/+8 | ||
Turned out that using `/file/add ...` introduced a regression. Accessing (reading and writing) file contents is limited to 4095 bytes. This limitation does not exist for `:execute script=... file=...`, so keep the old code. Also add a comment with warning. | |||||
2023-08-30 | backup-upload: check configuration size before writing file | 1 | -7/+9 | ||
2023-08-30 | backup-email: check configuration size before writing file | 1 | -5/+6 | ||
2023-08-29 | backup-upload: detect failure creating config file | 1 | -6/+13 | ||
2023-08-29 | backup-email: detect failure creating config file | 1 | -2/+10 | ||
2023-08-29 | backup-email: support indication of failure | 1 | -2/+9 | ||
2023-08-29 | backup-email: write config file directlyrouteros-7.9beta4-8 | 1 | -5/+5 | ||
This functionality was added in RouterOS 7.9beta4... | |||||
2023-08-29 | backup-upload: write config file directlyrouteros-7.9beta4-7 | 1 | -5/+5 | ||
This functionality was added in RouterOS 7.9beta4... | |||||
2023-08-29 | hotspot-to-wpa-cleanup: show last-seen, not timeout | 3 | -3/+3 | ||
2023-08-24 | hotspot-to-wpa-cleanup: require RouterOS for wifiwave2routeros-7.12beta3-1 | 2 | -0/+4 | ||
RouterOS before version 7.12beta3 had a bug where getting comment from registration-table is not possible. Require that version at least. This was fixed in SUP-124500. | |||||
2023-08-18 | global-functions: prepare user-agent for fetch in global variable | 1 | -6/+6 | ||
2023-08-18 | mod/ssh-keys-import: $SSHKeysImport: add check for key type | 1 | -0/+6 | ||
2023-08-18 | mod/ssh-keys-import: support ed25519 keys...routeros-7.12beta1-1 | 2 | -2/+8 | ||
... with RouterOS 7.12beta1 | |||||
2023-08-18 | doc/mod/ssh-keys-import: drop duplicate key type | 1 | -1/+1 | ||
Stupid copy'n'paste error... 🫣 | |||||
2023-08-18 | sms-forward: drop RouterOS version dependency | 2 | -4/+0 | ||
... as global-functions depend on RouterOS 7.9beta already. | |||||
2023-08-18 | netwatch-notify: drop RouterOS version dependency | 2 | -4/+0 | ||
... as global-functions depend on RouterOS 7.9beta already. | |||||
2023-08-18 | mod/ssh-keys-import: drop RouterOS version dependency | 2 | -4/+0 | ||
... as global-functions depend on RouterOS 7.9beta already. | |||||
2023-08-15 | Merge branch 'wifiwave2' into next | 36 | -347/+1340 | ||
2023-08-15 | news and migration for wifiwave2change-104 | 2 | -1/+3 | ||
2023-08-09 | hotspot-to-wpa: convert to template, split capsman & wifiwave2 | 9 | -158/+523 | ||
2023-08-09 | daily-psk: add support for wifiwave2 | 3 | -8/+116 | ||
2023-08-09 | dhcp-lease-comment: add support for wifiwave2 | 3 | -4/+44 | ||
2023-08-09 | collect-wireless-mac: add support for wifiwave2 | 3 | -4/+103 | ||
2023-08-09 | accesslist-duplicates: add support for wifiwave2 | 3 | -4/+55 | ||
2023-08-09 | capsman-download-packages: download a default set for wifiwave2 | 3 | -2/+26 | ||
Well, AX devices can be arm or arm64... So let's just download packages 'routeros' and 'wifiwave2' - crossing fingers... 🤞 | |||||
2023-08-09 | capsman-download-packages: no download of missing package for wifiwave2 | 3 | -28/+6 | ||
Sadly the log messages from wifiwave2 do not contain any hint what is missing... So it's not possible to download missing files. | |||||
2023-08-09 | Makefile: support excluding blocks from templates | 1 | -0/+3 | ||
2023-08-09 | capsman-rolling-upgrade: convert to template, split capsman & wifiwave2 | 5 | -39/+141 | ||
2023-08-09 | capsman-download-packages: convert to template, split capsman & wifiwave2 | 5 | -90/+288 | ||
2023-08-07 | capsman-download-packages: find script by code comment | 2 | -2/+5 | ||
2023-08-07 | Makefile: only regenerate existing scripts from templates | 1 | -4/+3 | ||
2023-08-07 | Makefile: support wifiwave2 in templates | 1 | -3/+9 | ||
2023-08-07 | collect-wireless-mac: move comment up | 3 | -6/+6 | ||
2023-08-07 | Makefile: drop path rewriting, use pattern to filter | 5 | -31/+46 | ||
2023-08-06 | mod/notification-telegram: introduce $PurgeTelegramQueue | 2 | -0/+14 | ||
... to purge the queue and remove the scheduler. | |||||
2023-08-06 | mod/notification-matrix: introduce $PurgeMatrixQueue | 2 | -0/+14 | ||
... to purge the queue and remove the scheduler. | |||||
2023-08-06 | mod/notification-email: introduce $PurgeEmailQueue | 2 | -0/+14 | ||
... to purge the queue and remove the scheduler. | |||||
2023-07-23 | check-certificates: properly handle in place updates | 1 | -9/+12 | ||
This worked just kind of... The certification was updated, but script aborted before the notification was sent. | |||||
2023-07-15 | check-routeros-update: also match platform for neighbors | 1 | -1/+1 | ||
2023-07-13 | check-routeros-update: match version with date suffix | 1 | -1/+2 | ||
Neighbor version can have a date suffix. This changes to match only on the beginning. Closes: GH-45 Co-authored-by: Christian Hesse <mail@eworm.de> | |||||
2023-06-28 | netwatch-dns: increase startup delay | 1 | -1/+1 | ||
In RouterOS 7.9 netwatch itself comes with a (default) startup-delay of five minutes. Increase our delay to make sure netwatch is active. | |||||
2023-06-28 | netwatch-notify: drop the delay on startup...routeros-7.9beta4-6 | 2 | -4/+4 | ||
... now that in RouterOS 7.9 netwatch itself comes with a startup-delay. Hosts in state 'unknown' are just ignored. | |||||
2023-06-28 | README: reference stable version | 1 | -1/+1 | ||
2023-06-28 | global-functions: $MkDir: drop extra block, restore indention | 1 | -14/+13 | ||
We had this to make the previous commit cleaner. No functional change. | |||||
2023-06-28 | global-functions: $MkDir: drop old code with smb workaround...routeros-7.9beta4-5 | 2 | -42/+3 | ||
... and increase required RouterOS. | |||||
2023-06-28 | Merge branch 'hotspot-to-wpa' into next | 5 | -22/+56 | ||
2023-06-28 | hotspot-to-wpa-cleanup: drop hard-coded timeout, get from comment | 3 | -12/+22 | ||
This keeps the default of four weeks, though. | |||||
2023-06-28 | hotspot-to-wpa-cleanup: drop hard-coded server name, find by commentchange-103 | 4 | -12/+25 | ||
2023-06-28 | hotspot-to-wpa: reject for two seconds... | 1 | -1/+5 | ||
... to make the device send a new DHCP request after. | |||||
2023-06-28 | hotspot-to-wpa: support non-local userschange-102 | 4 | -2/+9 | ||
This has some limitations, though: The password is not known and additional configuration can not be given in user's comment. | |||||
2023-06-27 | doc/sms-forward: link the RouterOS button to changelog | 1 | -1/+1 | ||
2023-06-27 | doc/mod/ssh-keys-import: link the RouterOS button to changelog | 1 | -1/+1 | ||
2023-06-27 | README: link the RouterOS button to changelog | 1 | -1/+1 | ||
2023-06-27 | Merge branch 'no-escape-question-mark' into next | 6 | -8/+8 | ||
2023-06-27 | global-functions: $IsTimeSync: calculate with uptime, drop scheduler | 1 | -5/+6 | ||
2023-06-27 | update-tunnelbroker: escaping question mark is no longer required | 1 | -1/+1 | ||
2023-06-27 | mod/scriptrunonce: escaping question mark is no longer required | 1 | -1/+1 | ||
2023-06-27 | mod/notification-email: escaping question mark is no longer required | 1 | -1/+1 | ||
2023-06-27 | global-functions: escaping question mark is no longer required | 2 | -4/+4 | ||
2023-06-27 | global-config: escaping question mark is no longer required | 1 | -1/+1 | ||
2023-06-23 | update-tunnelbroker: rework the retry-loop | 1 | -10/+11 | ||
2023-06-23 | fw-addr-lists: retry to download on failure | 1 | -4/+14 | ||
2023-06-22 | mode-button: add dollar sign in scheduler name | 1 | -5/+5 | ||
2023-06-22 | packages-update: rename scheduler to match function name | 2 | -3/+3 | ||
2023-06-22 | global-functions: $IsTimeSync: reset ntp client when "waiting" | 1 | -0/+13 | ||
Every now and then the ntp client stays in status "waiting" forever... This happens if the server answers, but is not accurate enough. Unlike with connection failure the address is not rotated. (SUP-120012) Let's reset it... Should help with a pool address (like pool.ntp.org) at least. | |||||
2023-06-14 | update list of contributors | 1 | -0/+1 | ||
2023-06-13 | Merge branch 'fw-addr-lists' into next | 8 | -1/+555 | ||
2023-06-13 | fw-addr-lists: support domain names in lists | 1 | -3/+3 | ||
2023-06-13 | fw-addr-lists: prepare lists from spamhaus.org in config | 2 | -1/+6 | ||
2023-06-13 | certs: add Cloudflare certificates... | 1 | -0/+163 | ||
... for later use. | |||||
2023-06-13 | fw-addr-lists: add lists from abuse.ch in config | 2 | -1/+6 | ||
2023-06-13 | certs: add GlobalSign certificates... | 1 | -0/+177 | ||
... for later use. | |||||
2023-06-13 | introduce fw-addr-listschange-101 | 6 | -1/+205 | ||
2023-06-13 | global-functions: $CertificateDownload: add proper version in user agent | 1 | -3/+4 | ||
2023-06-13 | gps-track: add error handling | 1 | -10/+14 | ||
2023-06-13 | gps-track: wait to be fully connected | 1 | -0/+2 | ||
2023-06-13 | Merge branch 'script-lock' into next | 21 | -0/+57 | ||
2023-06-13 | update-tunnelbroker: lock the script | 1 | -0/+3 | ||