Application Optimized Routing keeps forwarding new connections to an offline WAN

Application Optimized Routing keeps forwarding new connections to an offline WAN

Application Optimized Routing keeps forwarding new connections to an offline WAN
Application Optimized Routing keeps forwarding new connections to an offline WAN
2026-08-26 14:30:04 - last edited 2026-08-28 14:14:53
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.3.1 Build 20231207 Rel.61384

Hello,

I found a reproducible issue involving Application Optimized Routing, Policy Routing, and an offline WAN.

Network topology:
- WAN: Online and working normally.
- WAN/LAN1: Physical link remains connected and receives the following configuration:
  - IP address: 192.168.15.2
  - Subnet mask: 255.255.255.0
  - Default gateway: 192.168.15.1
  - DNS: 192.168.15.1
- WAN/LAN1 has no Internet connectivity and is correctly detected by Online Detection as Offline.
- A Policy Routing rule normally forces my notebook through WAN/LAN1.

Problem:
When WAN/LAN1 loses Internet access but its physical link remains connected, the router correctly shows this WAN as Offline. However, with "Enable Application Optimized Routing" enabled, Internet navigation from my notebook stops working correctly.

Disabling the Policy Routing rule does not immediately resolve the issue.

This is not limited to old browser or NAT sessions. New curl processes, each creating a new HTTPS connection, also fail.

Test results while the problem was occurring:
- First test: 3 connection timeouts followed by 2 successful connections.
- Second test: 5 consecutive connection timeouts.
- HTTP/3 also timed out.
- The failures returned curl error 28 after the 5-second connection timeout.
- The failed requests had HTTP code 000 and no remote IP, indicating that the TCP connection was not established.

Example:

curl: (28) Connection timed out after 5002 milliseconds
codigo=000 ip= total=5.002328s

At the same time, a normal traceroute was routed through the healthy WAN:

1  192.168.0.1
2  192.168.1.1
3  186.230.220.89

This suggests that different protocols or new flows were receiving inconsistent routing decisions.

Workarounds:
1. Physically disconnecting WAN/LAN1 immediately restores connectivity.
2. Disabling "Enable Application Optimized Routing" also restores normal connectivity while:
   - WAN/LAN1 remains physically connected;
   - WAN/LAN1 keeps its IP configuration;
   - Online Detection continues to correctly show WAN/LAN1 as Offline.

After disabling Application Optimized Routing, navigation works normally through the healthy WAN.

Expected behavior:
When Online Detection marks a WAN as Offline, all Application Optimized Routing mappings associated with that WAN should be invalidated. New connections should not be forwarded to the offline WAN.

Actual behavior:
Application Optimized Routing appears to retain or create mappings to WAN/LAN1 even though it is correctly detected as Offline. New TCP and UDP connections may continue to be sent through the unavailable WAN.

The official documentation states that load balancing should not take effect on a WAN detected as offline.

A similar issue was previously reported here:
https://community.tp-link.com/en/business/forum/topic/595572

There is a newer firmware version, 1.3.2 Build 20251030, but its release notes only mention security vulnerability fixes and do not mention Application Optimized Routing, Policy Routing, or WAN failover.

Could TP-Link confirm whether this is a known issue and whether firmware 1.3.2 contains any related undocumented fix? I can test a newer or diagnostic firmware if required.

Thank you.

  0      
0
#1
Options