I have a flint 3 for 3 weeks now and today after setting up noip dyndns in luci and rebooting I no longer had internet and it was not possible to log into the router whether through the router IP address I gave it or 192.168.8.1.
I tried disconnecting the power of the router and the modem and waiting a couple a minutes but nothing. I was able to connect to wifi with the ssid I set up but still couldn’t log in, same with a wired connection.
I was forced to reset the router and set everything up again and my question is if this is happens often? That a reboot completely thrashes the system.
To be clear I only had wireguard server running and nothing else. I was on the latest firmware 4.8.4
After the reset I set up noip using the exact same steps as before and it is up and running but now I don’t dare to reboot.
We tested locally using the BE9300 v4.8.4 together with luci-app-ddns, and everything appears to work normally.
After configuring DDNS with NO-IP, the device was still functioning properly after a reboot.
So the issue may not actually be related to DDNS, but instead caused by some other unknown factor.
Based on your description, it seems that the BE9300 SSID can still be discovered and connected to.
Could you please confirm the following:
After connecting, is the device able to obtain an IP address normally?
At that point, if you access 192.168.8.1 (or your configured LAN IP), does the GUI begin loading normally?
However, since you have already reset the router, it may now be difficult to determine the exact cause.
At the moment, aside from cases where incompatible kernel modules were manually installed, we rarely encounter situations where a reboot requires a factory reset in order to regain access.
