Age | Commit message (Collapse) | Author | Files | Lines |
|
The lease comment is supposed to be a human readable string... But we
could allow parsable information.
|
|
|
|
|
|
|
|
|
|
No functional change for the user... The migration is done
automatically.
|
|
|
|
... 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.
|
|
|
|
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%.
---- ✂️ ----
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This becomes complicated with legacy wireless and wifiwave2 package, old
and new CAPsMAN. Let's just drop the check.
|
|
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!)
|
|
|
|
|
|
---- ✂️ ----
🗃️📉️ Health warning: free RAM
The available free RAM on MikroTik is at 18% (47MiB)!
---- ✂️ ----
🗃️📈️ Health recovery: free RAM
The available free RAM on MikroTik increased to 65% (168MiB).
---- ✂️ ----
|
|
---- ✂️ ----
🧮️📈️ Health warning: CPU load
The average CPU load on MikroTik is at 76%!
---- ✂️ ----
🧮️📉️ Health recovery: CPU load
The average CPU load on MikroTik decreased to 64%.
---- ✂️ ----
|
|
|
|
|
|
|
|
|
|
We had...
◀ Go back to main README
▲ Go back to top
... and switch to...
⬅️ Go back to main README
⬆️ Go back to top
|
|
|
|
|
|
|
|
|
|
---- ✂️ ----
📨 SMS Forwarding from 7277
Received this message by MikroTik from 7277:
On oct/17/2022 13:44:10 GMT -0 type class-0:
Welcome to our network!
---- ✂️ ----
|
|
---- ✂️ ----
❌ Netwatch Notify: example.com down
The host 'example.com' (93.184.216.34) is down since oct/19/2022 16:27:03.
---- ✂️ ----
✅ Netwatch Notify: example.com up
The host 'example.com' (93.184.216.34) is up since oct/19/2022 17:03:00.
It was down for 6 checks since oct/19/2022 16:27:03.
---- ✂️ ----
|
|
---- ✂️ ----
⚠️ Log Forwarding
The log on MikroTik contains these 3 messages after 6d23:55:18 uptime.
● 13:24:02 script;error backup-cloud: Failed uploading backup for MikroTik to cloud!
● 13:24:17 system;info;account user admin logged in from 192.168.88.177 via ssh
● 13:24:57 system;info;account user admin logged out from 192.168.88.177 via ssh
---- ✂️ ----
|
|
---- ✂️ ----
📅 daily PSK Guest-Wifi
This is the daily PSK on MikroTik:
SSID: Guest-Wifi
PSK: S3cr3tStr1ng
Date: oct/18/2022
A client device specific rule must not exist!
🔗 https://www.eworm.de/cgi-bin/cqrlogo-wifi.cgi?scale=8&level=1&ssid=Guest-Wifi&pass=S3cr3tStr1ng
---- ✂️ ----
|
|
---- ✂️ ----
📱 48:F1:7F:D0:E5:4E connected to Wifi
A device with unknown MAC address connected to Wifi on MikroTik.
Controller: MikroTik
Interface: wl5-wifi
SSID: Wifi
MAC: 48:F1:7F:D0:E5:4E
Vendor: Intel Corporate
Hostname: host-523c8e0e
Address: 192.168.20.254
DNS name: host-523c8e0e.dhcp.MikroTik.example.com
Date: oct/20/2022 09:21:56
---- ✂️ ----
|
|
---- ✂️ ----
✨ RouterOS update
A new RouterOS version 7.6 is available for MikroTik.
Hostname: MikroTik
Board name: CHR
Architecture: x86_64
RouterOS:
Channel: stable
Installed: 7.5
Available: 7.6
RouterOS-Scripts:
Version: 85
🔗 https://mikrotik.com/download/changelogs/stable-release-tree
---- ✂️ ----
|
|
---- ✂️ ----
✨ LTE firmware upgrade
A new firmware version R11e-LTE6_V033 is available for LTE interface lte on MikroTik.
Interface: MikroTik R11e-LTE6
Installed: R11e-LTE6_V027
Available: R11e-LTE6_V033
---- ✂️ ----
|
|
---- ✂️ ----
⚡📉 Health warning: voltage
The voltage on MikroTik jumped more than 10%.
old value: 16.2V
new value: 12.4V
---- ✂️ ----
🔥 Health warning: temperature
The temperature on MikroTik is above threshold: 51°C
---- ✂️ ----
✅ Health recovery: temperature
The temperature on MikroTik dropped below threshold: 47°C
---- ✂️ ----
❌ Health warning: psu1-state
The power supply unit 'psu1-state' on MikroTik failed!
---- ✂️ ----
✅ Health recovery: psu1-state
The power supply unit 'psu1-state' on MikroTik recovered!
---- ✂️ ----
|
|
---- ✂️ ----
🔏 Certificate renewed
A certificate on MikroTik has been renewed.
Name: example.com
CommonName: example.com
Private key: available
Fingerprint: cc54cdd01fcd7698ecb71213874be776906eb33d26cd57754d168632f14c4c8b
Issuer: R3
Validity: sep/08/2022 03:50:56 to dec/07/2022 03:50:55
Expires in: 8w 3d 12:03:30
---- ✂️ ----
|
|
---- ✂️ ----
💾⬆️ Backup & Config upload
Backup and config export upload for MikroTik.
Hostname: MikroTik
Board name: CHR
Architecture: x86_64
RouterOS:
Channel: stable
Installed: 7.6
RouterOS-Scripts:
Version: 85
Backup file: MikroTik_example_com.backup
Config file: MikroTik_example_com.rsc
---- ✂️ ----
|
|
---- ✂️ ----
💾☁️ Cloud backup
Uploaded backup for MikroTik to cloud.
Hostname: MikroTik
Board name: CHR
Architecture: x86_64
RouterOS:
Channel: stable
Installed: 7.6
RouterOS-Scripts:
Version: 85
Name: cloud-20221020-092419
Size: 370767 B (362 KiB)
Download key: LLDBfPcWXxmSetWilqeJX5V
---- ✂️ ----
|
|
This is a good condidate:
https://showipv6.de/
We can drop the cloud code, which seems to be unreliable in somd
situations.
|
|
|
|
To filter in firewall you should use something like this:
/ip/firewall/filter/add action=reject chain=output out-interface-list=WAN port=514 protocol=udp reject-with=icmp-admin-prohibited;
/ip/firewall/filter/add action=reject chain=forward out-interface-list=WAN port=514 protocol=udp reject-with=icmp-admin-prohibited;
|
|
|
|
|
|
This broke with:
* doc/netwatch-dns: giving hostname in comment is not required
9853943a365639f675fba0bb9c1d64b7edfd00d7
|
|
... and also update all version numbers to match current release.
|
|
... and also drop the version from global-config and
global-config-overlay.
|
|
|
|
|
|
Starting with RouterOS 7.4 the netwatch tool has been extended, it can
now do tcp and http probes. Rename the parameter for reasonable naming
with services.
|
|
|
|
|
|
|
|
For RouterOS 6.x a separate package 'ntp' exists. This adds server
functionality, but allows ip addresses for the client only. I added the
script 'rotate-ntp' to update addresses from names...
Now with RouterOS 7.x there's no extra package and the limitation does
no longer exist. So let's just drop the script.
This adds migration code, that...
* removes the script from configuration
* removes a scheduler from configuration
* sets the configured ntp pool name for ntp client
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|