MultiPlus‑II GX Ethernet instability / silent connection drops

We have deployed >100 MultiPlus‑II GX systems with Venus OS Large. On 3 units, the Ethernet connectivity periodically drops, making the device unreachable for periods of time. We only observed the issue on the Ethernet connection; after switching to Wi‑Fi, the device worked fine and stayed reachable. During a connection drop, the eth0 network interface was still reported as up.
dmesg shows during boot:

[ 6.120431] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000)
...
[ 11.220824] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 12.186495] dwmac-sun8i 1c30000.ethernet eth0: Too many address, switching to promiscuous

But afterward, there are no subsequent “Link is Down” or “Link is Up” messages when the connection breaks. Also in the other log files I found no related entries. The Ethernet connection recovers after several minutes and then stays stable for 30 seconds to several minutes, until it breaks again.

This behavior persists across Venus OS versions 3.64, 3.67, and 3.71 (no improvement after downgrading or upgrading). I accidentally installed even a non‑Large Venus OS image on one of the affected units, but the issue was still present.

Since the firmware update process continued through the connection drop, I assume that some parts of the network stack still work, even though the Ethernet interface is effectively unusable from the outside.

Is this issue known on MultiPlus‑II GX hardware? Are there any recommended workarounds, firmware updates, or hardware fixes for this kind of silent Ethernet instability?

I’m happy to provide more logs or run specific tests on the affected units.

Thanks in advance!

If you’re using both interfaces, you need to select which is providing internet access. This is a new feature in 3.70+

Thanks for the hint. The problematic devices were running 3.64 and were only connected via Ethernet. I downgraded and upgraded them to see if that would resolve the issue. I also tested the Wi-Fi connection to try and isolate the problem. Unfortunately, nothing has helped so far.

You can try set the ethernet gateway to 0.0.0.0