Good day everyone,

I would like to ask about using Netwatch in a HotSpot interface. I have a RB433 running RouterOS 5.0, one LAN interface connects to Internet, and one WLAN interface, and the other 2 LAN interfaces all together in a Bridge, provides HotSpot service (Ip range: 10.59.0.0/23). Antennas and repeaters are connected to the remaining LAN interfaces, but they are in 192.168.9.0/24 IP range, static addresses.

I have 2 devices in 192.168.9.0 range, IP Addresses are 192.168.9.150, 192.168.9.200, adding both hosts in Netwatch list, they appear down. Searching in forums, I came across those Firewall rules: http://forum.mikrotik.com/viewtopic.php?f=2&t=16670 and http://forum.mikrotik.com/viewtopic.php?f=2&t=18054 Now both devices can ping Mikrotik, but Mikrotik Netwatch still show them as down.

Adding them to IP > Hotspot > IP Bindings both MAC and IP Address of the devices, both bypassed... Still Netwatch shows them as down and Ping from Mikrotik returns timeout. But pinging from 192.168.9.150 to Mikrotik, first ping fails, but second and successive ones gets reply from Mikrotik, and then Netwatch reports 192.168.9.150 host as up.
Same happen to 192.168.9.200. Mikrotik ping fails, Netwatch down. 192.168.9.150 pings 192.168.9.200 or 192.168.9.1, first ping fails, successive ones gets reply. Now Mikrotik can ping 192.168.9.200 and Netwatch reports 192.168.9.200 as up. Looking at log, hotspot debug topic, adds an ARP line everytime Mikrotik detects a ping request on the net; and everything works great. Ping between all 192.168.9.0 network devices, Netwatch works great.
Finally, I set 3 static ARP entries: 192.168.9.1 to Mikrotik's MAC address (Bridge interface), and the 192.168.9.150 and .200 ones. Netwatch working 100%.

Router Reboot: Everything in Netwatch appears down again, until .150 or .200 pings between them, or they try to access 192.168.9.1 Mikrotik's IP address to appear up again... Any ideas of how to solve this behavior and get an up state in Netwatch since reboot?

Thanks in advance, attached a Network map.

Have you tried disabling the 1:1 NAT on the hotspot? That will cause ARP poisoning on the hotspot network.

Code: Select all

/ip hotspot
set 0 address-pool=none

Nope, I didn't. It worked like a charm Thank you very much, I owe you a beer
After another reboot: Instant up state.
Thank you and best regards~!