Ongoing, daily WAN down alerts.  Self resolving.  Two SL terminals in bypass mode and both in different buildings feed SFP WAN (copper) and WAN ports of the ER7206 v1.  A few offline events per day are logged.  The log grows daily.  Here is a sample: 

Some homework excertps using CoPilot.....   Do you agree with the conclusion?   

WAN Down coming from one of two places:

1. Starlink’s raw L2/L3 behaviour (micro‑drops, handoffs, ICMP weirdness)

2. ER7206 v1.0’s primitive WAN detection logic

The ER7206 v1.0 WAN detection engine is hard‑coded to:

• Ping a single target

• With a short timeout

• With very few retries

• And declare the WAN offline quickly

So the ER7206 is simply reporting:

• “My probe failed” not “The Starlink terminal is down”

If you want proper WAN detection, only hardware solves it

The following Omada gateways have the new WAN detection engine:

• ER7206 v2

• ER707‑M2

• ER8411

These allow:

• Multiple probe targets

• DNS‑based detection

• Adjustable retries

• Per‑WAN customization

• Much better behaviour with Starlink

If you want stable logs and clean failover, this is the real fix.

OP:  This seems like a less CPU intensive effort to resolve with V1 firmware than other speed related issues that hit processing limits on older hardware.