Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2025-01-29 | mod/ipcalc: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | mod/inspectvar: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | mode-button: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | mod/bridge-port-vlan: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | mod/bridge-port-to: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | log-forward: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | leds-toggle-mode: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | leds-night-mode: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | leds-day-mode: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | lease-script: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | ipv6-update: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | ipsec-to-dns: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | ip-addr-bridge: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | hotspot-to-wpa: use short url rsc.eworm.de | 3 | -6/+6 | ||
2025-01-29 | hotspot-to-wpa-cleanup: use short url rsc.eworm.de | 3 | -6/+6 | ||
2025-01-29 | gps-track: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | global-wait: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | global-functions: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | global-config: use short url rsc.eworm.de | 1 | -3/+3 | ||
2025-01-29 | global-config-overlay: use short url rsc.eworm.de | 1 | -3/+3 | ||
2025-01-29 | fw-addr-lists: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | firmware-upgrade-reboot: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | dhcp-to-dns: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | dhcp-lease-comment: use short url rsc.eworm.de | 4 | -8/+8 | ||
2025-01-29 | daily-psk.template: use short url rsc.eworm.de | 4 | -8/+8 | ||
2025-01-29 | collect-wireless-mac: use short url rsc.eworm.de | 4 | -8/+8 | ||
2025-01-29 | check-routeros-update: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | check-lte-firmware-upgrade: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | check-health: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | check-certificates: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | certificate-renew-issued: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | capsman-rolling-upgrade: use short url rsc.eworm.de | 3 | -6/+6 | ||
2025-01-29 | capsman-download-packages: use short url rsc.eworm.de | 3 | -6/+6 | ||
2025-01-29 | backup-upload: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | backup-partition: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | backup-email: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | backup-cloud: use short url rsc.eworm.de | 1 | -2/+2 | ||
2025-01-29 | accesslist-duplicates: use short url rsc.eworm.de | 4 | -8/+8 | ||
2025-01-29 | unattended-lte-firmware-upgrade: require RouterOS | 1 | -0/+2 | ||
2025-01-24 | fw-addr-lists: use my static mirror | 1 | -3/+3 | ||
2025-01-24 | BRANCHES: adopt new default url | 1 | -3/+3 | ||
2025-01-24 | global-config: download scripts from rsc.eworm.de | 1 | -2/+4 | ||
Currently AI bots are crawling website all around the world. For a website hosting git content this adds a lot of extra load and traffic: The site has lots of sections, repositories have a lot of files, branches, tags, commit ids, etc... Multiply that and you have a nearly unlimited number of unique urls. The bots try to get each and every of these. To speed up the learing process on their side a swarm of hundreds, thousands or more ip addresses is active at the same time, ultimately DDOS'ing the websites, making it inaccessible. 😳🤬 Well, there is one single file all of these AI bots are not interested in: robots.txt 🤬🤬 On top some use random user agent strings, making filtering impossible. 🤬🤬🤬 For a short term sulution I deploy the repository content as static files, hopefully making these accessible at least. We will see. | |||||
2025-01-22 | fw-addr-lists: spamhaus.org returned to 'GTS Root R4' | 2 | -3/+3 | ||
2025-01-09 | ppp-on-up: release only bound ipv6 dhcp clients | 1 | -1/+1 | ||
2025-01-06 | packages-update: refuse when running from backup partition | 1 | -0/+6 | ||
2025-01-06 | check-routeros-update: refuse when running from backup partition | 1 | -0/+7 | ||
2025-01-06 | backup-upload: refuse when running from backup partition | 1 | -0/+8 | ||
2025-01-06 | backup-partition: refuse when running from backup partition | 1 | -0/+7 | ||
2025-01-06 | backup-email: refuse when running from backup partition | 1 | -0/+8 | ||
2025-01-06 | backup-cloud: refuse when running from backup partition | 1 | -0/+8 | ||
2025-01-02 | update copyright for 2025 | 77 | -77/+77 | ||
2024-12-30 | global-functions: $WaitForFile: drop the first workaround | 1 | -10/+0 | ||
This reverts commit 8231c3e833ee83a118f4d8395c097e6a9f312c2f. Truned out this workaround was not sufficient, see the follow-up in commit 191cc1b952b469c474b0181ebdee0ccfd47ae75b for details. But possibly the second one does it on its own? Reverting this for a test run. | |||||
2024-12-30 | global-functions: $FetchHuge: another workaround for complete file | 1 | -1/+5 | ||
Turns out the workaround in $WaitForFile (commit 8231c3e833ee83a118f4d8395c097e6a9f312c2f) is not sufficient. It helps sometimes, but not always. Possibly depends on CPU speed and bandwidth of internet connection... Who knows!? 🤪 But! Reading the file goes beyond the known file size. That's suspicious and indicates this exact issue. So add a delay, and keep reading until sizes are equal. | |||||
2024-12-30 | fw-addr-lists: spamhaus.org returned to 'ISRG Root X1' | 2 | -3/+3 | ||
This reverts commit 4d8dce97691ad090091574a790449a7bd564023c. | |||||
2024-12-25 | global-functions: $ParseKeyValueStore: support JSON as input | 1 | -0/+7 | ||
This used to require a key=value store, separated with commas. An example for `netwatch-notify` is: /tool/netwatch/add comment="notify, name=example.com" host=93.184.215.14; Now JSON is supported as well, so you could use: /tool/netwatch/add comment="{\"notify\":true,\"name\":\"example.com\"}" host=93.184.215.14; Looks more clumsy here, but may be of help in more complex setups... | |||||
2024-12-25 | global-functions: $ParseKeyValueStore: properly return boolean values | 1 | -0/+2 | ||
2024-12-25 | global-functions: $ParseKeyValueStore: split key and value... | 1 | -2/+3 | ||
... into separate variables. | |||||
2024-12-17 | mod/notification-ntfy: add basic authentication in headers | 1 | -3/+6 | ||
This makes it a bit easier and straight forward as we pass the headers anyway. | |||||
2024-12-17 | mod/notification-ntfy: support authentication with bearer token | 3 | -0/+9 | ||
Closes: https://github.com/eworm-de/routeros-scripts/issues/86 | |||||
2024-12-17 | fw-addr-lists: do not fail on invalid json data | 1 | -1/+3 | ||
2024-12-17 | mod/notification-email: $FlushEmailQueue: just return on empty queue | 1 | -0/+4 | ||
2024-12-17 | mod/notification-email: $FlushEmailQueue: move the check up... | 1 | -4/+6 | ||
... as this needs to be done before creating a scheduler. 😜 Also remove the scheduler and return. | |||||
2024-12-17 | mod/notification-email: $FlushEmailQueue: create scheduler if missing... | 1 | -2/+8 | ||
... as it is required to be modified several times below. | |||||
2024-12-17 | mod/notification-email: $FlushEmailQueue: return on purge | 1 | -0/+6 | ||
2024-12-17 | mod/notification-email: $FlushEmailQueue: return on success | 1 | -3/+4 | ||
2024-12-17 | global-functions: $WaitForFile: delay until "complete"... | 1 | -0/+10 | ||
Well, turns out that waiting for existence of a file is not sufficient. Chances are that a file is available just partly, so wait until the size no longer changes... Let's hope that works as expected. 🤞 | |||||
2024-12-17 | mode-button: support led toggle without extra script | 1 | -1/+1 | ||
2024-12-17 | leds-toggle-mode: toggle in one call... | 1 | -5/+1 | ||
... and drop the condition. | |||||
2024-12-17 | mod/notification-email: increase retry interval on failure | 1 | -2/+4 | ||
2024-12-17 | mod/notification-email: drop useless safeguard | 1 | -1/+1 | ||
Guess it was useful back in the day. Now the function exits early if the queue is empty... So this can never be zero. | |||||
2024-12-09 | Merge branch 'func-exit-error' into next | 12 | -39/+77 | ||
2024-12-09 | mode-button: $ModeButtonScheduler: explicitly name the variable | 1 | -4/+8 | ||
2024-12-09 | mod/ssh-keys-import: $SSHKeysImportFile: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | check-routeros-update: pass script name to local function | 1 | -6/+8 | ||
2024-12-09 | mod/ssh-keys-import: $SSHKeysImport: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | Merge branch 'exit-error' into next | 57 | -57/+359 | ||
2024-12-09 | mod/scriptrunonce: $ScriptRunOnce: use $ExitError to indicate unintentional ↵ | 1 | -2/+4 | ||
error | |||||
2024-12-09 | global-functions: $FetchHuge: passing boolean to function is still broken... ↵ | 1 | -4/+4 | ||
🤨 | |||||
2024-12-09 | update-tunnelbroker: use $ExitError to indicate unintentional error | 1 | -1/+7 | ||
2024-12-09 | mod/notification-telegram: $SendTelegram: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | update-gre-address: use $ExitError to indicate unintentional error | 1 | -1/+5 | ||
2024-12-09 | mod/notification-telegram: $FlushTelegramQueue: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | telegram-chat: use $ExitError to indicate unintentional error | 1 | -1/+8 | ||
2024-12-09 | mod/notification-ntfy: $SendNtfy: use $ExitError to indicate unintentional error | 1 | -2/+4 | ||
2024-12-09 | sms-forward: use $ExitError to indicate unintentional error | 1 | -1/+7 | ||
2024-12-09 | mod/notification-ntfy: $FlushNtfyQueue: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | sms-action: use $ExitError to indicate unintentional error | 1 | -1/+5 | ||
2024-12-09 | mod/notification-matrix: $SendMatrix: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | ppp-on-up: use $ExitError to indicate unintentional error | 1 | -1/+5 | ||
2024-12-09 | mod/notification-matrix: $FlushMatrixQueue: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | packages-update: use $ExitError to indicate unintentional error | 1 | -1/+13 | ||
2024-12-09 | mod/notification-email: $SendEMail: use $ExitError to indicate unintentional ↵ | 1 | -2/+4 | ||
error | |||||
2024-12-09 | ospf-to-leds: use $ExitError to indicate unintentional error | 1 | -1/+5 | ||
2024-12-09 | mod/notification-email: $FlushEmailQueue: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error | |||||
2024-12-09 | netwatch-notify: use $ExitError to indicate unintentional error | 1 | -1/+5 | ||
2024-12-09 | mod/ipcalc: $IPCalc: use $ExitError to indicate unintentional error | 1 | -2/+4 | ||
2024-12-09 | netwatch-dns: use $ExitError to indicate unintentional error | 1 | -1/+8 | ||
2024-12-09 | mod/inspectvar: $InspectVar: use $ExitError to indicate unintentional error | 1 | -2/+4 | ||
2024-12-09 | mode-button: use $ExitError to indicate unintentional error | 1 | -1/+4 | ||
2024-12-09 | mod/bridge-port-vlan: $BridgePortVlan: use $ExitError to indicate ↵ | 1 | -2/+4 | ||
unintentional error |