There’s lots of reasons a person might want to go to the Official Open-WRT firmware…
There’s lots of stuff bundled into the GL.Inet firmware as far as the Flint router goes that has nothing to do with the average Home Router user…If GoodCloud and Tailscale and ZeroTier are something the user needs then the GL.Inet firmware has you covered…Some users may decide they want to get rid of that stuff and add things like SQM and QOS as well as other things offered by the Official Open-WRT. When I receive my FLINT2 I’ll decide what I want. Choice and the option to load the Official-WRT is a good thing.
I don’t think you have to choose. There is enough memory in this puppy you don’t need to make room for other packages.
That’s right. I didn’t notice there’s a factory image. MT3000 doesn’t have it for some reason and I thought the situation will be the same for MT6000.
Why switch to vanilla OpenWRT? If you like to tweak some details then you might not be able to permanently change settings that aren’t covered in the official UI because it overwrites whole config files. Also at least on MT3000 network interfaces config doesn’t work with luci. It insists on converting it to a new format but that then can break other stuff.
here they sent the 3 adapters like the mt3000
The router accepts the OpenWrt sysupgrade image, so you could use that to preserve the OEM bootloader.
https://forum.openwrt.org/t/gl-mt6000-up-to-900-mbps-using-wireguard/173524/51
https://forum.openwrt.org/t/gl-mt6000-up-to-900-mbps-using-wireguard/173524/74
https://forum.openwrt.org/t/gl-mt6000-up-to-900-mbps-using-wireguard/173524/76
Yep, here is the summary page - which is a bit easier to read than the forum:
Really, really, really important:
OEM uboot recovery has a Web GUI that will be preserved if OpenWRT is installed using a sysupgrade image.
Installing an OpenWRT factory image will replace the OEM uboot with OpenWRT uboot that does not currently have a GUI web recovery option, only serial/TFTP.
wasn’t trying to be argumentative, was just curious, since it is already running OpenWRT, I configured everything through luci . Didn’t realize that could maybe be a problem.
Since I find tailscale to be a worthwhile feature, I’d have to look and see if there was a package for openWRT that implemented that.
Just curious, but did you end up creating a FedEx account and linking it to a credit/debit card? It’d be good to know if doing that still helps to avoid some additional fees.
Depending on the shipping cost I think I’m looking at £20 - £30 VAT and £4.25 - £12.75 for FedEx’s disbursement fee. Although the disbursement fee might be avoided by setting up a FedEx account, if some websites are to be believed.
It was even stranger.
I received an e-mail 1 day before delivery and was able to pay the amount of 21.xx euros in this e-mail. I did this with my credit card.
The next day I created a FedEx account (because you never know if you’ll need it after all) and also put my credit card on file there. The parcel was delivered, everything was great. On 30.11. a FedEx AutoPay charge was then made to my credit card for 15.xx euros. For the same shipment! 
I wrote to FedEx afterwards and got the 21.xx euros back.
So yes, you can probably avoid the fees with the account.
So after contacting GL iNet support last night through Facebook messenger, I tried to cancel my pre-order and they asked me to wait just a little longer, they asked for proof of the order that took place in the middle of November and then got shipped 9 days later, so I took a pict of it on this thread and sent it, the guy explained it must of just been one that slipped through, he also stated that they had a delay, they expected to ship all pre-order middle to the end of November, but it got delayed until the beginning / middle of December, however, to my surprise, I woke up this morning to an email from GL inet stating the order has been fulfilled and a tracking number has been provided for FedEx shipping, amazing what happens when you threaten to cancel.
Are there any way to export from flint wireguard server config and import into flint2?
Received my flint 2 early bird pre order here in the US - this little machine has so much power the CPU and ram are always sitting on low, nothing tickles it …lol
Yup, just copy your /etc/config/wireguard_server to the new device.
Excited to share with everyone that my Flint2 is starting to the journey with FedEx to Australia. Will keep you posted.
I noticed some people are talking of replacing the GL-inet FW with the OpenWRT one.
What are the pros and cons of that? I realise that it will be clean of many addons GL bundle. I just wonder if there are fixes that are still happening as bugs get ironed out, how do they get pushed up to OpenWRT builds?
Hi all, i’ve registered a fedex account with same email for shipment information. Any chance to pay by website VAT fees? during registration fedex brought 1€ from my card, i don’t know why…
You’ll have to wait until FedEx AutoPay does it’s job.
What about delivery to UK? Which company delivery? FedEx?
Reasons for Switching to Vanilla OpenWrt:
- Trustworthiness:
- Opting for the vanilla OpenWrt operating system provides a transparent understanding of the utilized software. Moreover, it empowers users to create and deploy their custom builds of OpenWrt, incorporating personalized modifications.
- Software Layering:
- GL-iNet SDK operates atop OpenWrt. Customizing configurations outside the GL-iNet SDK may lead to the inadvertent deletion or misinterpretation of custom changes when applying new configurations from the GL-iNet SDK.
- Synchronization Challenges:
- GL-iNet constructs its operating system from an OpenWrt fork, periodically syncing the source code. Given the dynamic nature of GL-iNet’s development, it becomes imperative to ensure the seamless operation of the code on both synced sites. Failure to do so may result in the forking source code falling out of sync, impacting stability and developer support.
- Closed Source Components:
- Certain components within GL-iNet might be proprietary and not open-sourced, limiting the extent to which users can inspect or modify these elements.
Recommendations:
- GL-iNet Original Firmware:
- Suitable for users exclusively working within the GL-iNet SDK environment.
- Offers a stable environment, especially on recent devices with nearly up-to-date packages.
- Vanilla OpenWrt:
- Recommended if:
- You require the latest OpenWrt version and its packages.
- Customization of firmware and software is a priority.
- You possess a discontinued device and necessitate updates.
Considerations:
- Trust: Vanilla OpenWrt relies on the OpenWrt community’s trust, while GL-iNet firmware involves trusting the manufacturer and maintainer.
By carefully assessing your specific needs, you can make an informed decision between the reliability of GL-iNet’s original firmware and the flexibility of vanilla OpenWrt.