Yep, I have the same doubts about the possibility of duplication, expressed and discussed here, JFYI:
viewtopic.php?t=215082
but there isn't yet a definite answer/recommendation.
To be fair, SiB is a well known and esteemed member here on Mikrotik forums, so not so random.... some testing done by some random person on another forum.
Try blocking by interface list, instead of by IP:Can you give me an example? I tried to drop packets from 192.168.20.0/24 to 192.168.10.0/24, but without success.
Well, it works from here.Your link for code tags isn't valid anymore...
::local lrttavg ($"rtt-avg" / 100)
:local lrttavg ($"rtt-avg" / 1000)
Well, at $21,500.00, it better puncture preambles, postambles and possibly the space-time continuum: https://www.wavonline.com/Tarana-Wireless-35-0171-001
Hmmm.
And, the rtt-avg of 24516 actually means 24.516ms.
While the one previously posted by rextended, which is much simpler ::foreach i in=[/user-manager session find where active=no] do { /user-manager session remove $i; }
This remove only inactive sessions
/user-manager session remove [find where active=no]
/ip route print
/ip address print
{
:local myhost Pippo
:put $myhost
}
/tool netwatch
:local mystatus [get [find where host=] status]
{
:local myhost $host
:put $myhost
}
:local myhost $host
{
:local myhost $host
:put $myhost
}
Not correct. The issue is not with updating ROS.
Sure, devices used in productive environments should be absolutely reliable.... we can't provide a public administration or government with equipment that doesn't work.
Did you actually check that port UDP 53 is used BOTH by DNS and Wireguard?I have just tried setting my home wireguard client peer to 53 and and nothing happend, not even connection to winbox broke and all works fine.
Just in case, the first two of the twelve rules of the Mikrotik Club are relevantYep, VLAN 0 would be an issue. Also avoid using VLAN 1. Some devices treat VLAN 1 as something special - often with unpredictable results.
Not really, as already explained the L009 is NOT providing PoE out if powered by PoE in, by design.Hi! Based on the description, the problem could be in several places.
Talking of double negations .. I presume there Is an "out" that slipped from your fingers ... (I would try putting It after the "with").
But I would never have figured out with your help ...
So not only device namingInterestingly, 7.13 came out before 7.12.2 did, but 7.13 does not work.
And timeout=1s, OK.interval=10s packet-count=50 packet-interval=380msSeriously, which parameters lead to 19s620ms?
That is rather easy, suggested "down" script contents:The goal for me here, BTW, is to not wake up to a screen full of notifications about down hosts when the ISP does some 1 minute flapping in the middle of the night.
#DO NOTHING
We also have not any idea until you post your configuration, after, maybe.I have no idea whether there is problem in my configuration (entered over cli) or something else in hex..
Ahh, good.Excuse me, I pasted wrong product. I've ordered TL-WPA8631P KIT, this comes with wifi.
https://www.tp-link.com/baltic/home-net ... 8631p-kit/
Which is essentially point #2 in the given:Netwatch leaks out any wan to find a connection and thus you need to blackhole any netwatch routing with a second following route same table distance add one.
You can use mine, only 5c per ping.
/ip route print
and disable the unused services (telnet, etc.)/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=TRUSTED
(taking BTW ether10 out of the bridge for management)./interface list member
add interface=bridge1 list=LAN
add interface=ether10 list=MGM
For MKX, just to be clear, a submarine is NOT a ship!![]()
Connected how?not showing up in winbox neighbours