Well, in this case you need second rule that sends ping to blackhole if the ISP has outage.
For example:
add check-gateway=ping comment=“testing ip address” distance=1 dst-address=
ip.ip.ip.ip/32 gateway=gw.gw.gw.gw
add comment=“testip address - blackhole” distance=99 dst-address=
ip.ip.ip.ip/32 type=blackholeThe blackhole rule will be normally not active, as it has high distance, but when the gw is not accessible, the checking route becomes invalid and does not count. In this case there is normal “default” (0.0.0.0/0) route that decides about the way where to send checking ping. It fails for first tryout so netwatch should switch to second default route. Then the testing address becomes accessible by second default route and netwatch can “think” that the first route is on again and switch back to it. So it will be flapping if you are switching default routes back and forth.
If you add blackhole for this specific address you ensure that all packets to testing address will be sent thu first wan (if gw looks responding) or to blackhole. It means - no false positive pings when first wan does not have access to internet.
On the other way there could be false negative decision in case the testing address stops responding even the wan connection to internet is fine. Then you have to change your testing ip… 