Interface comments in alerts, and a DHCP gauge that adds up
New
{{comment}}notification variable. Alerts can now carry the RouterOS comment for the
interface, NetWatch host, VPN peer or BGP peer they are about. Add it to your template under
Settings, Notifications, Message Templates, for example{{alertType}}: {{detail}} ({{comment}}).
It is not in the default template, so nothing changes unless you add it.
(#116, thanks
@erion1979-cell)
Fixed
- "DHCP used IPs" over-reported utilisation. Static reservations nobody was using counted as in
use, and leases that disappeared were never cleared in poll mode. A /23 could read 507 of 512 used
with about 110 addresses actually held. (#115,
thanks @erion1979-cell) - Traffic chart could silently lose most of its window and redraw short, then refill. One
out-of-order sample, which a router emits when NTP corrects its clock, ended the redraw early. - Backup pruning could offer every real restore point for deletion if a file it did not create
sat in the backup folder. - Report rate card showed the wrong sample count, counting bandwidth rows instead of traffic
samples. - A firewall address written without a prefix matched every address, so blocking a single host
did not raise the lockout warning it should have. - Queue edits recorded changes nobody made, and said a field had been cleared when the router
had kept its value. - Action status messages never appeared on the WAN, Queues, Router Users and Packages pages.
- Five Queues column headers offered a sort they do not have. They are no longer marked
sortable: a simple queue is first match wins, so position is meaningful. - Three values were rendered but never sent: the upgrade dialog's channel line, the topology
core node name, and the Bandwidth page device count.
Internal
- The test suite stopped under-reporting its own size. 1527 tests, stable across runs.
- CI and the pre-push hook now run the suite in the image that carries the dev tooling.
- Three checks run on every build: orphaned element lookups, payload fields read but never sent, and
variables written but never read.
Discussion
- Should MikroDash be rewritten in Go and TypeScript? Comments wanted, objections as welcome as
support. (#114)