Microtik Netwatch config on BSNL FTTH Broadband. Too much Down and Up false alarms

[amohan78]

Hi All

I have used two ISPs, one of them is BSNL FTTH and then made a 2 WAN load balancing on Microtik Hex S. Initially I made a failover configuration with the gateway of 2 ISPs and configured a simple ICMP based Netwatch check on if the ISP is up or down. The Netwatch was configured on the DNS of the ISP and a Microtik Firewall filter rule was set up to ensure that traffic for the DNS of the ISP moved through that ISP only. On the down and up state of Netwatch, I have called scripts that send Telegram messages.

BSNL DNS is 61.1.1.1. When I set a ICMP check on this DNS IP address in Netwatch, I was finding that it would be sending DOWN and UP almost every hour, at least 5 to six times and that downtime would last maximum 40 secs or a minute. It was so much that I disabled the Netwatch based routing script and wrote a recursive routing script on 2 WANs in Microtik.

Then I realized that the Down and Up alerts were false alerts since during those times the recursive routing would not change!

Then I decided to configure netwatch as dns queries on www.google.com rather than ICMP and the result is no better. I have checked with interval, timeout, packet size but nothing has helped.

Has anyone used Netwatch with BSNL FTTH and had this issue ? Could anyone solve this matter ?

 

[flame]

@amohan78 same problem with Airtel broadband bridge mode static IP. having two ISP Jio as WAN2 and Airtel as WAN1 every 40 to 1 hours, sometime 3 hours (10PM to 3AM) no disconnection, day time keep dropping connection only for Airtel. Jio zero Downtime. using Netwatch Script Load balancing(PPC) and Failover simultaneously. Thought Mikrotik problem but no its ISP side problem direct configuring Airtel static IP desktop/laptop connection drops so culprit is Airtel ISP. Check yours BSNL by direct connecting to your available laptop/Desktop for packet PING Loss. Run it for 3 to 4 hours for confirmation...