Link Down not working
1. Modems connected directly to the ER605; Tigo WAN1, C&W LAN/WAN1
2. ER605 configure as the primary router and computer connected to a secondary router that is configured in bridge mode in order obtain the IP address from main router (ER605)
3. Computer is wired to the router set on bridge as well all personal devices
I have 2 ISP that is connected to the ER605, Whenever i loose internet service from WAN1 (C&W) the Load Balancer shows it online. When i disconnect it manually it will switch to WAN/LAN1 (Tigo) as well for when the network cable remove physically from the Load Balancer. But when the service is down it doesnt detect it offline or down.
i have hotspot connected to WAN/LAN2 but it isnt physically connected at this time. Please disregards it it doesnt make a difference if you remove WAN/LAN2 from WAN Mode
I have the fail over configure to statis it was on automatic same results too
Screenshot 1 "Connected and service Down" shows modem connected... despite not able to retrieve the DNS and unable to retrieve Gateway information - SERVICE IS DOWN (WAN TIGO)
Screenshot 2 "ER605 Status WAN" Status Manually disconnected modem - All details cleared due to modem disconnected and WAN/LAN1 Service is up and running
Screenshot 3 "ER605 Status WAN 1" Status Manually disconnected modem - details shows populated due to service functioning its up and running
I am trying to get backup link to work whenever the internet provider fails to deliver the service and want to make sure my configurations is correct prior to approaching my ISP.
Currently the backup link works when both modems are set on primary, but is inconsistent due to packets being sent to the ISP that is down and i want the load balancer to determine that the WAN is down and to forward these only to WAN/LAN1.
I tried the following configurations:
My Initial config
Some internet packets lost due to sites or games not loading properly or responding
It doesnt switch to the backup link due to the packets arriving to the load balancer. Unless manualy disconnected from the Cloud controller or physicall unplugged which defeats the purpose.