Official beta version directly from the gl repository.
4.6.0 open-source.
4 Likes
Is this fixed already on the latest snapshot? @yuxin.zou
By the way, Goodcloud it's working flawless in this beta 
The code to fix it has been merged into the snapshot.
2 Likes
There’s a new beta, I’ll try on MT3000. Currently not for MT6000 though
This version is running very well on my mt6000, no problems apparently so far. only some corrections such as irq-smp-affinity is incorrect, in kernel 6.6 the default is 120 and 121, it is also done in 4.5.8 and also fullcone is not working in the pppoe connection.
Do you have any 4.6.0 owrt24 link for GL-MT3000?
2 Likes
Yes
1 Like
@GL.iNet Staff Try to create an image according to the pesa1234 model: iBF settings & QAM-256 VHT on 2g activable in Luci
iBF settings are for 2g ang 5g network
- WED and irqbalance are enabled
This version seems to run flawlessly on MT6000, however I found this problem: I have a Slate AX connected to Flint 2 in WDS mode and if hardware acceleration is enabled on Flint 2, the devices connected trough cable to Slate AX don't have internet connection. Disabling hardware acceleration (or selecting software acceleration) fix the problem.
1 Like
will there be an update for Tailscan too?
Mostly no. Please update Tailscale using Script: Update Tailscale on (nearly) all devices
1 Like
Thanks, we will check it.
We have analyzed these bugs and are in the process of fixing them.
7 Likes
Is it also possible to implement @oly 's recommendation above?
This new version is running excellent...I compared this build's WiFi to my Vanilla OpenWRT build running the latest OpenSource Mediatek Wifi files (Replaced them from Mediatek Repository) and this version which I assume is running the closed source Mediatek wifi drivers is beating the OpenSource version by a smidge speed-wise...Everything for my setup running great (VPN, Static IPs, etc.)...
Sorry for late reply. Yes let's do this.
1 Like
Please also fix the typo "2g / 5g".
They should be 2.4GHz and 5GHz.
2g and 5g are totally different things.
So,.. "Allow Custom DNS to Override VPN DNS" doesn't work. All WireGuard connected clients cannot access internet, nor anything shows up in AdGuard Logs
(I'm on Flint 1 with 4.6 beta)
Seems like this is not resolved on the latest snapshot, I’ll wait for a new beta
Seems like AdGuard is getting confused,.. VPN'ed clients should be introduced to AdGuard as [VPN- %Client Names%]. If Adguard is shown VPN as something like virtual dual-WAN,.. maybe it can see connections?
[VPN-XYZ] --> [Adguard] --> [VPN-XYZ]
[XYZ] --> [Adguard] --> [XYZ]
...and AdGuard can properly show Names in Logs?? 
[VPN] IP / Custom name set Admin Panel]??