Yup. FWIW, the docs on how this works are lacking . My guess it operates a "matcher"/selector, not like the firewall "filter"/etc - or at least that how I rationalize the logic here.... really wierd...
Yup. I'd look at the CPU usage on the Proxmox host, if CPU is low there, but CHR is high... you should increase the CPU cores assigned to CHR. Or perhaps memory too.Which again points at CHR itself rather than at virtualization platform.
with an M.2 (or miniPCIe) slot (aka the ax version of wAPacR)?wAP ax will be a very small device and is coming very very soon (question of days or weeks)
Feel free to post your needs/question(s) and any relevant config.@amm0, would it be possible to ask you a question about my relatively simple setup? If so, I would love to reach out. Thanks!
sudo mv /usr/bin/winbox-linux /usr/bin/`shuf -n 1 /usr/share/dict/words`box
LOL. I couldn't even proofread my text.Edit: @Amm0 was faster...
Perhaps if you're in Europe...
hello everybody! sorry if this isnt the right place for this, but...
Please keep this forum topic strictly related to this particular RouterOS release.
Maybe. Some hardware malfunction causing issues in the kernel is exactly kinda thing watchdog was designed to catch.Most likely hardware.....