What's going on

When your GL.iNet Slate AX (GL-AXT1800) connects to local devices over Wi-Fi or Ethernet but fails to pass outbound traffic, the issue is almost always a network handshake mismatch. Because this device functions as a high-performance pocket router within the GL.iNet Travel Routers ecosystem, it often negotiates complex routing layers like repeater modes, captive portals, and active VPN tunnels simultaneously. When one link in that chain drops or misconfigures, outbound internet halts completely.

For broader network setup issues across different hardware, browse our main router troubleshooting hub.

Symptoms people notice

• Local Wi-Fi connects easily, but smartphones and laptops display an alert stating "Connected without Internet".
• Admin Panel is reachable at 192.168.8.1, but status icons under the Internet tab display a persistent spinning wheel or error status.
• Repeater mode connects to hotel Wi-Fi, but web pages redirect to timed-out blank screens instead of the expected login portal.
• Outbound network traffic freezes completely as soon as a WireGuard or OpenVPN client profile is enabled.

Likely causes

1. IP Subnet Overlap: The upstream network uses 192.168.8.x, colliding directly with GL.iNet's factory default LAN address.
2. Unauthenticated MAC Address: Host networks require browser captive portal acceptance, blocking the router's hardware MAC address.
3. Active VPN Kill Switch: A configured VPN profile is toggled on, but can't establish a handshake, locking down all unencrypted WAN traffic.
4. Insufficient USB Power Supply: The Slate AX requires a full 5V/4A (20W) power supply. Standard 5V/2A phone chargers cause hardware instability.
5. Multi-WAN Interface Priority Misconfiguration: Ethernet or USB Tethering is assigned top priority over Repeater mode while disconnected.

Quick checks first

Before diving deep into OpenWrt terminal settings or resetting your hardware, run through these quick diagnostic steps:

• Power Cycle properly: Unplug the power cord for 10 seconds. Ensure you are using the original 5V/4A power supply brick plugged directly into a wall outlet.
• Check Physical Cable Links: If using Ethernet WAN, ensure your modem or source router cable is firmly clipped into the dedicated WAN port (or the reconfigurable 2.5G port if altered in settings).
• Test Direct Connection: Plug a laptop directly into the source modem or test the target host Wi-Fi network without the Slate AX involved to confirm internet service is actually alive.

When it's a real hardware fault

Most networking drops on GL.iNet hardware are software- or configuration-bound. However, physical component failures do happen. If the power LED remains solid red or continuously cycles without boot activity, or if plugging an Ethernet cable into the WAN port produces zero link LEDs on both ends, the internal network transformer or Ethernet port solder joints may be physically damaged.

Similarly, if the router becomes intensely hot to the touch and drops all wireless broadcasts entirely until left off for an hour, thermal degradation of the Qualcomm IPQ6018 SoC may be occurring. In these cases, software resets will not restore stability.

Soft resets vs board/panel work

Always start with soft configuration adjustments within the OpenWrt-based GL.iNet interface. Toggling interface protocols, clearing DNS caches, or updating firmware via the web interface carries zero physical risk. You can perform a clean software reset by holding the physical Reset button on the side of the Slate AX for 10 seconds until the status LED flashes rapidly.

Opening the Slate AX chassis to inspect thermal pads, power delivery caps, or internal Wi-Fi antennas is generally not recommended for standard users. If internal component failure is suspected, board-level micro-soldering is required. For detailed hardware evaluations and reviews of similar networking hardware, check our hardware reviews section.

Next steps

1. Change the Gateway Subnet: Go to Network > LAN and update the IP to 192.168.9.1 to clear subnet conflicts.
2. Clone MAC Address: Match your smartphone's MAC address under Internet > MAC Address to bypass captive portal limits.
3. Update Firmware: Download the latest official GL.iNet firmware build manually and upload it through System > Upgrade to resolve known OpenWrt driver bugs.