.gitignore | ||
accesslist-duplicates.capsman | ||
accesslist-duplicates.local | ||
accesslist-duplicates.template | ||
bridge-port-to-default | ||
check-certificates | ||
check-routeros-update | ||
collect-wireless-mac.capsman | ||
collect-wireless-mac.local | ||
collect-wireless-mac.template | ||
daily-psk | ||
dhcp-lease-comment.capsman | ||
dhcp-lease-comment.local | ||
dhcp-lease-comment.template | ||
dhcp-to-dns | ||
email-backup | ||
email-daily-psk | ||
GeneratePSK | ||
global-config | ||
gps-track | ||
ipv6-update | ||
learn-mac-based-vlan | ||
lease-script | ||
leds-day-mode | ||
leds-night-mode | ||
leds-toggle-mode | ||
Makefile | ||
manage-umts | ||
mode-button-event | ||
mode-button-scheduler | ||
netwatch-syslog | ||
ppp-on-up | ||
README.md | ||
remove-packages | ||
rotate-ntp | ||
script-updates | ||
sms-action | ||
sms-forward | ||
ssh-keys-import | ||
super-mario-theme | ||
update-gre-address | ||
update-tunnelbroker |
RouterOS Scripts
RouterOS is the operating system developed by MikroTik for networking tasks. This repository holds a number of scripts to manage RouterOS devices or extend their functionality.
Use at your own risk!
Requirements
Latest version of the scripts require at least RouterOS 6.43 to function properly. The changelog lists the corresponding change as follows:
*) fetch - added "as-value" output format;
See branch pre-6-43
if you want to use the scripts on devices with older
RouterOS version.
Initial setup
The update script does server certificate verification, so first step is to download the certificates.
[admin@MikroTik] > / tool fetch "https://letsencrypt.org/certs/isrgrootx1.pem.txt"
status: finished
downloaded: 1KiBC-z pause]
total: 1KiB
duration: 1s
[admin@MikroTik] > / tool fetch "https://letsencrypt.org/certs/letsencryptauthorityx3.pem.txt"
status: finished
downloaded: 1KiBC-z pause]
total: 1KiB
duration: 1s
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 files to your MikroTik device.
Then we import the certificates.
[admin@MikroTik] > /certificate import file-name=isrgrootx1.pem.txt passphrase=""
certificates-imported: 1
private-keys-imported: 0
files-imported: 1
decryption-failures: 0
keys-with-no-certificate: 0
[admin@MikroTik] > /certificate import file-name=letsencryptauthorityx3.pem.txt passphrase=""
certificates-imported: 1
private-keys-imported: 0
files-imported: 1
decryption-failures: 0
keys-with-no-certificate: 0
Now let's download the main scripts, add them in configuration and remove the files.
[admin@MikroTik] > / system script add name=global-config source=([ / tool fetch check-certificate=yes-without-crl "https://git.eworm.de/cgit.cgi/routeros-scripts/plain/global-config" output=user as-value]->"data")
[admin@MikroTik] > / system script add name=script-updates source=([ / tool fetch check-certificate=yes-without-crl "https://git.eworm.de/cgit.cgi/routeros-scripts/plain/script-updates" output=user as-value]->"data")
The configuration needs to be tweaked for your needs. Make sure not to send your mails to mail@example.com
!
[admin@MikroTik] > / system script edit global-config source
And finally load the configuration and add a scheduler.
[admin@MikroTik] > / system script run global-config
[admin@MikroTik] > / system scheduler add name=global-config start-time=startup on-event=global-config
Updating scripts
To update existing scripts just run script-updates
.
[admin@MikroTik] > / system script run script-updates
Adding a script
To add a script from the repository create a configuration item first, then update scripts to fetch the source.
[admin@MikroTik] > / system script add name=check-routeros-update
[admin@MikroTik] > / system script run script-updates
Scheduler and events
Most scripts are designed to run regularly from
scheduler. We just
added check-routeros-update
, so let's run it every hour to make sure not to
miss an update.
[admin@MikroTik] > / system scheduler add name=check-routeros-update interval=1h on-event=check-routeros-update
Some events can run a script. If you want your DHCP hostnames to be available
in DNS use dhcp-to-dns
with the events from dhcp server. For a regular
cleanup add a scheduler entry.
[admin@MikroTik] > / system script add name=dhcp-to-dns
[admin@MikroTik] > / system script run script-updates
[admin@MikroTik] > / ip dhcp-server set lease-script=dhcp-to-dns [ find ]
[admin@MikroTik] > / system scheduler add name=dhcp-to-dns interval=5m on-event=dhcp-to-dns
There's much more to explore... Have fun!
Upstream
URL: GitHub.com
Mirror: eworm.de GitLab.com