What's going on

The GL.iNet Flint 2 (GL-MT6000) is a powerhouse Wi-Fi 6 router running on open-source OpenWrt software paired with a MediaTek Filogic 830 chipset. However, when wireless connections abruptly die mid-call or during gaming, the fault is rarely a complete physical breakdown.

Instead, Wi-Fi dropouts on this specific router usually trace back to software driver conflicts, aggressive hardware network acceleration, or automatic channel switches. Because GL.iNet overlays a custom interface on top of standard OpenWrt, kernel updates and packet steering optimizations can occasionally introduce wireless radio instability.

Symptoms people notice

• The 5GHz SSID vanishes without warning, leaving high-speed devices disconnected while 2.4GHz devices remain online.
• Ethernet-connected PCs stay online, proving the internet service and main CPU are fine while the Wi-Fi subsystem crashes.
• System logs inside the LuCI panel report repeated wireless driver crash logs (mt7986_phy or wed offloading reset errors).
• Wi-Fi cuts out momentarily every time a high-bandwidth task like a multi-gig file transfer or Zoom call begins.
• Dynamic channel changes force devices off the network for up to a minute while radar checks complete.

Likely causes

1. Hardware Acceleration (WED) Conflicts: Packet steering and hardware offloading can overload the Wi-Fi driver under specific traffic types, causing the radios to crash and reset.
2. DFS Channel Radar Interruption: Setting 5GHz channels to 'Auto' often places the router on DFS frequencies, which temporarily disable themselves when detecting radar interference.
3. Firmware Configuration Bloat: Upgrading the GL.iNet firmware while preserving old settings can leave stale overlay scripts that conflict with new radio drivers.
4. Power Supply Instability: A loose power jack or faulty 12V adapter can fail to supply sufficient amperage during heavy transmit bursts, causing localized radio chip resets.
5. Thermal Throttling: Placing the unit in an unventilated cabinet can cause the MediaTek Wi-Fi radios to overheat and reset to protect internal silicon.

Quick checks first

Start with non-destructive, quick fixes before touching advanced settings:

• Check thermal conditions: Feel the chassis. Ensure the side and bottom vents are clear of dust and the device isn't sitting on fabric or inside a closed cabinet.
• Verify the power connection: Unplug the power adapter from both the wall and the router, re-seat it firmly, and avoid using unrated third-party power bricks.
• Disable Band Steering: Separate the 2.4GHz and 5GHz Wi-Fi networks into distinct SSIDs in the Admin Panel to isolate which radio is failing.
• Lock in non-DFS channels: Manually select Channel 36, 40, 44, or 48 for the 5GHz network instead of letting it choose automatically.

For broader diagnostic tips across other network hardware, explore our router problem guide.

When it's a real hardware fault

If you have flashed a clean factory firmware image without preserving settings, verified a stable 12V power supply, and disabled hardware acceleration, yet the Wi-Fi continues to drop every few minutes, you may be facing a hardware-level failure.

Hardware faults on the GL-MT6000 generally involve failure of the onboard MediaTek radio power rails or thermal degradation of the internal power amplifier modules (FEMs). If the system logs report continuous hardware watchdog timeout or phy reset failed errors even on stock firmware, the internal wireless module is physically failing.

Soft resets vs board/panel work

Soft resets, configuration wipes, and setting adjustments through the GL.iNet web GUI or LuCI interface resolve the vast majority of Flint 2 connection issues. Adjusting Wi-Fi channels, disabling network acceleration, or re-flashing official firmware images requires no technical disassembly and poses no risk to the device.

Attempting board-level repairs—such as replacing surface-mount power capacitors or soldering replacement Wi-Fi chips—is not practical or cost-effective for consumer routers. If clean software reinstallation does not resolve physical radio drops, replacing the unit under warranty or consulting hardware reviews for a replacement router is the safest route.

Next steps

1. Access the Admin Panel at 192.168.8.1 and disable Network Acceleration under Network Settings.
2. Assign static, non-DFS channels (Channels 36–48) to the 5GHz radio band.
3. If drops persist, back up critical settings and perform a full Factory Reset under System settings.
4. Download the latest stable GL-MT6000 image from the official GL.iNet portal and perform a clean re-flash.
5. If wireless radios remain offline while wired ports function, check warranty options on the GL.iNet Flint 2 (GL-MT6000) or check out alternative models in the GL.iNet Travel Routers series.