mirror of
https://git.eworm.de/cgit/routeros-scripts
synced 2025-06-21 01:15:42 +02:00
Merge branch 'external-links' into next
This commit is contained in:
commit
507a520994
13 changed files with 47 additions and 31 deletions
|
@ -13,7 +13,7 @@ Installing from branches
|
|||
> ⚠️ **Warning**: Living on the edge? Great, read on!
|
||||
> If not: Please use the `main` branch and leave this page!
|
||||
|
||||
These scripts are developed in a [git](https://git-scm.com/) repository.
|
||||
These scripts are developed in a [git ↗️](https://git-scm.com/) repository.
|
||||
Development and experimental branches are used to provide early access
|
||||
for specific changes. You can install scripts from these branches
|
||||
for testing.
|
||||
|
|
|
@ -21,7 +21,7 @@ first step of [installation](README.md#the-long-way-in-detail) is importing
|
|||
the certificate.
|
||||
|
||||
The scripts can install additional certificates when required. This happens
|
||||
from this repository if available, or from [mkcert.org](https://mkcert.org)
|
||||
from this repository if available, or from [mkcert.org ↗️](https://mkcert.org)
|
||||
as a fallback.
|
||||
|
||||
Get the certificate's CommonName
|
||||
|
@ -29,7 +29,7 @@ Get the certificate's CommonName
|
|||
|
||||
But how to determine what certificate may be required? Often easiest way
|
||||
is to use a desktop browser to get that information. This demonstration uses
|
||||
[Mozilla Firefox](https://www.mozilla.org/firefox/).
|
||||
[Mozilla Firefox ↗️](https://www.mozilla.org/firefox/).
|
||||
|
||||
Let's assume we want to make sure the certificate for
|
||||
[git.eworm.de](https://git.eworm.de/) is available. Open that page in the
|
||||
|
|
|
@ -31,7 +31,7 @@ for details!
|
|||
## Donations
|
||||
|
||||
Add yourself to the list,
|
||||
[donate with PayPal](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=A4ZXBD6YS2W8J)!
|
||||
[donate with PayPal ↗️](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=A4ZXBD6YS2W8J)!
|
||||
|
||||
* Abdul Mannan Abbasi
|
||||
* Andrea Ruffini Perico
|
||||
|
|
38
README.md
38
README.md
|
@ -10,13 +10,14 @@ RouterOS Scripts
|
|||
|
||||

|
||||
|
||||
[RouterOS](https://mikrotik.com/software) is the operating system developed
|
||||
by [MikroTik](https://mikrotik.com/aboutus) for networking tasks. This
|
||||
repository holds a number of [scripts](https://wiki.mikrotik.com/wiki/Manual:Scripting)
|
||||
[RouterOS ↗️](https://mikrotik.com/software) is the operating system developed
|
||||
by [MikroTik ↗️](https://mikrotik.com/aboutus) for networking tasks. This
|
||||
repository holds a number of [scripts ↗️](https://wiki.mikrotik.com/wiki/Manual:Scripting)
|
||||
to manage RouterOS devices or extend their functionality.
|
||||
|
||||
*Use at your own risk*, pay attention to
|
||||
[license and warranty](#license-and-warranty)!
|
||||
[license and warranty](#license-and-warranty), and
|
||||
[disclaimer on external links](#disclaimer-on-external-links)!
|
||||
|
||||
Requirements
|
||||
------------
|
||||
|
@ -35,7 +36,7 @@ Specific scripts may require even newer RouterOS version.
|
|||
> running RouterOS v6 switch to `routeros-v6` branch!
|
||||
|
||||
Starting with RouterOS 7.17 the
|
||||
[device-mode](https://help.mikrotik.com/docs/spaces/ROS/pages/93749258/Device-mode)
|
||||
[device-mode ↗️](https://help.mikrotik.com/docs/spaces/ROS/pages/93749258/Device-mode)
|
||||
has been extended to give more fine-grained control over what features are
|
||||
available. You need to enable `scheduler` and `fetch` at least, specific
|
||||
scripts may require additional features.
|
||||
|
@ -61,9 +62,9 @@ First time users should take the long way below.
|
|||
### Live presentation
|
||||
|
||||
Want to see it in action? I've had a presentation [Repository based
|
||||
RouterOS script distribution](https://www.youtube.com/watch?v=B9neG3oAhcY)
|
||||
RouterOS script distribution ↗️](https://www.youtube.com/watch?v=B9neG3oAhcY)
|
||||
including demonstation recorded live at [MUM Europe
|
||||
2019](https://mum.mikrotik.com/2019/EU/) in Vienna.
|
||||
2019 ↗️](https://mum.mikrotik.com/2019/EU/) in Vienna.
|
||||
|
||||
> ⚠️ **Warning**: Some details changed. So see the presentation, then follow
|
||||
> the steps below for up-to-date commands.
|
||||
|
@ -83,7 +84,7 @@ Note that the commands above do *not* verify server certificate, so if you
|
|||
want to be safe download with your workstations's browser and transfer the
|
||||
file to your MikroTik device.
|
||||
|
||||
* [ISRG Root X2](https://letsencrypt.org/certs/isrg-root-x2.pem)
|
||||
* [ISRG Root X2 ↗️](https://letsencrypt.org/certs/isrg-root-x2.pem)
|
||||
|
||||
Then we import the certificate.
|
||||
|
||||
|
@ -194,7 +195,7 @@ Scheduler and events
|
|||
--------------------
|
||||
|
||||
Most scripts are designed to run regularly from
|
||||
[scheduler](https://wiki.mikrotik.com/wiki/Manual:System/Scheduler). We just
|
||||
[scheduler ↗️](https://wiki.mikrotik.com/wiki/Manual:System/Scheduler). We just
|
||||
added `check-routeros-update`, so let's run it daily to make sure not to
|
||||
miss an update.
|
||||
|
||||
|
@ -328,7 +329,7 @@ Possibly a scheduler and other configuration has to be removed as well.
|
|||
Contact
|
||||
-------
|
||||
|
||||
We have a Telegram Group [RouterOS-Scripts](https://t.me/routeros_scripts)!
|
||||
We have a Telegram Group [RouterOS-Scripts ↗️](https://t.me/routeros_scripts)!
|
||||
|
||||
[](https://t.me/routeros_scripts)
|
||||
|
||||
|
@ -352,7 +353,7 @@ at github.
|
|||
This project is developed in private spare time and usage is free of charge
|
||||
for you. If you like the scripts and think this is of value for you or your
|
||||
business please consider to
|
||||
[donate with PayPal](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=A4ZXBD6YS2W8J).
|
||||
[donate with PayPal ↗️](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=A4ZXBD6YS2W8J).
|
||||
|
||||
[](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=A4ZXBD6YS2W8J)
|
||||
|
||||
|
@ -371,6 +372,21 @@ but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
[GNU General Public License](COPYING.md) for more details.
|
||||
|
||||
Disclaimer on external links
|
||||
----------------------------
|
||||
|
||||
Our website contains links to the websites of third parties ("external
|
||||
links"). As the content of these websites is not under our control, we
|
||||
cannot assume any liability for such external content. In all cases, the
|
||||
provider of information of the linked websites is liable for the content
|
||||
and accuracy of the information provided. At the point in time when the
|
||||
links were placed, no infringements of the law were recognisable to us.
|
||||
As soon as an infringement of the law becomes known to us, we will
|
||||
immediately remove the link in question.
|
||||
|
||||
> 💡️ **Hint**: All external links are marked with an arrow pointing
|
||||
> diagonally in an up-right (or north-east) direction (↗️).
|
||||
|
||||
Upstream
|
||||
--------
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Description
|
|||
-----------
|
||||
|
||||
This script uploads
|
||||
[binary backup to Mikrotik cloud](https://wiki.mikrotik.com/wiki/Manual:IP/Cloud#Backup).
|
||||
[binary backup to Mikrotik cloud ↗️](https://wiki.mikrotik.com/wiki/Manual:IP/Cloud#Backup).
|
||||
|
||||
> ⚠️ **Warning**: The used command can hit errors that a script can with
|
||||
> workaround only. A notification *should* be sent anyway. But it can result
|
||||
|
|
|
@ -17,7 +17,7 @@ Description
|
|||
-----------
|
||||
|
||||
This script saves the current configuration to fallback
|
||||
[partition](https://wiki.mikrotik.com/wiki/Manual:Partitions).
|
||||
[partition ↗️](https://wiki.mikrotik.com/wiki/Manual:Partitions).
|
||||
It can also copy-over the RouterOS installation when run interactively
|
||||
or just before a feature update.
|
||||
|
||||
|
|
|
@ -30,8 +30,8 @@ automatically is supported.
|
|||
> ⚠️ **Warning**: Installing updates is important from a security point
|
||||
> of view. At the same time it can be source of serve breakage. So test
|
||||
> versions in lab and read
|
||||
> [changelog](https://mikrotik.com/download/changelogs/) and
|
||||
> [forum](https://forum.mikrotik.com/viewforum.php?f=21) before deploying
|
||||
> [changelog ↗️](https://mikrotik.com/download/changelogs/) and
|
||||
> [forum ↗️](https://forum.mikrotik.com/viewforum.php?f=21) before deploying
|
||||
> to your production environment! Automatic updates should be handled
|
||||
> with care!
|
||||
|
||||
|
|
|
@ -19,10 +19,10 @@ Description
|
|||
This script downloads, imports and updates firewall address-lists. Its main
|
||||
purpose is to block attacking ip addresses, spam hosts, command-and-control
|
||||
servers and similar malicious entities. The default configuration contains a
|
||||
[collective list by GitHub user @stamparm](https://github.com/stamparm/ipsum),
|
||||
lists from [dshield.org](https://dshield.org/) and
|
||||
[blocklist.de](https://www.blocklist.de/), and lists from
|
||||
[spamhaus.org](https://spamhaus.org/) are prepared.
|
||||
[collective list by GitHub user @stamparm ↗️](https://github.com/stamparm/ipsum),
|
||||
lists from [dshield.org ↗️](https://dshield.org/) and
|
||||
[blocklist.de ↗️](https://www.blocklist.de/), and lists from
|
||||
[spamhaus.org ↗️](https://spamhaus.org/) are prepared.
|
||||
|
||||
The address-lists are updated in place, so after initial import you will not
|
||||
see situation when the lists are not populated.
|
||||
|
|
|
@ -72,7 +72,7 @@ The configuration goes to `global-config-overlay`, these are the parameters:
|
|||
> your local `global-config-overlay` and modify it to your specific needs.
|
||||
|
||||
These patterns are matched as
|
||||
[regular expressions](https://wiki.mikrotik.com/wiki/Manual:Regular_Expressions).
|
||||
[regular expressions ↗️](https://wiki.mikrotik.com/wiki/Manual:Regular_Expressions).
|
||||
To forward **all** (ignoring severity) log messages with topics `account`
|
||||
(which includes user logins) and `dhcp` you need something like:
|
||||
|
||||
|
|
|
@ -32,7 +32,7 @@ Configuration
|
|||
-------------
|
||||
|
||||
Set up your device's
|
||||
[e-mail settings](https://wiki.mikrotik.com/wiki/Manual:Tools/email).
|
||||
[e-mail settings ↗️](https://wiki.mikrotik.com/wiki/Manual:Tools/email).
|
||||
Also make sure the device has correct time configured, best is to set up
|
||||
the ntp client.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Description
|
|||
-----------
|
||||
|
||||
This module adds support for sending notifications via
|
||||
[Matrix](https://matrix.org/) via client server api. A queue is used to
|
||||
[Matrix ↗️](https://matrix.org/) via client server api. A queue is used to
|
||||
make sure notifications are not lost on failure but sent later.
|
||||
|
||||
Requirements and installation
|
||||
|
|
|
@ -17,7 +17,7 @@ Description
|
|||
-----------
|
||||
|
||||
This module adds support for sending notifications via
|
||||
[Ntfy](https://ntfy.sh/). A queue is used to make sure
|
||||
[Ntfy ↗️](https://ntfy.sh/). A queue is used to make sure
|
||||
notifications are not lost on failure but sent later.
|
||||
|
||||
Requirements and installation
|
||||
|
@ -28,7 +28,7 @@ Just install the module:
|
|||
$ScriptInstallUpdate mod/notification-ntfy;
|
||||
|
||||
Also install the Ntfy app on your mobile device or use the
|
||||
[web app](https://ntfy.sh/app) in a browser of your choice.
|
||||
[web app ↗️](https://ntfy.sh/app) in a browser of your choice.
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
|
|
@ -17,7 +17,7 @@ Description
|
|||
-----------
|
||||
|
||||
This module adds support for sending notifications via
|
||||
[Telegram](https://telegram.org/) via bot api. A queue is used to make sure
|
||||
[Telegram ↗️](https://telegram.org/) via bot api. A queue is used to make sure
|
||||
notifications are not lost on failure but sent later.
|
||||
|
||||
Requirements and installation
|
||||
|
@ -33,7 +33,7 @@ and create an account.
|
|||
Configuration
|
||||
-------------
|
||||
|
||||
Open Telegram, then start a chat with [BotFather](https://t.me/BotFather) and
|
||||
Open Telegram, then start a chat with [BotFather ↗️](https://t.me/BotFather) and
|
||||
create your own bot:
|
||||
|
||||

|
||||
|
@ -102,7 +102,7 @@ Tips & Tricks
|
|||
### Set a profile photo
|
||||
|
||||
You can use a profile photo for your bot to make it recognizable. Open the
|
||||
chat with [BotFather](https://t.me/BotFather) and set it there.
|
||||
chat with [BotFather ↗️](https://t.me/BotFather) and set it there.
|
||||
|
||||

|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue