We're a chatty bunch. Use AI to summarize...or just use the wiki. [OpenWrt Wiki] GL.iNet GL-MT6000
BLASPHEMER!!!!!!
Nothing is perfect, this seems like one of the best wifi 7 options coming though. They said <20W for the Flint 2 and it uses about 10W. The MT7988 is a 6nm chip and likely more efficient than the MT7986 on 12nm. I'd imagine in practice this is a 15W device, unless you're powering USB stuff or using all 3 radios at once.
Not unless eMLMR works, Advanced TWT works, etc. It will just join the club of broken wifi7 gear getting sold at premium prices. That LED screen is there to serve as a nice shiny distraction.
Wi-Fi 7 doesn't really offer any significant advantages. The announced Wi-Fi 8, on the other hand, is all about signal reliability and stability, rather than just gigabits of speed over the air and only a fraction of that over the cable. Simply because Ethernet ports fall short in terms of speed.
My assumption is with the new US FCC laws - Flint 4 will be everywhere except the US for the time being
Who outside the US is willing to buy me one and mail it for a small fee 
Hi folks.
Any ideas why does these errors appearing?
13 Wed Jun 3 19:23:51 2026 daemon err modinfo: cannot find module - mt798x-wmac
On the latest 24th version there were no issues.
Actually, I don't see any issues yet, except these 2 errors.
{
"kernel": "6.12.87",
"hostname": "flfl",
"system": "ARMv8 Processor rev 4",
"model": "GL.iNet GL-MT6000",
"board_name": "glinet,gl-mt6000",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "25.12.4",
"firmware_url": "https://downloads.openwrt.org/",
"revision": "r32933-4ccb782af7",
"target": "mediatek/filogic",
"description": "OpenWrt 25.12.4 r32933-4ccb782af7",
"builddate": "1778712129"
}
}
dmesg | grep mt798
[ 9.161716] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20240823160656a
[ 9.262352] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20240823160721
[ 9.330746] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20240823160840
[ 9.436714] mt798x-wmac 18000000.wifi: registering led 'mt76-phy0'
[ 9.499242] mt798x-wmac 18000000.wifi: registering led 'mt76-phy1'
[ 13.516973] mt798x-wmac 18000000.wifi phy0-ap0: entered allmulticast mode
[ 13.524070] mt798x-wmac 18000000.wifi phy0-ap0: entered promiscuous mode
[ 13.531996] mt798x-wmac 18000000.wifi phy0-ap0: left allmulticast mode
[ 13.538615] mt798x-wmac 18000000.wifi phy0-ap0: left promiscuous mode
[ 13.587980] mt798x-wmac 18000000.wifi phy0-ap0: entered allmulticast mode
[ 13.594982] mt798x-wmac 18000000.wifi phy0-ap0: entered promiscuous mode
[ 14.181799] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
[ 14.188835] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
[ 14.233257] mt798x-wmac 18000000.wifi phy1-ap0: left allmulticast mode
[ 14.239866] mt798x-wmac 18000000.wifi phy1-ap0: left promiscuous mode
[ 14.265752] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
[ 14.272825] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
https://www.gl-inet.com/products/gl-be14000/ NEW Specifications CPU Memory / Storage DDR4 2GB / eMMC 64GB!!!!!
Here's mine. But I haven't paid attention to it, I just turn on WED for wifi and leave it alone it works great.
root@OpenWrt:~# dmesg | grep mt798
[ 7.785122] mt798x-wmac 18000000.wifi: attaching wed device 0 version 2
[ 8.318613] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Time: 20240823160656a
[ 8.419025] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20240823160721
[ 8.487407] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20240823160840
[ 8.593399] mt798x-wmac 18000000.wifi: registering led 'mt76-phy0'
[ 8.649209] mt798x-wmac 18000000.wifi: registering led 'mt76-phy1'
[ 34.827979] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
[ 34.828122] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
same experience here, WED works as expected also if you install bridger (like in Pesa's build) the WLAN to WLAN traffic is also fully offloaded
WED and SQM on wan/pppoe interface is no issue right?
Has anyone done 802.11s mesh with 160 MHz @ 5 GHz between two MT6000 successfully?
I am thinking on buying a 2nd, but not yet decided. I have a Dynalink DL-WRX36 and it is not pairing with HE160 on mesh to this MT6000, only @ HE80
Perhaps you will succeed with HE80, which is quite common in mesh scenarios between different manufacturers/chips, even when running OpenWrt. The chances of success decrease across different drivers and routers
Silly question, but how would Mesh differ from 2 APs sharing SSID and Password? (and Fast Transition enabled).. It already hands off as you move between the APs?
Fast transition generally done when you have Ethernet backhaul between the two routers. Mesh users wireless backhaul. I think probably not as good as fast transition? And maybe more complex. Also I think mesh generally has more than just two APs
No silly questions, except for those you don't ask
It’s 2GB now.