Noremove wireguard too
remove winbox support
No I want to see wireguard logs for any client peers experiencing issues. These are "server" endpoints (no client endpoint-ip/port information configured) and yet they are trying to connect to nowhere and spamming the logs about it in the processJust disable wireguard logging, sheesh.
So it's not MikroTik's business/duty to inform customers of a software change correcting regulatory channel enforcement? I'll wait for your infinite insight in answering this question thenIf you use a peripheral outside of how it was meant to be used, that's your business.
Yepp this is what's bothering me. Is it possible to change this? (The default should also be changed IMO)I think apart from the style, the worst thing was the text on the left and the author on the right…
Yes - finally!! Confirmed fixed, Thanks!!*) container - fixed file ownership after system upgrade for containers running on internal disk;
*) container - fixed multiple container automatic startup on boot;
ssh admin@mikrotik /interface/ethernet/etherX/set enabled false
+1 for routing/rules address-listsProbably my fault, I asked for address lists in Routing Rules and it got lost in translation ;-)
Best of both worlds... Can winbox talk to, and be used to configure OpenWrt ?Enlighten me please...
Why would one run Openwrt in Docker on Routeros when it can be run natively on lots of Tik HW ??
Natively performance should be better ?
No plans myself, just wondering why.
Ok Interesting! I'll try it like that & expecting good results. Thanks:)are you running any command inside container? If not this is how it should behave.
LOL, Good comparison, mateThe MikroTik is very much like the picture labeled woman in this article, compared to a "consumer" based router (more like the one labeled man).
Absolutely, thanks for all your service, can't fault or discredit you there (or come anywhere near to matching the contributions you've made). Sorry for clashing with you, I'm glad we see eye to eye again. See you aroundas you can see in other posts, I don't just "bark"...
How can we run Wireguard on 6.48.6 without investing in other external hardware ?What have 7.2 for hAP ac2 that 6.48.6 can not do?
Cool trick. Will this have any impact on CPU/firewall performance however? Maybe there's (should be!) a better way to do this than having to create a whole bridge just for a single variable?put the value in the name of one fake bridge...
?? it doesRouterOS does not support standard Tagged or Untagged ports
Dude is supported now on v7.2rc series+1
Android or web view for the maps and graphs.
Also I'm waiting to update to v7 because the lack of dude