We have solved this issue, please try to use latest version.
1 Like
What about AX1800 and AXT1800? Not even a snapshot has been released
1 Like
You will use this VPN rule in the next version (v4.8), our developers are working on v4.8, stay tuned!
1 Like
AX1800 and AXT1800 are still in internal testing and their beta versions will be released this month.
1 Like
There is no new version to upgrade to, either via "Upgrade" option in the Beryl AX UI, or from the beta download page...so I don't see a way to test any fix, @Alisa. The version on the download page is the same version that failed. 
1 Like
Hello,
I just see that there is a new op24 4.7.0 beta since yesterday.
Is this thread ok for discussion about this op24 version?
1 Like
Please try downloading the RC version manually and then upgrading the RC version manually, this should solve your problem.
Currently v4.7.0 op24 is available in MT3000 and MT6000, other product model upgrades are still being planned.
4 Likes
Why spending development time on TWO versions of 4.7?
4.7 OpenWRT 21
4.7 OpenWRT 24
Probably worth to focus on OpenWRT 24
In your download website is saying
"...If these issues are resolved in the future, we will revert to the Native OpenWrt version with the open-source driver..."
"...We will continue to address bugs in the open-source version and will make it the main line if it eventually outperforms the closed-source..."
Worth to give more details on the Release Notes.
I agree with this. From what I remembered, GL's development only included closed source drivers from MTK because of some unfixed wireless issues especially with 2.4Ghz as a last resort. However, most recent developments from OpenWRT including their own open-source drivers are now in parity, or even better, than the MTK drivers. That's why I also don't know GL needs to continue developing MTK based firmware if the problems that they're experiencing from last time was already been solved.
5 Likes
OK, done. Things look the same in the FW Upgrade section as they did before, but for now I'll assume the re-do did something. We'll see the next time an updated FW is available.
Just checked 4.7.0-op24 out
i noticed the vpn setup ui is not fully mobile responsive for me, please see:
There are two issues:
- there is no scrollbar this may can cause issues if newer options get added.
- elements are not centered correctly.
The setup itself seem ok, it's only the page of the screenshot.
Device: Poco X6 Pro
1 Like
@gl.iNet staff and moderators:
I think this should be a good idea to split 4.7op24 discussions from this topic because it may be difficult to follow who’s talking about op21 and who’s about op24 
What do you think about that?
I agree but it's impossible to filter like 274 entries.
So I guess the people just need to clearify what they are talking about ...
But for what reason someone would use op21 while 4.7.0-op24 is already available?
Maybe because it’s a beta , where 4.7op21 is RC.
So stability may be the criteria
There is no practical differences between the Beta and Release Candidate, because there are just a few people testing them...
It's just the name...
It's not like a real Beta, RC that we find in Linux, for example, where we have thousands of people testing it on the real life.
Is very difficult to find bugs due to the lack of users testing it.
The real proof of stability is 30~60 days after the firmware is released (on the stable channel), because we will have much more people testing it.
If you like to test something now, go straight to the 4.7.0-op24 and don't waste your time on op21.
Came here to say that NordVPN only shows 20 servers from Seattle (in the US region) and no others.
1 Like
Found that the ARGON Theme could no longer be installed in the LUCI interface in 4.70-op24.
(It worked in 4.66-op24)...Tried multiple times uninstalling then clearing all leftovers with WinSCP...Then reinstalling...ARGON Theme would not work (Did not display and would default back to other theme)...Like I said it worked in 4.66-op24...It also works without issue in Plain Vanilla OpenWRT 24.10...Not a big deal but thought I would point it out.
2 Likes
I've created a separate thread for a better structure.
1 Like