This needs to be the last two filter rules.
As usual, under development.anyway where's the new testing release?
I have never thought about thatSimply open the backup with "notepad"
OK, but what is the answer to my question. You do say that every new change log do show all added stuff since main release. My post clearly that what is sad, does not add up.Please stay on topic. Deleting offtopic now
caps,(?:info|debug).*?: (?<ap>[^:]+): selected channel (?<frequency>\d+)\/(?<widt>\d+)?-?(?<extensionChannel>\w+)\/(?<standard>[^\/]+)\/\S+\((?<dBm>\d+)dBm
:local health [/system health get [find name="psu2-voltage"]]
What's new in 6.34 (2016-Jan-29 10:25):
*) mipsle - architecture support dropped (last fully supported version 6.32.x);
/system logging export verbose
Have already done some years ago, and was told that they will look at it on a later release.@Jotne: open a ticket as it's not a version-specific issue.
Netwatch can also trigger scripts.Hi,
are there events which can be used to trigger scripts other than scheduled triggers?
/ip address print
Or not.It could be today or this week itself.
One of them is me, since I have to rewrite the Splunk Mikrotik logging.Likely the problem is that a complete overhaul of the logging system would make some people (who have invested time in handling the mess as it is) angry...
Are OP logged inn to your router (winbox/web) and have the log window open all time?Sure, but I agree with OP that it doesn't seem very professional with screens full of red warnings that every connection is unsafe.
/ip firewall connection remove [find where dst-address~"your_public_ip_on_interface_xxx"]
/opt/splunk/etc/system/local/inputs.conf
/opt/splunk/bin
./splunk btool inputs list | grep udp
[monitor:///data/syslog/udp/.../*.log]
[udp]
index=*
This is how beta are posted. Look at older beta threads and you will find all beta version in just one thread for each main version.7.3beta40 is available, why is it buried in this thread.
/ip arp print detail
:put [/ip arp get *1]
{
/ppp secret
:foreach id in=[find where profile="Profile-A"] do={
set $id profile="Profile-B"
}
}
When something needs to be run on both versions, don't use syntax compatible only with v7
:local Version [/system/resource get version]
->
:local Version [resource get version]
Did you ask your ISP if they have an NTP server you can use?It is confirmed that the ISP is blocking NTP protocol and they will not do anything to solve it. I have to do it from my side.
Can not be. Missing DHCP/Bridge/interface config +++Is that the full config ?
index=* sourcetype=mikrotik eventtype IN (*tp_connection_from,*tp_user_logged_in,ppp_authentication_failed,l2tp_user_logged_out)
index=* sourcetype=mikrotik ppp
index=*
Does not help if owner of Mikrotik Routers does not bother to read the forum.Put it in the signature part of your user account ;)
Did you read this forum before upgrade?Argh the wiviwave2 package make my hAPAC3 bootloop forever...
Can you give some example on that.all other disadvantages...
:put [/ip cloud get public-address]
:put [/system/resource/get uptime]
5w4d12:38:02
index=*
Since you can not see what's inside HTTPS packages, you can not know if its a web site or DoH traffic. And since any can setup a DoH or DoT server, there are no way you can block this.Not necessarily.
Because DoH server can be blocked, and then fallback to standard DNS.
Not the same, but you can install VmWare and use CHR version of RouterOS.I hope that one day my network interface will work
version 6 works without problems
local cAdd
set cAdd [/ip/cloud/get public-address]
You should not be shocked, since this is just a test version and should not be used in production.but it was a little shocking moment as the PING didn´t came back.....
From my long list of release, there has not been a faster public release (4:25) from 6.47 and up (including beta). Have not looked at releases before 6.47. But I may have missed some...No, there have been fix releases quicker than that...
:put [/ip/cloud/get public-address]
It was just to show that in 7.x series MT has change from posting many beta version of the software to posting many RC version.What is the problem that you are reporting with this specific 7.2rc6 and what does it have to do with 6.4x versions?
Then you should remove 8.8.8.8 DNS settings from 192.168.0.3Because if the source IP is 192.168.0.3, Google should just drop the packet , it can't send traffic back to it.
No, it will only block traffic that has destination IP in the blackhole route.Unless I'm missing something, this will blackhole all internal traffic..
/ip firewall nat reset-counters-all
name~"(?i)fibr"
name~"(\?i)fibr"
This is why you should (if possible) always test on a equal local device before starting on remote device.Nope, the device was upgraded from v6.48.x -> v7.1.3 -> v7.1.5 remotely is the key word here
What's new in 7.1.4 (2022-Mar-21 13:23):
*) ups - fixed UPS support;
I know its only arm yet. Can you post a link to where MT stats that there will be no ZeroTier for other platform?no plans for other architecture atm as per MT