ER7206: Online Detection marks WAN offline – because of size of ICMP probes
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
- Is the 20-byte probe fixed? Could its size/payload be made configurable, or default to a standard 32/56-byte echo?
- Can DNS-only (or TCP/HTTP) detection be used with the controller, as in standalone Manual mode?
- Is this a known issue, and is a fix planned for ER7206 firmware?
