Wow, that's a bunch of useful information to process for me.
Thanks to all of you for taking the time to help!
I tried it but I did not come to grips with it.
+1.1. Detect Internet doesn't always work.
... and don't get me started on RFC 2549 compatibility. ;-)我刚刚discovered that this release COMPLETELY FAILS in compatibility tests with RFC 1149. Time to sell all my MikroTik gear and go buy Uni-TP stuff instead.
I can confirm that and add the fact that this has to do with firmware 6.48. RouterOS 6.48 with Firmware 6.47.8 on a hEX PoE has health info as it should.hEX PoE lost health info in 6.48
hex.PNG
Could you please elaborate on that point?*) sstp - fixed "idle-timeout" on TILE and CHR devices;
Great solution, thanks a lot!Add two additional routing tables with default routes for each of WAN connections.
And then a couple of routing rules, that restrict usage of the tables depending on src IP:
LMAOBeep is originally made for Beeps, not for play a "Star Wars -- The Imperial March"Note is orginally made for notes, not for art
No, actually I've got a bunch of "old" hAP ac devices lying around and was curious if they'd do any good in the mentioned scenario. May I assume you don't think so?You mean hAP AC2?
That could allow for better airtime usage, in theory.
I get that. But the webfig torch NEVER shows more than the two lines to be seen in the screenshot, no matter what traffic is to be seen via winbox.I guess this likely is the point. Torch is a "right now" tool, not a "historical data" tool.roughly the same time.
Time Oct/22/2018 19:15:05
Buffer memory
Topics
system
error
critical
Message router was rebooted without proper shutdown by watchdog timer