Commit graph

264 commits

Author SHA1 Message Date
Christian Hesse
ee94024dca dhcp-to-dns: get domain from dhcp server's network definition 2023-04-24 22:26:26 +02:00
Christian Hesse
9617095022 check-certificates: try all SANs for download 2023-04-07 23:36:09 +02:00
Christian Hesse
4073daa139 check-certificates: include SANs in information 2023-04-07 22:53:33 +02:00
Christian Hesse
68364d4a50 doc/check-health: use an unusual interval 2023-03-31 17:45:55 +02:00
Christian Hesse
d700dbc00e dhcp-to-dns: support host name from dhcp lease comment
The lease comment is supposed to be a human readable string... But we
could allow parsable information.
2023-03-28 12:05:47 +02:00
Christian Hesse
b22a84ed0f doc/dhcp-to-dns: mention A record and optional CNAME record 2023-03-28 11:42:58 +02:00
Christian Hesse
b66364d716 doc/netwatch-notify: prevent escaping code in hook by creating a script 2023-03-20 13:32:39 +01:00
Christian Hesse
f7962f5d79 doc/netwatch-notify: move hint on notification settings up 2023-03-20 12:35:34 +01:00
Christian Hesse
650c362ed9 netwatch-notify: support note in notification 2023-03-20 12:35:34 +01:00
Christian Hesse
a832fd04ef rename scripts and add file extension ".rsc"
No functional change for the user... The migration is done
automatically.
2023-03-07 22:26:01 +01:00
Christian Hesse
4ca8f83a52 ... and update the logo in notifications 2023-03-06 21:07:58 +01:00
Christian Hesse
d2d913ec19 check-routeros-update: allow to install all updates 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.
2023-03-06 21:06:48 +01:00
Christian Hesse
a9741336b8 doc/check-routeros-update: update wording and details 2023-03-03 14:08:48 +01:00
Christian Hesse
c48509683c check-health: wording: load -> utilization
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%.
---- ✂️ ----
2023-02-14 20:24:06 +01:00
Christian Hesse
e50e25c638 doc/check-health: make the voltage limit a separate point 2023-02-13 21:10:35 +01:00
Christian Hesse
b6d2cb44c1 doc/check-health: add line break between screenshots 2023-02-13 21:10:35 +01:00
Christian Hesse
62707dc549 ipv6-update: support host addresses in address-list 2023-02-10 11:36:12 +01:00
Christian Hesse
15fc0b91e9 doc/backup-upload: new option $BackupSendGlobalConfig 2023-02-08 09:44:52 +01:00
Christian Hesse
f2f7d66b2d doc/backup-email: new option $BackupSendGlobalConfig 2023-02-08 09:44:21 +01:00
Christian Hesse
08383daa5c telegram-chat: always reply to origin chat 2023-02-02 10:06:42 +01:00
Christian Hesse
bf1af61d2d doc/telegram-chat: give an example on how to work around command runtime 2023-02-01 17:28:45 +01:00
Christian Hesse
049a029170 doc/telegram-chat: add hint on output size 2023-02-01 14:30:52 +01:00
Christian Hesse
7e7987afec doc/telegram-chat: add hint on command runtime 2023-02-01 11:29:56 +01:00
Christian Hesse
8f47bc9836 doc/telegram-chat: warn about changing group id 2023-02-01 11:29:51 +01:00
Christian Hesse
8b488cb82f doc/telegram-chat: allow bots to receive messages in a group 2023-01-31 18:11:22 +01:00
Christian Hesse
cbc547332e check-routeros-update: drop check for cap
This becomes complicated with legacy wireless and wifiwave2 package, old
and new CAPsMAN. Let's just drop the check.
2023-01-31 17:27:15 +01:00
Christian Hesse
819c7294c6 introduce telegram-chat
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!)
2023-01-31 17:26:51 +01:00
Christian Hesse
555d0e8bfc check-certificates: make the warning time configurable 2023-01-23 17:46:03 +01:00
Christian Hesse
36a8938dea doc/check-certificates: document the renew time 2023-01-23 17:45:22 +01:00
Christian Hesse
6780e1a24c check-health: monitor free RAM
---- ✂️ ----
🗃️📉️ 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).
---- ✂️ ----
2023-01-20 23:20:53 +01:00
Christian Hesse
75bd14267e check-health: monitor CPU load
---- ✂️ ----
🧮📈️ 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%.
---- ✂️ ----
2023-01-20 23:13:27 +01:00
Christian Hesse
2294ac77a8 doc/log-forward: add tips and tricks 2023-01-20 00:34:27 +01:00
Christian Hesse
cfb31e840c doc/log-forward: add some more details 2023-01-18 11:53:57 +01:00
Christian Hesse
aabc6b22fe doc/daily-psk: drop the start-date from scheduler 2023-01-12 23:28:37 +01:00
Christian Hesse
ab306ad3c7 doc/daily-psk: add missing bits for CAPsMAN 2023-01-12 23:26:23 +01:00
Christian Hesse
34ed387343 use arrows with emoji representation
We had...

  ◀ Go back to main README
  ▲ Go back to top

... and switch to...

  ⬅️ Go back to main README
  ⬆️ Go back to top
2023-01-11 12:28:31 +01:00
Christian Hesse
80671e3803 doc/sms-forward: take care of harmful commands in hooks 2023-01-10 08:58:33 +01:00
Anatoly Bubenkov
ea09a18d3f sms-forward: support hooks 2023-01-10 08:58:33 +01:00
Christian Hesse
88b34cfb39 doc/sms-forward: reorder configuration 2023-01-09 15:35:57 +01:00
Christian Hesse
a7bdebbfb0 doc/mod/notification-email: mention correct time 2022-11-22 21:49:34 +01:00
Christian Hesse
aef88e313b doc/sms-forward: update notification
---- ✂️ ----
📨 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!
---- ✂️ ----
2022-10-20 11:37:09 +02:00
Christian Hesse
ee7836263f doc/netwatch-notify: update notifications
---- ✂️ ----
 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.
---- ✂️ ----
2022-10-20 11:37:05 +02:00
Christian Hesse
4f8a2bd8e2 doc/log-forward: update notification
---- ✂️ ----
⚠️ 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
694f4e2894 doc/daily-psk: update notification
---- ✂️ ----
📅 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
dddbd3da27 doc/collect-wireless-mac: update notification
---- ✂️ ----
📱 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
6940f851b0 doc/check-routeros-update: update notification
---- ✂️ ----
 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
863cf9cae0 doc/check-lte-firmware-upgrade: update notification
---- ✂️ ----
 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
692ed21262 doc/check-health: update notifications
---- ✂️ ----
📉 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!
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
fadf4d5008 doc/check-certificates: update notification
---- ✂️ ----
🔏 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00
Christian Hesse
98844d85d5 doc/backup-upload: update notification
---- ✂️ ----
💾⬆️ 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
---- ✂️ ----
2022-10-20 11:28:09 +02:00