ER7206: Online Detection marks WAN offline – because of size of ICMP probes

ER7206: Online Detection marks WAN offline – because of size of ICMP probes

ER7206: Online Detection marks WAN offline – because of size of ICMP probes
ER7206: Online Detection marks WAN offline – because of size of ICMP probes
2026-10-06 20:04:22 - last edited 2026-10-12 03:34:20
Model: ER7206 (TL-ER7206)  
Hardware Version: V2
Firmware Version: 2.3.6 Build 20260722 Rel.15891

Setup

  • ER7206 v2.0, firmware 2.3.6 Build 20260722 Rel.15891, managed by Omada Controller 6.3.0.451.42.11 Build 20260904 Rel.26567
  • WAN2: 5G modem (public IPv4)
  • WAN3: ISP line connected directly to the gateway, Dynamic IP (ISP uses CGNAT, 100.118.x.x), MAC cloned from the ISP's own router
  • Link Backup enabled: WAN2 primary, WAN3 backup
  • Online Detection Interval: 1 minute

Problem
Omada reports WAN3 as offline ("The online detection result of [WAN3] was offline"), and the Link Connectivity Detection graph shows no latency data for it at all, while WAN2 looks fine. The link itself works: failover to WAN3 works when WAN2 is disabled, and Network Tools pings via WAN3 succeed.

What I found with a packet capture on WAN3

  • The detection probes are a single ICMP echo request (IP packet 48 bytes, ICMP payload 20 bytes, all zeros) and no reply ever arrives.
  • With Echo Server on Custom (1.1.1.1), a probe goes out about every 30 seconds, always unanswered.
  • With Echo Server on Auto, the gateway first resolves four domains via the ISP DNS (replies arrive), then sends one echo request to each resolved address, none answered.

Network Tools ping (gateway, interface chosen)

Interface Packet size Result
WAN/LAN3 32 B 4/4 replies
WAN/LAN3 20 B 0/4 (also tried 8.8.8.8 and the ISP DNS server: all time out)
WAN2 32 B 4/4 replies
WAN2 20 B 4/4 replies

So the small probe is not answered through the ISP, regardless of destination. I can't tell where it is dropped, but the same probe works over WAN2.

Documentation mismatch
The FAQ for Online Detection says a reply to either ping or DNS lookup is enough for the port to show online (https://www.tp-link.com/en/support/faq/2151). In my capture the DNS replies arrive, but the port stays offline, so the controller-managed gateway seems to depend on the ping.

Questions

  1. Is the 20-byte probe fixed? Could its size/payload be made configurable, or default to a standard 32/56-byte echo?
  2. Can DNS-only (or TCP/HTTP) detection be used with the controller, as in standalone Manual mode?
  3. Is this a known issue, and is a fix planned for ER7206 firmware?
  0      
0
#1
Options
1 Accepted Solution
Re:ER7206: Online Detection marks WAN offline – because of size of ICMP probes-Solution
2026-10-10 02:47:20 - last edited 2026-10-12 03:34:20

  @tomen 

Hi,
Thank you for your post on the Business Community.


In Controller mode, Online Detection relies on ICMP responses, and the probe payload size is fixed at 20 bytes. There are some differences between Controller mode and Standalone mode in terms of the detection mechanism.
In Controller mode, the Echo Server can be configured using either an IP address or a domain name. In contrast, Standalone mode supports only custom IP addresses. Additionally, DNS Lookup-based detection is available in Standalone mode, but is not currently supported when the gateway is managed by the Controller.
Regarding the Echo Server behavior:

- When the Echo Server is set to Auto, the gateway first resolves the target domain names and then sends ICMP echo requests to the resolved IP addresses.
- When the Echo Server is set to Custom, if an IP address is specified, the gateway sends ICMP echo requests directly to that address and determines the result based on the ICMP response.

 

As for the issue where WAN3 is reported as Offline, based on the information and packet captures you provided, it appears more likely that the ISP is dropping or filtering these ICMP probe packets. As a result, the Online Detection mechanism is unable to receive the expected ICMP replies and therefore marks WAN3 as Offline, even though the link itself remains operational.

Recommended Solution
  1  
1
#2
Options
3 Reply
Re:ER7206: Online Detection marks WAN offline – because of size of ICMP probes-Solution
2026-10-10 02:47:20 - last edited 2026-10-12 03:34:20

  @tomen 

Hi,
Thank you for your post on the Business Community.


In Controller mode, Online Detection relies on ICMP responses, and the probe payload size is fixed at 20 bytes. There are some differences between Controller mode and Standalone mode in terms of the detection mechanism.
In Controller mode, the Echo Server can be configured using either an IP address or a domain name. In contrast, Standalone mode supports only custom IP addresses. Additionally, DNS Lookup-based detection is available in Standalone mode, but is not currently supported when the gateway is managed by the Controller.
Regarding the Echo Server behavior:

- When the Echo Server is set to Auto, the gateway first resolves the target domain names and then sends ICMP echo requests to the resolved IP addresses.
- When the Echo Server is set to Custom, if an IP address is specified, the gateway sends ICMP echo requests directly to that address and determines the result based on the ICMP response.

 

As for the issue where WAN3 is reported as Offline, based on the information and packet captures you provided, it appears more likely that the ISP is dropping or filtering these ICMP probe packets. As a result, the Online Detection mechanism is unable to receive the expected ICMP replies and therefore marks WAN3 as Offline, even though the link itself remains operational.

Recommended Solution
  1  
1
#2
Options
Re:ER7206: Online Detection marks WAN offline – because of size of ICMP probes
2026-10-10 21:07:48

Hi @Nathan-TP , thank you for the detailed explanation, it matches what we see in the packet captures.

 

I have a few follow-up questions about Online Detection in Controller mode:

1. Is there a plan to make the Online Detection probe configurable (payload size and/or protocol), or to change the fixed 20-byte payload to a more common size (e.g. 32 bytes)? In my case 32-byte echo requests to the same targets pass over WAN3 without loss, only the 20-byte probes are dropped.

2. Is DNS Lookup detection (currently Standalone-only) planned for Controller mode, or another method that does not depend on the ICMP payload size (e.g. a TCP/HTTP probe)?

3. Until then, what do you recommend for Link Backup when the ISP filters the probe? A Custom Echo Server pointing to the gateway's own WAN IP always answers, but it cannot detect a real outage, so failover is effectively unusable.

4. For reference: RFC 792 does not define a minimum or maximum data length for ICMP Echo, so a 20-byte payload (48-byte IP packet) is valid and the ISP-side filtering is a policy decision, not a protocol requirement. It would still help if the documentation stated that the probe size is fixed at 20 bytes and that some ISPs drop such packets.

Environment: ER7206 v2.0, firmware 2.3.6, OC200 controller, WAN3 = Telekom Slovakia with a public IPv4 address.

 

Thanks!

  0  
0
#3
Options
Re:ER7206: Online Detection marks WAN offline – because of size of ICMP probes
2026-10-12 03:34:16

Hi,@tomen 

Thank you for your follow-up questions and for sharing the additional analysis.

 

At this time, there are no plans to modify the current Online Detection design. In Controller mode, the detection mechanism relies on DNS resolution together with ICMP probes that use a fixed payload size, and there are currently no announced plans to make the probe size, payload, or protocol configurable.

 

Regarding your suggestion about the documentation, we appreciate the detailed feedback. We will forward your comments to the relevant team for evaluation.

 

Thank you for your understanding and for taking the time to provide such thorough testing results and observations.

  0  
0
#4
Options