"not connected", and doing nothing, when using Ethernet

[reusfor]

I try to use my Ragnar on a Raspi 3B+ with wired Ethernet. With WLAN it worked as expected.
But now the web interface shows "not connected". And no scan is donw automatically or can be started manually.

obviously I'm connected :). Pinging the default gateway from the web interface is working, as example.

[PierreGode]

I Will review the pi 3b Ragnar is tested on zero w2 and pi4 and pi5 and can honestly not saw what the difference would be. What OS are running?

[hiSandog]

Connectivity should be derived from the active default route/interface, not the presence or state of a WLAN interface. The scanner can enumerate non-loopback IPv4 interfaces, choose the route used for the gateway, and derive its CIDR for discovery; Ethernet-only systems should then behave identically. Diagnostics should show selected interface/address/subnet and explain when no scannable route exists, with tests for eth0, renamed interfaces, Wi-Fi, and both active together.