LOL, you're normally the one with IPv6 answers...Lack of responses makes me uneasyDoes no one have both GUA and ULA on the same link?
I filed a report about the docs. MT fixed the description of the thr- params...but yeah they forgot the ICMP probe stats (which have been wrong for a while). It's still open.Curiosity of the day:
The netwatch help page has been changed/edited yesterday,
Using WInBox4, the DHCP client "check-gateway" option is a static control, but should be drop-down.*) dhcpv4/v6-client - added check-gateway parameter;
You need to get them from MikroTik as they cannot be posted publicly. Email support at support@mikrotik.com for the files, which will have the instructions since it rather complex operation.Please share the R11e-LTE-US files so I can install them on my LTE module.
interval=10s packet-count=50 packet-interval=380msSeriously, which parameters lead to 19s620ms?
My point was it's not clear and there is more subtlety here... Might be the DHCP client polling? Now whether that's a connection in this terminology, IDK.No smartypants, connections have the connection flag, this one doesn't.
All roads lead to improving docs, and perhaps more "wizards" in UI or at least docs with complete examples to avoid needing AI (or at LLMs)...Still it needs to learn by actual good examples which for rsc there are not much available as for other languages which can mislead AI.
why not be accurate and fix the RN?You can choose to understand what they meant to say or you can choose to get lost in translation.
The issue is RN says "connections", not "listeners"... There is a difference.In IP/Services.
@Amm0 already explained to look at sniffers, or lab a smaller example. But ZeroTier "L2" should be transparent to "L3" [multicast] OSPF.Maybe @Amm0 can help you out here.
100%Since MT already uses Confluence/Jira, they can just publish a link
Agreed. I'm surprised this has not happened more. But ideally the forum should block the *.rif from being uploaded.Remove supout, is only for support@mikrotik.com and not for be shared on user forum because can contain sensitive data.
Please keep this forum topic strictly related to this particular RouterOS release.
We have relatives there, and taking my mom to visit this summer. They wanted me to "fix their wi-fi" while visiting & thinking how to outsourceCurious why you asked...
Fixed for me. Thanks.*) fix RoMON connect (introduced in v4.0beta19)
That sounds like good news!Very close to final version.
Any updates?
"Sir, I see some movement on the enemy's trench."
/system/history/print detail
Well when the release mgmt discussions start to overwhelming the "testing" thread... the "process" is that beta becomes a rc ;).this will be for sure going in circles for eternity
/routing/nexthop print
/routing/routes print
So what is the summary on why RoMON does not work here? I lost track of the conversation.Well based on the avatar, I guess that post could be considered a dud!)
Fixed. I swear I'd seen that cause not RoMON work in past. But re-tested it, you're right.My post intentionally refers to @Ammo's one in particular, just for the case that someone comes searching and gets mislead by it. But unless @Ammo edits his, few people will probably notice mine.
Sure, but that's what HAProxy is for...Normis said the problem is the forum software doesn't support HA and/or distributing the site between several servers. Do with this info what You will.
Is there any way you can publish a ZIP of the forum content when you migrate it? I still think it interesting try the forum content in some small language model.posts will be migrated
While :nothing is nothing... [:nothing] is nil:Is not clear at all on post #2: not mix nil and nothing, because nothing is also different from nothing.
:put [:typeof [:nothing]]
nil
:put ([:typeof [:find "asd" "p" -1]]="nil")
:put ([:find "asd" "p" -1] = [:nothing])
Maybe if it multiple lines you need a {} code block, since the [] is not a codeblockBut alas.
/ip/arp/find [{
:put $address
:put $interface
}]
* assuming you're not in North America+1 for ATL LTE18.
That make sense, given they've long implemented the now ratified RFC-9759It might actually happen sooner than you'd expect. Word is Mikrotik has recently brought on about 15 people, supposedly working full-time on developing business-oriented features.
no plan to make it avoidable while still keeping the device up to date. This is my main complaint.
True in part. But there is no context menu (right-click) with "Copy", and in WinBox4 the "copy" being in the title bar (i.e. stacked paper icon is copy) may not be obvious to all...Not sure why you think it is missing.
Maybe. No point arguing here. Open a new ticket with the exact problem you're see... since, yes, sometime it does take a few rounds in a ticket to convince them. But they do fix something if there is clear repo case in a ticket.As was said, it's a RouterOS bug.