/ip routeSorry, I don't know what you meanThat's why you're getting a command error. Now is routing "mark" in the firewall, it a "table" routes.
To @anav's point, your problem is not the same. IPSec isn't mentions at all here & that add more complexity.I have exactly the same problem as Chaosphere64. [...] IPSec Lan2Lan connection [...] How can I solve this problem?
What's new in 7.15beta8 (2024-Mar-21 09:12):
*) bridge - added MVRP support;
Or move the ZT client part into the main package, and leave the controller bit as zerotier.npk.Since the client is so small (less than 10 MB), it's possible it would fit even on smaller devices.
Thanks for the update. I know it's not an easy problem to "just fix". But the 16MB problem has been on a slow simmer for "some time" .Our team of experts is working on this issue at this very moment.
I don't see anything in title bar either, at least in winbox v3.40.He sees in the future. Hopefully.maybe I'm blind, can't see anything license related in the winbox title bar
If you remove the (timeout>60) matcher in @rextended version, it should still work against all records. The "where" still has something to do e.g. [:remove $".id"], even without matchers.The above will run even without making sure any 10 or 15 or 30 or 60...
SUP-100671, opened Dec 2022.Ah, I wasn't aware of that detail regarding mDNS. I suggest you open a feature request ticket then :)
SNMP is capturing stdout, as-value surpasses that. And /system/script don't "return" anything, like a function or [/cmd/get value] would – so :put is all ya got to SNMP.This is very weird:
[...]
Worked, need to write :put
:put [ping address=8.8.8.8 interval=200ms count=3 as-value]
I think that's what they're working on... There are a few moving parts in re-mapping . The where/how take some testing I think.This is what I was asking before. Couldn't you use network address other than 0.0.0.0/0.
I didn't mean to attack-the-attacker either. @anav you do good work here. Just solving some of these "non-problems" is what sometimes eventually yields to simpler "pathways to success". But always a lot of complaining and arguing before that.I'm blushing!!
Ahead of the times. VRF and Docker, before either were invented. Left with /container that can't run RouterOS inside it (like MetaROUTER could), but some RouterOS-on-RouterOS certainly be one way to ofuscate things on V6.No one remember MetaROUTER?
LOL. I have the edit window open but didn't hit save.And remove the port 8728 from the url...
/tool fetch url=http://172.16.0.1/rest/ip/address output=user
Maybe some Kleenex™ would help to clear it up.What is AMPERE??
Due to the stupid name it is impossible to Google...
Both?A purely philosophical question then arises: is this a bug or just a very flexible router?
Or repurpose :quit for early termination when used in /system/scriptAny chance we will have :exit really, really soon to fix this? Otherwise I will have a lot of work to do, implementing other (and probably a lot more complicated) workarounds to my scripts.