Does not change my opinion.
It’s not a provided feature, it’s custom-built. So it’s OK if it stops working.
It’s sad, ofc, but not a big deal.
The person could simply use tar combined with gpg.
Damn, did not notice that GL included scripts written by me. Where did you find them?
Yeah, playing dumb fits your attitude. 
Awesome news, I wonder if the hanging 5GHz wireless / degrading speed is fixed with that version. This is the only thing preventing me from using 23.05.
I never had this problem here, the only thing that needs to be fixed is 2.4 which has problems related to mtk/mt76 and not openwrt.
I wasnt able to use the 160mhz on the snapshot for the 5ghz, lots of people were complain it wasnt working, is it working in the final ?
yes, it works at 160mhz
I might give this a try on the MT6000, vanilla OpenWrt works great on my MT3000, I have decided to stay there.
did it change something to 2.4ghz in particular?, I know that the main repo of OpenWrt is different beast than 23.05.3, but I’m at commit 5d34c83, but this bug is still there for me for MT79, I hope they can fix it 
No, you still have the problem related to 2.4
I’ve not seen any reply about my post. …
That returns your public ip 
but the reason is unknown for me, though i do know the public ip is not easy to obtain via OpenWrt system i often observe this with luci-app-ddns theres multiple ways to obtain the public ip, you have ddns active?
yes, I have it active, before I used it with curl activated but it always gave errors, both in gl and in pure openwrt, so I did a test by deactivating curl in both and it stopped showing errors but now this message appears.
user.warn ddns-scripts[10875]: glddns: Get current IP via 'web' failed - retry 1/0 in 60 seconds
this error to be more exact!
Ah, disregard, I think this message always appears every 30 minutes due to the @admon script, everything is fine!
Just my 2 cents: Given GL.inets pricing I had rather higher expectations but really wouldn’t see improvements or bugfixes of OpenWRT / LuCi as GL.inets deliverables.
So best was IMO to report it to LuCi devs.
edit:
GL.inet promises “Flint 2’s proprietary firmware is based on Openwrt [version], designed to give you full control of your network and devices” (emphasis by me) so I do complain when then only do deliver a subset of OpenWrt, but I don’t expect them (in matters of OpenWrt) to deliver any more. Singular exception was in regard to the chosen hardware (still makes me wonder why one would chose a not fully supported hardware!).
Japa182,
Thanks for letting us know…When I saw your post I began working on mine today…
Got my 3 wireguard interfaces, 3 openvpn instances, wifi, and scheduled tasks all working.
Yeah 2.4Ghz is dicey depending on the device. I tested wifi with two different laptops…My old laptop connects on 2.4 and 5Ghz without issue. My new laptop only connects on 5Ghz. Not that it matters as I’m totally wired and only configured it for the learning experience. Everything went pretty smooth today especially when you figure out that OpenWRT installation instructions on the web varies widely. I’m using the Material Theme which I like (Hate Bootstrap but I know traditionalists won’t use anything but that)…Very happy with the performance. Backing up config now…We’ll see if my scheduled reboot works tomorrow morning (It should)…Everything working great. Thanks.
EDIT: Yep my cron job rebooted the router this morning at the exact time…
Hardware acceleration enabled as well as WED (Edited config file for WED)…
The Open-WRT people did a fantastic job with this build. Not their fault that 2.4Ghz is still flawed.
That is a chipset problem (Looking at you Mediatek).
"When you are given lemons...Make lemonade".
I agree to not understand why they chose a good hardware but not well managed
They are not the only producer using that platform:
Personlly I knew that mediatek platform has been sold by Asus ,Xiaomi and BananaPi .
I bought the -flint 2 because it is the cheapest of the all
