[JuanVqz]

What

Logging in with Wi-Fi off showed "Something unexpected happened! Check the logs for more info." The log had the real cause:

dial tcp 192.168.0.25:8080: connect: network is unreachable

ClassifyError knew refused connections, timeouts and DNS failures, but not ENETUNREACH, so it fell through to FailureUnknown.

Change

• romm.ErrNetworkUnreachable for ENETUNREACH, classified as the new auth.FailureNetwork.
• Login and startup screens show "No network connection! Please check that Wi-Fi is on and connected."
• EHOSTUNREACH ("no route to host") now counts as a refused connection instead of an unknown error, so it gets the existing "Could not connect to host" message.
• English and Spanish strings. The other locales fall back to English until translated.

Testing

• New romm/errors_classify_test.go builds the dial errors net/http returns (wrapped the way romm/auth.go wraps them) and checks each maps to the right sentinel. A case in TestClassify covers FailureNetwork.
• go test ./..., go vet ./... and go run ./tools/archcheck pass.
• goi18n merge does not list the new keys as missing for es.
• Found on a Miyoo Mini Plus (Onion 4.3.1-1) with Wi-Fi off. I have not run the new build on the device yet.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

The PR gives login and startup a clear message when a connection fails with ENETUNREACH.

• Login and startup explain when the device has no network.

No actionable issues were found. No runtime or device checks were performed.

_{Reviews (1) · Last reviewed commit: "fix(login): tell the user when the devic..." · Reviewed by Greptile}