I fixed the problem, It reboots every day at 5:00 in the morning using GL.iNet scheduler 
No backups for me 
So will put that on hold and let it run till it breaks.
is there a way I can check if my uboot is still working and not corrupt?
I’m unable to get it to run, plugged one cable in lan1 and powered the router gave my windows 11 pc a static ip to 192.168.1.2.
now I have tried it two ways:
if I power the router I first see a idle blue light, I have tried to press the pin 10 seconds on the flint but that does not work.
then when I waited until the breathing led (blue led breathing), and I then used 10 seconds pin press I do see the router led go black and turn on white for a few seconds, but then it goes back to blue idle light and then back to breathing.
is it me or do I think uboot is hard crashing?
I believe I got a early flint from a year ago.
Early uboot will fail in certain circumstances. Please try to use incognito window of your browser.
1 Like
I figured it out, it seems I had to hold press the pin before powering the device I’m not sure why this was as I cannot remember I did this before 
1 Like
Before going to the trouble of re-flashing uboot.
Any way to determine current version of uboot?
Will new version of uboot cause all config settings to be lost?
That is step #3 
I am having Tshirts made that say : Everbody knows how to Uboot, till they need to Uboot.
I don’t know how many times I have put the Static IP in as 192.168.2.1
2 Likes
The problem isn’t the gl equipment. It’s the ISP router.
I have the same problem. I’m running a MINIMUM of 47 devices at any one time and sometimes as many as 55, and increasing all the time. My ISP router seems to be limited on how many IP addresses it will be able to see, like most modern routers (and any service in the UK) they seem to be limited capacity.
My fibre router will crash roughly once or twice per hour which results in a 5 or 10 minute reboot, in the mean time the entire house grinds to a halt and no lights or switches can be used wirelessly. I have to get up off my a**e and do it myself… In the 21st century! 1st world problems.
My solution was to buy a XIAOMI 5g phone off ebay, because most phones allow unlimited private ip addresses and xiaomi are cheap, a gl.inet router to connect the phone and a mesh system together, fabricobble a network and now I have very few issues with reboots and disconnects.
BUT.
My mesh is meant to be 1200mbps yet I can’t seem to break the 60mbps barrier. The gl router can easily make 300mbps but the mesh behind it can’t. Win some, lose some.
Has been up for 3 days 9 hours at 93% used (363mb) memory with 18% cached (70mb). The only thing I have not done is Run: echo ‘3’ > /proc/sys/vm/drope_caches which I will do soon to see if that makes it happen.
Theory That when cached memory is dropped that what every application is consuming memory (I think its adguardhome) will take too much and crash the router
Do you open admin panel? There are memory leak in nginx which will be fixed in release 3 these two days.
Bug Report
After making a config backup in LuCi, resetting to default and downloading a package (sqm script and luci output so feeds work) can not update distfeeds or packages after reuploading made config backup.
Nothing changed it feeds.
I tested the restore config backup work okay. Do you have more details, like an error report screenshot?
FYI -
update to flint uboot 20220711 using instructions listed above (with firmware beta 4.1)
- All config settings/GUI were retained. Not wiped to default
- never could figure out what version of uboot I was running before updating
a) version not reported on http://192.168.1.1/uboot.html
b) version not reported in luci interface
So - uboot updated without too much trouble
Thanks
The version is at bottom of the uboot upgrade page. http://192.168.1.1 or http://192.168.1.1/uboot.html
uboot2.0 version:22.07.10 is the latest one.
So a fresh system all default settings, the distfeeds and packages update and download with no problem. With wireguard client running, I get errors with updating distfeeds and packages stating no internet check network settings.
Its either trying to search using IPv6, or a firewall rule and or zone needs to be changed.
It can’t use ipv6 because it is not supported by the vpn
If anyone has a good guide on how the firewall/firewall zones works would be appreciated
Not that it makes a huge difference but should input for WAN be reject and I think one of the Masquerading is extra?
Force wget to use ipv4 only maybe a solution. I don’t have an environment to test, you try FYI.
Why not disable ipv6 totally?
1 Like
Both wan and wgclient need masquerading to work.
1 Like
This did not change the situation distfeeds are still blocked for some reason when when wgclient is enabled.
Finally, I found a simpler solution. That’s to delete the ipv6 address of wgclient interface:
uci delete wireguard.peer_831.address_v6
uci commit wireguard
Then redail wg client again.
NVM; I was trying to update the A-1300 