What's going on

Few things are more frustrating than having a functional Wi-Fi connection on your laptop, only for a new phone or tablet to be completely rejected when trying to join your GL.iNet network. Because GL.iNet routers run custom software layered over OpenWrt, connection failures for new devices usually boil down to software guardrails: exhausted DHCP pools, aggressive WPA3 encryption defaults, or subnets clashing in Repeater mode.

Understanding whether this is an authentication issue (wrong key/encryption) or an addressing issue (DHCP assignment failure) is the key to getting your new hardware connected quickly.

Symptoms people notice

• Existing connected devices continue working fine, but any new hardware gets kicked off or ignored.
• Phones show status errors such as "IP Configuration Failure", "Saved", or "Obtaining IP Address..."
• Entering the correct Wi-Fi password repeatedly yields an immediate "Incorrect Password" response.
• Connecting works fine on the Guest network, but fails on the primary Wi-Fi network.
• The new device connects briefly, receives no internet access, and drops connection after a few seconds.

Likely causes

1. DHCP Pool Exhaustion: The router's local address assignment pool is full, often caused by short lease times or heavy travel usage.
2. WPA3 / Encryption Mismatches: The access point is configured for WPA3-SAE, which older Wi-Fi cards cannot process.
3. Repeater IP Subnet Conflict: The upstream Wi-Fi network uses the same gateway address (e.g., 192.168.8.1) as your GL.iNet router.
4. MAC Filtering / Client Limits: Security profiles or client quotas in the GL.iNet Admin Panel are preventing new MAC entries.
5. Corrupt Wireless Config: Software glitch in hostapd or LuCI causing new handshake requests to time out.

Quick checks first

Before digging deep into OpenWrt configurations, run through these fast checks:

• Forget the Network: On the new device, tap "Forget Network", toggle Wi-Fi off and back on, and re-enter credentials.
• Check the Admin Panel: Log into 192.168.8.1 and check the client list on the main dashboard. Is the maximum allowed client count reached?
• Test 2.4GHz vs 5GHz: If you are using a single combined SSID, turn off band steering in Wireless settings and test connecting to 2.4GHz separately.
• Toggle Airplane Mode: Quickly reset the client device's network stack by cycling Airplane mode on and off.

For more general router connectivity patterns, check our router troubleshooting guides.

When it's a real hardware fault

Hardware failures causing only new devices to fail are rare, but they do happen. If the Wi-Fi radio module is failing due to thermal degradation or damaged antennas, it may maintain existing active connections while dropping the signal strength required to establish new low-power handshakes.

If your GL.iNet router fails to broadcast Wi-Fi entirely, resets itself continuously, or refuses to assign IP addresses even after a full factory reset, the onboard flash memory or wireless SoC may be degraded. In these cases, consult our device reviews for hardware replacement options.

Soft resets vs board/panel work

Fixing client connection issues on GL.iNet travel and home routers is almost entirely software-based:

• Soft Resets: Rebooting the GL.iNet router via the Admin Panel or pulling the power cord clears temporary DHCP leases and flushes transient firewall state errors.
• Firmware / Overlay Resets: Pressing and holding the physical Reset button for 10 seconds restores factory GL.iNet defaults, clearing bad OpenWrt configurations without opening the chassis.
• Internal Hardware Repairs: Opening small GL.iNet travel routers (like the Slate, Beryl, or Mango series) to repair components isn't cost-effective or recommended due to tiny surface-mount components. Stick to software triage.

Next steps

If clearing DHCP leases and changing Wi-Fi security to WPA2/WPA3 Mixed does not resolve the connection failure, navigate to System > Firmware in the GL.iNet Admin Panel. Perform a clean firmware update (uncheck 'Keep Settings' if persistent bugs remain). If issues persist across all new devices after a complete reset, consider evaluating hardware replacements or upgrading to newer Wi-Fi 6 models.