What's going on

When your GL.iNet Flint 2 (GL-MT6000) suddenly stops routing traffic to the internet, it can feel like a total breakdown—especially if your phone and laptop still show a full Wi-Fi signal. Because GL.iNet equips their performance routers with customized OpenWrt software and deep security layers like native WireGuard and AdGuard Home, an internet outage is frequently a software miscommunication rather than physical hardware damage.

Most connection drops stem from a failure in the initial WAN handshake with your service provider modem, an aggressive VPN firewall policy, or a DNS loop. Understanding how to systematically isolate these layers on GL.iNet travel routers and home gateways will save you from unnecessary hardware replacements.

Symptoms people notice

• Connected with No Internet: Wi-Fi icon appears normal on phones and PCs, but browsing throws DNS_PROBE_FINISHED_NO_INTERNET errors.
• Stuck WAN Status: The GL.iNet Admin UI shows the WAN interface spinning on "Connecting..." or hanging at dynamic IP acquisition.
• Ping Works, Browsing Fails: IP addresses (like 1.1.1.1) ping successfully in terminal, but web pages will not load.
• LED Indicators: The central main LED stays solid blue or white, but data traffic ceases completely across both LAN and 5GHz bands.

For broader symptoms across other router hardware, consult our master guide on router network problems.

Likely causes

1. ISP ARP / MAC Lock: Service providers often bind your internet connection to the network card address (MAC) of the first device connected to the modem.
2. VPN Kill-Switch Engagement: If "Block Non-VPN Traffic" is active and the remote server disconnects, all traffic is intentionally dropped.
3. Port Remapping Conflicts: The Flint 2 features dual 2.5Gbps ports; incorrect interface bindings can swap WAN functionality to a LAN port.
4. AdGuard DNS Deadlocks: If AdGuard Home crashes or fails upstream resolution, local devices lose the ability to translate web addresses.
5. Corrupted Leases: The modem and router hold mismatched local gateway addresses following a power flicker.

Quick checks first

Before diving into complex software configurations, run through these high-yield sanity checks:

• Direct Modem Test: Connect a PC directly to the ISP modem via Ethernet cable. If the PC also lacks internet, the outage is on your ISP's end, not the Flint 2.
• Cable Check: Ensure you are using a Cat6 or higher cable running from the modem into the 2.5G WAN port on the back of the GL-MT6000.
• Local Panel Access: Verify you can open http://192.168.8.1 in your browser. If this panel loads, your router's internal system and local Wi-Fi chip are operating normally.

When it's a real hardware fault

While most GL-MT6000 issues are logic- or config-driven, physical failures do occur. If the router fails to power on entirely, if all Ethernet port LEDs remain unlit regardless of connected cables, or if the unit gets abnormally hot to the touch and constantly reboots every few minutes, you may be dealing with a blown power supply power delivery component or corrupted SPI flash memory.

In hardware failure cases, board-level microsoldering or SoC replacement is rarely cost-effective compared to replacing the unit. Check hardware benchmarks and hardware stability ratings in our comprehensive hardware reviews hub.

Soft resets vs board/panel work

If you have locked yourself out of the admin panel or corrupted the Luci advanced interface, avoid physical disassembly. Use the outer button controls first:

1. Soft Reboot: Click 'Reboot' within the GL.iNet web interface or execute a quick power cycle via the toggle switch on the back panel.
2. Hardware Button Reset: While the Flint 2 is powered on, press and hold the side Reset button for 10 seconds until the main LED begins flashing rapidly. Release it to perform a factory reset without opening the casing.
3. U-Boot Recovery: If the router is soft-bricked, GL.iNet provides a built-in U-Boot Web UI accessible via static IP to re-flash stock firmware safely.

Opening the Flint 2 enclosure to access internal serial pins is strictly unnecessary for standard network restoration and should only be attempted by experienced network engineers.

Next steps

1. Cycle power on the ISP modem, wait for online status, then start the Flint 2.
2. Log into 192.168.8.1, check the VPN section, and temporarily disable the kill switch.
3. Use MAC Clone under Network settings if replacing an old ISP gateway.
4. If the problem persists across all devices, perform a 10-second button reset to restore factory OpenWrt configurations.