I agree - I had this need some time ago. Source IP address and Interface. Might be a way to implement a workaround using firewall or mangle rules maybe?
It it possible for NetWatch to utilize the whole fetch API? One of the important things for monitoring is e.g. allowing for HEAD requests. It seems like ROS already has everything in fetch for that but just not in NetWatch
hi Guntis, Please code an extra netwatch "type": BFD. That would use the BFD protocol to monitor a link, and it would provide both the client and server function (UDP port 3784 replies) and have similar parameters as the BFD function in RouterOS v6. That we, we would have a quick-and-dirty workaround for the lack of BFD in RouterOS v7, which apparently takes the routing guys very very long to implement, and I think it should be easy to add as a netwatch type. Then we can run scripts to enable/disable the BGP peer and use this at least until the routing guys get around to it.
@@Andrew_Thrift Because apparently the people working on routing are busy with something else and even though they declared BFD a "work in progress" over a year go, we still have nothing. And this blocks v7 deployment for us. Meanwhile, Guntis seems to be doing work on netwatch and may have time and skills available to include a BFD mode in netwatch, but not to modify the routing software.
Please add a "src-address" field !! This give us option to test a connection via S2S tunnels like IPSec tunnel mode ! If you change the NetWatch then this should be added !
seeing a lot of problems with netwatch.. ive emailed support, and posted on the forums about it.. triggering down scripts when the router itself running a ping at the same time doesnt drop.. 7.11.2.. helpppppp
type icmp, i send 100/100 pings and Status always show "Lost count: 1 , Loss Percent: 10.0%" - bug in ros7.5 ? This means the Thr.LossPercent selector not work when ros stay with constant PL10%. I see that always is a 1 Loss Count... :(
I was using netwatch to send alert on telegram in version 6 but after changing to v7 alert are not send via telegram because in V7 we are not able to ping domain .dns not resolving the address, any solution for this
For some reason it doesnt ping containers made from the router to check if its up or down - even though I can ping the containers from other devices in the same network
Why WinBox not longer change a domains.tld into IP ? Now WinBox show a info "Error in Host - address expected!". Please return the name resolve inside WinBox like before !
@@mikrotik Hopefully in the form of allowing a DNS name to use for the monitor address, and re-resolving it every time the TTL counts down (same as in address lists). So, not a resolve by winbox but a resolve by the router.
So is it possible to use netwatch for wan failover? Like, if i have 2 ISP's, one goes down (not the modem, but the whole line), then it sets the other modem as primary gateway?
@@mikrotik It would be better when you could specify the interface and/or source address to use in the ping, so you can be certain what ISP you are monitoring without having to set an explicit route to some destination via one of the ISPs.
It it possible for NetWatch to utilize the whole fetch API? One of the important things for monitoring is e.g. allowing for HEAD requests. It seems like ROS already has everything in fetch for that but just not in NetWatch
