GL-MT6000 Flint 2 (op24) - radio1 (5GHz) fails to wake after night shutdown with wifi up radio1

Description:

I'm running GL.iNet Flint 2 with op24 firmware 4.8.3 (OpenWrt with MTK drivers). I have the following setup:

  • radio0 (2.4GHz): Master mode only
  • radio1 (5GHz): Master mode + Mesh mode

Problem:
Every night, I shut down radio1 using a cron job:

30 23 * * * wifi down radio1
30 5 * * * wifi up radio1

After shutdown, radio1 does NOT return to operation.

Workaround:
I've tried:

  • Using wpad-mesh-openssl (causes mesh to fail)
  • Switching to plain wpad

Question:
Has anyone experienced similar issues with radio wake/sleep on MT7986 with op24? Is there a known fix or better approach to handling nightly radio shutdown/restart?

Any suggestions would be appreciated!

It works for me but I am using wpad-openssl and using Main/snapshot

what is the output from the command line of:

ubus call system board

You're asking the wrong people.


It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

1 Like
ubus call system board
{
	"kernel": "6.6.110",
	"hostname": "GL-MT6000",
	"system": "ARMv8 Processor rev 4",
	"model": "GL.iNet GL-MT6000",
	"board_name": "glinet,gl-mt6000",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "24.10.4",
		"revision": "",
		"target": "mediatek/filogic",
		"description": "OpenWrt 24.10.4 r28959-29397011cc",
		"builddate": "1760891865"
	}
}

Do I need to replace uboot if I want to upload main/snapshot?

Not that I know, I just upgraded from official Openwrt 24.10.4 to main/snapshot and that worked for me

But have a look at: https://openwrt.org/toh/gl.inet/gl-mt6000