OK, so you mean a virtual hop, not a virtual host.
You do not need a virtual hop to fail over among several WANs. The purpose of using a virtual hop is to allow monitoring of availability of a given link using several hosts in the internet, so if at least one of those hosts responds to pings, the link is considered working. Without it, a fault of the single monitored host causes the link to be considered unavailable.
So this has nothing to do with the number of WAN links and with the way you use them (exclusively by priority or distributing the load among them or a mixture of these).
thanks for sharing, if i am using 4 WAN load balance from:
https://aacable.wordpress.com/tag/mikro ... d-balance/
so i just need this to check on my 4 WAN right? please correct me if i am wrong.
add dst-address= 220.127.116.11 gateway = 192.168.1.1 scope = 10
add gateway=18.104.22.168 distance = 1 check-gateway = ping comment="Primary Route"
add dst-address= 22.214.171.124 gateway = 192.168.2.1 scope = 10
add gateway=126.96.36.199 distance = 2 check-gateway = ping comment="Secondry Route"
add dst-address= 188.8.131.52 gateway = 192.168.3.1 scope = 10
add gateway=184.108.40.206 distance = 3 check-gateway = ping comment="Thrid Route"
add dst-address= 220.127.116.11 gateway = 192.168.4.1 scope = 10
add gateway=18.104.22.168 distance = 4 check-gateway = ping comment="Fourth Route"