I will check with RD after the new year holiday. And Happy New Year to you.
Now we are working on the issue of MT6000 and MT3000, So the time may not so fast.
4 Likes
Thanks for doing so & the same to you, Alex… but it’s still another eleven days to New Year’s. 
2 Likes
Sorry for the mistake, and thanks for the addition info about the New Year. I used to think January 1st was New Year’s Day for everyone. 
1 Like
Oh, January 1st is for my side of the hemisphere… not that I’m not envious of a week’s worth of celebration, or anything. Do me a favor: just make sure the food is as good as the festivities. 
1 Like
my guess @bring.fringe18 - is that the delay in moving to to latest version of OpenWrt for Flint 1 / Slate AX is due to the hardware (CPU) support required (both of these use the Qualcomm IPQ6000 that are not currently supported per the OpenWrt hardware search website, whereas Beryl AX and Flint 2 use MediaTek CPUs respectively - which are supported).
Based on a few searches regarding IPQ6000 on latest OpenWrt in the forums - seems that it would take a significant effort to support and likely won’t be supported:
EDIT: there is some progress on AX1800 noted here - but it’s very much in active development still. Primary issue seems to be around the CPU clock(s). There’s links to dev builds in this thread if you’re interested in giving them a run…
Yep - i found that megathread a few hours later… still reading through it… hopefully decent progress has been made.
1 Like
news about a new firmware for the mt3000 and mt6000 with the 2.4ghz correction?
I’m testing 4.5.5 for the MT6000 and everything is working as it should, except 2.4
No, 2.4Ghz issus is under working. We need more time to solve it.
I will upgrade, let’s see how it goes 
I’ve been testing it for hours, I absolutely love it, I can finally use the Samba server, it is slower now but it is way more stable, it was unusable before, too many drops and sometimes I wasn’t even able to transfer a large file, now it works like a charm, it seems hugely optimized, I even did some heavy speed tests on my normal network and on my VPN VLAN while transferring a 20GB file and it didn’t drop or got any error like it used to, tried it several times.
It also has a better range, more transmit power, it used to be 20dbm and now you can set it to 24dbm (on LuCi). It will be set to the maximum power once you upgrade though
Now I wonder if the V4.6 will have the QoS option later, so far a great first impression
1 Like
Qos is not on the function list of V4.6
It will come later I guess, I’d like to see an option to enable USB 2.0 mode so we can avoid the USB 3.0 interference.
This alpha 4.6 version seems to be working well, I’ve been testing
Do you have a list of each feature of the V4.6? I know it’s too early for it though
Very happy to see some progress on this, looking forward to testing.
Has anyone had any issues running the wireguard client under 4.6? I’ve noticed when connected, that traffic won’t flow over the tunnel, unless you’re accessing a resource specifically on that network (e.g. 10.7..). Selecting the “Block all non-VPN traffic” option, causes connectivity to break for clients. The BAX when ssh’d into it still works and has network connectivity just fine with the above settings.
I’ve also noticed that with AdGuard the “AdGuard Home Handle Client Requests” setting is also broken, with all requests showing as 127.0.0.1. @alex_zheng.
Do you use VPN policies?
Block all non-VPN traffic does exactly what the name suggests. It will block all non-VPN traffic, even if you use VPN policies to allow certain devices without VPN - at least that’s my knowledge about this feature.
Do you use Override DNS Settings for All Clients in DNS? In that case, this is intentional.
For letting AdGuard Home handle all client requests, the router does not have to intercept the DNS:
For both, I’ve tried both under 4.4.6 and 4.5, and I’m getting different behaviours here. The DNS one I haven’t had time to look into, but this setting worked fine previously combined with override DNS. The VPN one, both with or without block non-VPN traffic, I get no throughput on the VPN from the clients. Checking my IP etc shows my normal network not the VPN. It is showing as connected and I can see this on the server side too. As mentioned this is multiple configs that worked just fine in previous versions but are now broken.
When will this version release as a beta? So far zero important issues, but I had to restart the router once because the Wi-Fi stopped working for some reason while using SMB without Network Acceleration enabled
I don’t think it’s a good idea, 2.4ghz speeds are slow, just like Flint 2. I think is something related with MT driver on 23.05