@desperado 

The only way I could do it was to create an IP Group Profile for a specific computer that I want test with and then set up a Policy Routing to force it out on the specific Wan. 

@desperado Yes, the RT480 had the built in test tools which made testing very easy.

@desperado 

Hey,

On controller, you can check the WAN status under Details. See this image.

If you want to specify some devices to a specific WAN interface, you should configure policy routing.

Hope it helps!

@Somnus 

True, but still, there are times it reports that it is up, but when you do a speedtest, latency and throughput is 0. Need to be able to check where the problem is. Also, is there a way to modify how it tests the link status? How does it determine the status of that particular link? 

On a standalone version, we can specify the link test for it to do a failover, let's say ping a public DNS or ping a particular website from that interface for it to check that the link is really functioning. 

@desperado 

Did you configure link backup feature? The word "failover", as I know, is a mode of link backup. If so, the backup WAN will show online, but it won't transfer any traffic. You cannot configure policy routing and link backup at the same time. They are two conflicting features. Policy routing requires both WAN activated, while link backup will only have primary WAN or backup WAN activated.

Both on controller and in standalone, the router determines the status WAN via online detection, as you said, ping a public DNS or ping a particular website from that interface for it to check that the link is really functioning.

@Somnus 

I've configured my link as failover, in a stand alone mode, when you do a speed test, it would check the speed of both links even if its on a failover. What happened during that time was I'm not getting any readings on my backup wan but omada reports the link as online which is the reason why I wanted to do further investigation why I'm not getting  latency and speed readings on the backup wan. 

on a standalone mode, you do have the capability to do traceroutes and pings from the interface that you want as well as customize the wan link test. 

From what I'm seeing, troubleshooting on an omada controlled router is really limited.

@desperado 

Did you get any readings on the backup WAN before you have this issue? I have some different opinions with you.

From my point of view, failover means primary WAN is linked up, and backup WAN is down in daily use. Only when the primary WAN is down by accident, will the backup WAN be activated and traffic will go to backup WAN till the primary WAN recovers. In this case, if primary WAN works fine, traffic won't go to backup WAN, so it's normal there won't be any readings when you do the speedtest on backup WAN.

On TL-R600VPN and some old models, Status page will show primary WAN as link up and backup WAN as link down, so we can simply judge is the failover mode takes effect or not via the status. However, on omada gateway, like ER605 and ER7206, both WAN's will show link up even if the failover mode works. I have to go to online detection to check the status of backup WAN, or do traceroutes to confirm if my failover is working or not.

In controller mode, you can still do traceroutes and pings from the interface without problem. Have you tried these methods?

The only downside, as I think, is why the router shows both WAN connections as link up even if my failover works fine, which sometimes really makes me confused. Hope TP-Link can change the mechanism back to the same as that of those old models.

@Somnus 

Hi Sommus

"

From my point of view, failover means primary WAN is linked up, and backup WAN is down in daily use. Only when the primary WAN is down by accident, will the backup WAN be activated and traffic will go to backup WAN till the primary WAN recovers. In this case, if primary WAN works fine, traffic won't go to backup WAN, so it's normal there won't be any readings when you do the speedtest on backup WAN."

I've configured my links as failovers and I do get speed test results from both of the interfaces, see screenshots of the stats

I find this useful as this gives me the assurance that both of my links are up and running, 

Here's my WAN config

In controller mode, you can still do traceroutes and pings from the interface without problem. Have you tried these methods?

 -  This is what I'm looking for, I can't find the traceroutes or pings on an Omada controlled router. This is available on the TL-R600VPN stand alone mode configuration.