Flint2 with Sonoff DW2 Wifi

Have you tried clearing your browser cache or accessing the page in incognito/private mode? Does the issue still occur?

If refreshing the page, clearing the browser cache, or using incognito mode resolves the issue, then it is likely just an occasional communication issue between the browser and the router’s backend. In that case, seeing this prompt is normal and there is nothing to worry about.

After this changes, the router become unstable. After few hours or days. The router not providing internet and make all clients disconnected. The wifi SSID it seem disappearing and appearing again, but none of client can connect. I not even can connect to the router anymore. And have to off and on again.

I would like to check which firmware version for the Flint 2 supports 802.11b and does not have issues with network storage.

Currently, my Flint 1 is prompting me to update to firmware V4.8.3, but I am concerned that updating may remove support for 802.11b, as all my existing 802.11b devices are connected to Flint 1.

I am unable to test every firmware version, so I would appreciate your recommendation for a stable firmware that:

  • Supports 802.11b
  • Provides reliable network storage performance
  • Does not experience hanging after several hours of use

At the moment, I am using Flint 2 firmware V4.8.5 Beta (2026-03-25). However, I am unsure whether it supports 802.11b, as all my 802.11b devices are still connected to Flint 1.

Thank you in advance for your guidance.

Is there any answer on this matter? Why my Flint 2 after serveral days need to reboot, currently i using your snapshot 3.8.4.

Sorry for the late reply.

As previously mentioned, only the Flint 2 firmware based on OpenWRT 24 currently supports enabling “Allow legacy 802.11b rates.”

We have confirmed locally on the AX1800 v4.8.3 that this option is still available.

Regarding the instability or network storage issues, we recommend trying a factory reset and manually configuring the device instead of importing a backup, then checking if the situation improves.

If the problem persists, please export the logs or continue providing remote access via GoodCloud so we can analyze further.