#mikrotik — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mikrotik, aggregated by home.social.
-
On my RB5009 the kernel log reported a layer-2 loop, one line every 2 s, while RouterOS's log and port monitor showed a healthy device. I only saw it because I was already reading the kernel from inside the router.
With mikroscope, which I built: a Go agent in a RouterOS container that samples /proc, /sys, /dev/kmsg and perf at 1 to 100 Hz, and a CLI that installs it, records and forwards to 11 sinks.
-
On my RB5009 the kernel log reported a layer-2 loop, one line every 2 s, while RouterOS's log and port monitor showed a healthy device. I only saw it because I was already reading the kernel from inside the router.
With mikroscope, which I built: a Go agent in a RouterOS container that samples /proc, /sys, /dev/kmsg and perf at 1 to 100 Hz, and a CLI that installs it, records and forwards to 11 sinks.
-
On my RB5009 the kernel log reported a layer-2 loop, one line every 2 s, while RouterOS's log and port monitor showed a healthy device. I only saw it because I was already reading the kernel from inside the router.
With mikroscope, which I built: a Go agent in a RouterOS container that samples /proc, /sys, /dev/kmsg and perf at 1 to 100 Hz, and a CLI that installs it, records and forwards to 11 sinks.
-
On my RB5009 the kernel log reported a layer-2 loop, one line every 2 s, while RouterOS's log and port monitor showed a healthy device. I only saw it because I was already reading the kernel from inside the router.
With mikroscope, which I built: a Go agent in a RouterOS container that samples /proc, /sys, /dev/kmsg and perf at 1 to 100 Hz, and a CLI that installs it, records and forwards to 11 sinks.
-
On my RB5009 the kernel log reported a layer-2 loop, one line every 2 s, while RouterOS's log and port monitor showed a healthy device. I only saw it because I was already reading the kernel from inside the router.
With mikroscope, which I built: a Go agent in a RouterOS container that samples /proc, /sys, /dev/kmsg and perf at 1 to 100 Hz, and a CLI that installs it, records and forwards to 11 sinks.
-
Discover how CERT Polska used AI to uncover the critical MikroTrick exploit in MikroTik RouterOS, allowing unauthenticated administrative access.
-
Discover how CERT Polska used AI to uncover the critical MikroTrick exploit in MikroTik RouterOS, allowing unauthenticated administrative access.
-
Discover how CERT Polska used AI to uncover the critical MikroTrick exploit in MikroTik RouterOS, allowing unauthenticated administrative access.
-
Discover how CERT Polska used AI to uncover the critical MikroTrick exploit in MikroTik RouterOS, allowing unauthenticated administrative access.