Flint 2 (GL-MT6000 ) - bug reports - collective thread

Technical Support for Routers
2339

I have a few questions:

The device was announced with Openwrt23 at the time of release, but that is not the case. That was almost a year ago now.

Openwrt is absolutely not up for discussion and I have no interest in it. I bought the GLinet Flint 2 partly because of the easy menu navigation.

Now he's back to Openwrt Snapshot 21 and even in version 4.6.2 the WiFi connection breaks regularly.

If you make updates about Luci - he's currently completely off.

How long should it take until the device runs error-free? ??

2340

You know there is a op24 firmware? GL.iNet download center

2341

It is only a beta version where Wiregurd does not work as an example. It has also been tested extensively

2342

WireGuard works fine on op24. I am using it all day long.

2 Likes
2343

I tested 3 different providers.

Either via Config File or Manually not one of them is started.

2344

Then there must be an issue and you should post your logs and configs.

I can just say that I am using Mullvad all day and it works as fine as always.

4 Likes
2345

Now it's pretty simple.

I take version 4.6.2 Clean Install and test Wireguard. Every provider runs. WiFi just cuts out regularly for unexplained reasons.
I noticed with 4.6.2 that he prefers it when no USB drive is connected and WLAN 2.4 is not set to AX.

If I install version 24 even clean install, Wireguard doesn't start at all.

2346

Please create a new thread about it, posting all logs.

As said before op24 works totally fine for me, even using wg.

3 Likes
2347

Yes, there is a problem with the interferance on the 2.4GHz and GL-iNet reproduced the problem.
I believe this will not be fixed:

2348

You doing something wrong then, because I'm being using wireguard as a client and as a server all day long for over 2 months on "op24"

2 Likes
2349

What can you do wrong with a clean install???

24 Install. Then import one of the 3 different Wireguard Config files and you're done.

If I do this with 4.6.2 in the same procedure, wireguard works immediately.

The difference is only the firmware.

2350

Well not much, but that does not explain to us what other things you have configurated, or how the topology or use of setup is :slight_smile:

Last time i had a discussion with someone about internet cables, he said it were not his cables because someone did it for him, but when i looked to them the cable core was shown outside of the shielding, he thought it was supposed to be like that.

just like that 2 people have a different view on something and not visible if you don't know it, but things like this is still very relevant information :+1:

2 Likes
2351

Maybe try downloading the op24 firmware again, and to really make sure, check the checksum after downloading and flash it through u-boot. I agree with others, op24 works with WireGuard.

1 Like
2352

I have set up a WireGuard client on my Flint 2 (4.6.2) and the server is under a dynamic dns (duckdns domain). Although I have set up the watchdog cron job on my flint, if the server changes an ip address then WireGuard does not reconnect.

Any idea how to fix this?

2353

WireGuard won't reconnect automatically because it does not really know if a connection fails.

So your watchdog should disable VPN, clear DNS cache and enable VPN again.

2354

Hi @admon

I am using the /usr/bin/wireguard_watchdog script, added in /etc/crontabs/root like this:

* * * * * /usr/bin/wireguard_watchdog

But every time the ip changes on the server, it need to manually disconnect and reconnect the client.

2355

I never heard of this script. Where does it come from?

2356

It's part of Wireguard-tools and already installed on Flint 2. Here is the commit message @ openwrt

I have found that for people it worked (topic @glinet forum) but it doesn't seem to do the job for me.

2357

Totally random question: If I load a backup (created using LuCI) into a clean install (without keeping settings), will the result be exactly the same as if I had kept the settings?

2358

Yes and no.
Only config files will be kept, so installed opkg packages will be either reinstalled or missing.