TP-Link load balancer failing over onto backup connection even when primary is intact!
Recently set up the TP-Link ER605 on my home network.
I've hooked up my TP-Link cellular router (TL-MR100 running as a bridge; or rather in an attempt at bridge mode) and my ISP router (ditto) into the load balancer. So far, so good.
Then I configure a very basic backup rule. If WAN1 (ISP) goes down, please move over my connectivity to WAN2 (cellular). Which is basically the entire reason I bought this thing: to manage failover for me. Here's the backup rule. I'm using dual detection on Google DNS servers to check for link status.
All looks to be working until I randomly run a "who's my ISP?" test only to discover that .... the load balancer has moved onto cellular.
I manually disconnect WAN2 and my suspicion is confirmed: WAN1 (ISP) is perfectly fine. There should not have been a failover event.
Essentially the load balancer is failing over onto WAN2 even when WAN1 is perfectly fine and intact. Which is clearly not the anticipated behavior and risks degrading my network performance for no reason. Of note: I had the RT470 before this and experienced the exact same thing.
Anyone else experienced this?
TP-Link are a popular brand and I have a hard time believing that none of their load balancers can handle failover, so perhaps it's something I've misconfigured on the device.