And channel width 140mhz and country has been set?
It can be a issue, i suggest checking this topic for similar issues on 5ghz.
5 ghz is fine, it’s using 160 mhz and on iPerf I get LAN-WLAN speeds near gigabit over 15 feet. I think the issue is somewhere between WLAN and WAN routing and maybe has to do something with using PPPoE.
You could try 4.5.7 which has the mediatek drivers to see if these work better, though you will downgrade to a lower openwrt, but the wifi works alot more stable for me especially on 2.4ghz, for 5ghz i dont saw issues, but wifi is limited on settings you cannot use alot in luci, and the 2.5gb driver may be not present.
But pppoe is a different mix, especially that the pppoe connection also offloads so it can be tasky on the cpu, maybe the fix is to turn off firewall offloading, or hw accerelation or both first?
I hope soon there will be a more stable fw hopefully 23.05 or at minimum the mediatek sdk.
Will we have any feedback from the team about the new versions and the stable version with everything working?
So far no one has said anything and they haven’t said anything else…
5 Likes
Yeah, I was thinking the same, too much radio silent from the @staff something it’s not right 
3 Likes
I wonder the same thing, it’s strange we still don’t have any update regarding all this
They must be quite busy coming up with the next model with the photo frame!!!
Sorry you guys. Our team back to work this week. And we have collected the main issue of MT6000, We invite the MTK people for help, they will be our office these days. We will have some process after that. We are focus on this these days.
11 Likes
Hope to hear good things from that visit 
1 Like
This is great news. Thanks for the update. I wish you guys the best of luck with ironing out all the bugs.
Were you trying to be obtuse in your response? I think you didn’t understand my post. The issue is the CRC error while accessing the firmware environment variables. I explained my need for that information to see if a second-defined partition existed. I didn’t say that not having a second partition was an issue.
Since we’re on the subject now, this router has more flash memory than just about any other router currently shipped. It would be great to see if developers would release a new full firmware with multiple partitions to facilitate dual partition boot. It really wouldn’t be too difficult. I’m sure many in this community would love to use official firmwares alongside with snapshot OpenWRT firmwares or other combinations.
That sounds promising. I do hope that they can fix the 2.4GHz issue within the mt76 driver though, since then we’re not stuck with an old version of OpenWrt with outdated packages.
2 Likes
I upgraded to 4.5.7 , but I lost IPv6 functionality, I can’t get it in either passthrough or native (PD), I sometimes get an IPv6 address in Lan but it’s not routable. Has anyone else seen this issue ?
I’ll play around a bit more but it was working just fine in 4.5.6
Could you describe this detail?
How is it produced?
Im using 4.5.7 (the first one they released using google drive) and my IPv6 works (NAT6)
I had exact same issue, native ipv6 connection.
I can’t get it in either passthrough or native (PD), Couldn’t get an IPv6 address in Lan and syslog sayed: you have delegated ipv6-prefixes but haven’t assigned them to any interface.
I am using the official one off their page (Release 2)
I’ve noticed adguard has also stopped working.
I am getting 4% on Test Ad Block - Toolz (d3ward.github.io) as opposed to 97% before 
I did reset the router and I got adguard to work again, and using the url above up to 97% however IPv6 is still busted
>> nslookup www.google.com
Server: console.gl-inet.com
Address: 192.168.50.1
Non-authoritative answer:
Name: www.google.com
Addresses: 2607:f8b0:400a:80a::2004
142.251.33.100
>> ping -6 2607:f8b0:400a:80a::2004
Pinging 2607:f8b0:400a:80a::2004 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 2607:f8b0:400a:80a::2004:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I updated to the release 2 and my IPv6 still works but again using NAT6 since my modem is a 5G cellular one. When I also try to use Native or Passthrough, it shows IPv6 IPs on the UI but testipv6 fails but I think this is already related to what my modem uses.