How are you accessing the gui?
Gui and WiFi has been stable for me on all firmwares I've tried including the release candidate.
I've not seen your configuration file problem either.
Via http://192.168.8.1/#/login
The LUCI interface, on the other hand, always works correctly
Sorry it's my bad English 
I meant that I always installed new firmware by deleting existing configurations
Will try and report back.
Just tried. Still i get the same error. Issue persists. Developers should look into it.
Can you disable the DMZ? Not secure and not necessary in for the case.
The Ethernet 2 is used as LAN right?
Seems your computer is trying to be a dhcp server in this case. We have another case which is quest2 VR which does ipv6 dhcp server and confuses the network.
1 Like
Safe to upgrade from 4.5.8 to 4.6.2 and keep the settings, or is it recommended to start fresh?
1 Like
Howdy!
I just updated from 4.5.8 to 4.6.2
Looks like everything is working fine but I encountered a quirk.
I've described it in detail in this post.
Thanks!
Yeah. Seted up DMZ just to make sure nothing else interupted the Flint 2.
Yes indeed, Ethernet 2 is used as LAN.
I just disabled ipv6 from the adapter options in windows. Now lets wait and see.
Thanks for the recommendation!
1 Like
Word of advice, big version jumps and change of kernel it's always better to do a clean install, the router works better 95% of the time that way.... 
3 Likes
Have you tried to disable the 'Flow Control in Device Manager' and 'Energy Efficient Ethernet' for the Marvell?
Tried to no positive effect.
But i think that my problem was fixed when i disabled ipv6 from windows. We wait & see.
Answer from gl-inet regarding OP24 in another thread:
Hi Guys
I have this very strange issue. I have had Flint 2 for almost 8 months now. Came with 4.5.2 firmware installed. Every time I try and upgrade the firmware I have this issue where all the devices on the wifi are kicked off and are not allowed to join the network back, unless I go and reset the router.
After the reset it will work for a while and then it will do the same thing. Last night I upgraded to 4.6.2 hoping that this version will be better and now I have this issue where the router is stuck in this boot cycle and I get this error
4.5.2 version is stable, although it goes down for a few sec every few hours but comes back up automatically (no reboot required).
Any assistance will be appreciated.
WPA3 only devices? That's pretty common. You need to "forget" the Wi-Fi on these devices before rejoining.
The router is going into this endless reboot cycle and I have power it off and then power it back on.
I don't even get the wifi back.
Try upgrading without keeping settings.
That what I did mate.
I factory resettled the router and then installed the 4.6.2 version.
Maybe this router is faulty, as I have not seen anyone with this issue on the forum.
Hmm there are some odd things, which make me wonder how your topology and dhcp stanza has been setup.
Besides wifi devices getting stuck on a already handshaked data and not aknowledge new ones it can also be the dhcp settings.
Can you show a flowchart perhaps how your topology is set with dhcp ranges?
I have not configured the dhcp ranges.
I am not a very advance user, I just use the parental control and VPN Client on this, otherwise everything else on the router is preconfigured.
Should I try turning the DHCP server off?
Alright don't worry 
, we're to help.
Can you do a quick check and see what the wan information is on the home page of the ui?, if the gateway shows also 192.168.8.x then we might have a problem here.
If its not that, i suspect also a other thing and from my own experience it surely can be the issue.
GL-iNet added recently a feature to randomize the mac address from wifi to change the bssid against tracking your ap.
From my experience i have tested this in my own lab environment on OpenWrt 24 which i compile myself without the gl-inet software, and my conclusion was that it breaked half of my iot devices wifi, my suspicion is that the encryption handshake gets derived from the mac/bssid and then causes the same behaviour what misbehaving wifi devices can show by getting stuck on handshake data and not wanting to aknowledge new handshakes only after a reboot or by forgetting wifi network.
Maybe check this off inside the wifi settings, and then reboot router and then also reboot one device which was misbehaving and see if it fix itself.