New firmware version 4.7 being released for beta testing

A little off topic, but I just realised it's nearly been a year since I upgraded my Flint 2 FW to 4.5.4.... I was one of the early bird buyers. I've been closely watching the developments, especially the WiFi fixes, but got put off when OpenWRT was rolled back to an older version. Hoping the bugs get ironed out of this version soon and then ported / tested on the OP24 build.

My mT3000 has an error that automatically consumes ram over time and the connection to goodcloud is unstable


1 Like

@bruce Thank you!

1 Like

Log
Sat Oct 12 19:17:19 2024 daemon.info gl-cloud[13458]: (gl-cloud:623) fetch ca from: https://gslb-eu.goodcloud.xyz/getCaCert/ca.crt
Sat Oct 12 19:17:20 2024 daemon.info gl-cloud[13458]: (gl-cloud:667) fetch server from: https://gslb-eu.goodcloud.xyz/getTlsBucket
Sat Oct 12 19:17:20 2024 daemon.err gl-cloud[13458]: (gl-cloud:698) fetch server fail:-4 Token Invalid
Sat Oct 12 19:17:20 2024 daemon.err gl-cloud[13458]: (gl-cloud:1002) reconnect mqtt in 5s...

Trying to automatic discover router with Device ID from Goodcloud doesn't works, but in latest Beta (10/11) i manage to discover device entering manually all the info and then router connected without problem/error with Goodcloud.

2 Likes

Not really pratical unless you have a very basic setup.

it's not meant to be practical, it's a beta version. And if someone is already updating, preserving the settings, this should be the first piece of information they provide before asking a question. Many people mess up the configuration, set things up, use the command line via SSH to change the configuration, then update to the new beta version and are surprised that something doesn't work for them. That's what I mean.

1 Like

20 posts were split to a new topic: Improving GL support process - Discussion

For advanced setups, i think a user already is very experienced no?

In that case most configuration is in /etc/config if you make a backup you can cherry pick configs and drag them via scp.

This rarely breaked anything for me :slight_smile:

Often you will learn the walls of potentional files which may break, such as wireless when you change from mtk sdk to op24/openwrt snapshot, and im carefull with the vpn config.

For me the vpn configuration from Mullvad looks a bit outdated since mullvad no longer uses their external dns (it still works though!), but if it breaks i know it might be this change.

1 Like

Dear all, in this post let's talk about firmware v4.7.

For criticizing GL.iNet pls move to other thread. Otherwise we'll just delete your post.

2 Likes

Moved the discussion about GL support processes to Improving GL support process - Discussion

I'm using SurfShark and have the policy set so some devices can bypass the VPN. Problem is they still seem to be trying to use the VPN. Has anyone else noticed the issue?

How did you set the bypass? Based on MAC? Maybe the devices randomize the MAC?

Yes by MAC. None that I have set have the ability to randomize their MAC. When I switch to a MullVad VPN server everything works perfect.

I also reinstalled the latest Beta version and it seems that WireGuardClient does not work on NordVPN, I chose several server countries and it still doesn't show anything after I hit apply!



1 Like

I have the same issue as @oly

But it seems to be a problem that just popped up today. I updated 2 days ago and it worked fine.

Can anyone please come up with a fix ASAP. Wireguard and Nord finally worked and now its gone.

I tried to get a new acess token and I also went ahead and reset the Firmware. Nothing works...

I have the same issue as you. Have you found a solution? I contacted Nord's support team and they said, that they don't support Wireguard setups for routers. Have they maybe blocked Gl.inet from doing so?

We're working on it now, you can try downloading and upgrading to the latest firmware version.

It is the problem of Nord. Their API returns different format. We will fix with firmware update.

image
<...> Does it mean wired cable?
5g - Does it mean WiFi?
I updated 4.7 and my clients list all mixes and wrong.
For example, my Meta Portal device is WiFi but shows icon <..>
image
something not right numbers clients

4.7 beta (MT6000) missing for me, as new 4.6.8 RC is now listed.
Is there a better or alternate source?