/tool netwatch
add down-script="/sys reb \r
\ny\r
\n" host=192.168.7.1
The problem is that if ping 192.168.7.1 is available, it will restart after rebooting the device.
Actually, this is not a BUG. The device simply cannot ping the address in the first few seconds after boot.
Also, if a specific solution does not meet your requirement, it’s not a BUG just not applicable to your case.
There is built in watchdog functionality which has several delays built in to overcome the initial (disconnected) state.
https://wiki.mikrotik.com/wiki/Manual:System/Watchdog
The detection is done in two ways:
Software watchdog timer (mostly caused by hardware malfunction) device can recover itself with reboot.
Ping watchdog can monitor connectivity to an specific IP address and trigger reboot function.
The system will reboot in case 6 sequental pings to the given IP address (sent once per 10 seconds) will fail.
Setting: no-ping-delay (time; Default: 5m)
Another way would be to disable netwatch on boot and enable it when the dhcp client is bound, but it’s still possible netwatch-down will be triggered before script on-startup.