What connected but no internet means on a GL.iNet router
In repeater mode the router joins someone else's Wi-Fi and shares it on its own network. GL.iNet documents a yellow warning for the case where that link is up but useless: The interface is connected, but the Internet can't be accessed. Its first two checks are to confirm the upstream Wi-Fi actually has internet, and to look at the repeater interface status on the Multi-WAN page. [1]
The quickest way to test the upstream network is to join it directly with your phone. If the phone gets a login page, the problem is the portal. If the phone browses freely, the problem is on the router: a subnet clash, a DNS setting or a VPN rule. [1][2]
| Symptom | Check | Fix |
|---|---|---|
| Phone on the venue Wi-Fi sees a login page | Captive portal not accepted | Login mode on, or VPN, AdGuard and rebinding protection off, then accept the portal [2][3] |
| Warning: LAN subnet is in conflict with the WAN subnet | Upstream also uses 192.168.8.x | Change LAN subnet, for example to 192.168.10.1 [4] |
| Sites fail by name but the portal is done | Encrypted DNS, manual DNS or AdGuard Home | Set DNS mode to Automatic; disable AdGuard Home to test [3][6] |
| Nothing loads while VPN shows disconnected | Kill switch is blocking non-VPN traffic | Fix the tunnel, or adjust Block Non-VPN Traffic or All Other Traffic [5] |
| Phone on the venue Wi-Fi also has no internet | Upstream network is down | Ask the venue or switch networks [1] |
Cause 1: the captive portal has not been accepted
Hotel, airport and cafe networks usually hold every device at a login page. GL.iNet's captive portal guide gives three methods. On firmware v4.6 and later, enable Auto-Enable Login Mode for Public Hotspots and Enable Camouflage on the Join Network page; the router then enters login mode when it joins a hotspot without internet access, and camouflage makes it masquerade as the device you use for the admin panel. [2]
GL.iNet's repeater guide notes the trade-off of Login Mode for Public Hotspots: login mode suspends some services and switches DNS to automatic, which may expose your network activity to the hotspot provider. That is acceptable for the minute it takes to log in; turn your protections back on afterwards. [1]
The manual method is to check DNS (rebinding protection disabled, DNS mode Automatic), disable all VPN connections, disable AdGuard Home, then re-enter or refresh the portal page and wait a minute. On a phone, GL.iNet suggests turning Wi-Fi off and on and reconnecting to the router's Wi-Fi. If the venue ties access to a device address, the third method is to clone your phone's MAC address in the repeater settings. [2]
Cause 2: the upstream network uses the same subnet
GL.iNet routers use 192.168.8.x on their own network by default. If the upstream router uses the same LAN range, the two networks clash. GL.iNet's subnet conflict page describes this for a router connected to the GL.iNet WAN port, and the warning LAN subnet is in conflict with the WAN subnet, with a Change LAN Subnet link. [4]
The fix: click the link, change the number after the second dot from 8 to another number, for example 192.168.10.1, and apply. GL.iNet says the page should redirect; if it does not, type the new address and log in again. From then on, the admin panel is at the new address, which is worth noting on the router label. [4]
Worked example: a rental whose main router hands out 192.168.8.x addresses. If the dashboard shows the conflict warning, move the travel router to 192.168.10.1 as GL.iNet describes, log in at the new address, and test browsing again before changing anything else. [4]
Cause 3: DNS settings, encrypted DNS and AdGuard Home
GL.iNet's DNS page lists four modes: Automatic, which uses the DNS server provided by the upstream device; Encrypted DNS (DoT, DoH, DoQ, ODoH or DNSCrypt depending on firmware); Manual DNS; and DNS Proxy. Anything other than Automatic sends lookups somewhere the venue may block until you log in, and some networks block outside DNS servers entirely. [3]
GL.iNet warns that turning on DNS Rebinding Attack Protection may cause private DNS lookup failure, and tells you to disable it on networks with a captive portal. It also documents Override DNS Settings for All Clients and Allow Custom DNS to Override VPN DNS, both of which change where lookups go and are worth switching off while testing. [3]
AdGuard Home on the router acts as the DNS server for every device. GL.iNet's page says that with Handle Client Requests enabled, DNS queries from clients are processed directly by AdGuard Home. GL.iNet's captive portal guide tells you to disable AdGuard Home while logging in. If sites fail by name after the portal is done, disable AdGuard Home briefly; if browsing returns, check its upstream DNS and filter lists. [6][2]
Cause 4: a VPN kill switch is blocking traffic
GL.iNet's kill switch page explains that on firmware v4.7 or earlier, Block Non-VPN Traffic restricts all connected devices from the internet when the VPN is off or disconnected, to prevent DNS leaks. That is the intended behaviour, and it looks exactly like a dead repeater when the tunnel cannot connect. [5]
On firmware v4.8 or later the feature is split. Tunnel Kill Switch is enabled by default once a tunnel is active and is checked under the gear icon next to the tunnel name. Enhanced Kill Switch, in Policy Mode, is controlled by the All Other Traffic section; if you disable All Other Traffic, unmatched traffic is blocked and the internet is only available through the VPN. [5]
The order of work: get the portal accepted with the VPN off, confirm plain browsing works, then turn the VPN on. If the tunnel will not connect on that network, leaving the kill switch on is the safe default, and the practical fallback is phone tethering or another network. [2][5]
Repeater options that help on difficult networks
- Allow Switching to Other Saved Networks: the router can move to another saved network when the current one is unavailable. [1]
- Band Selection: limit scanning and connection to one band if a venue's 2.4 GHz or 5 GHz network is unreliable. [1]
- MAC Mode Factory, Clone or Random: Clone uses a client device's MAC address, useful where the portal ties access to one device. [1][2]
- Lock BSSID: connect only to one access point when several share the same SSID. [1]
- SSID or password errors: remove the network from Known Networks and reconnect. [1]
Checklist before you give up on the network
- Phone joined directly to the venue Wi-Fi: does it get a login page or internet? [1]
- Login mode on (v4.6+), or VPN, AdGuard Home and rebinding protection off, while you accept the portal. [2][3]
- Dashboard shows a subnet conflict? Change the LAN subnet. [4]
- DNS mode set to Automatic for testing. [3]
- VPN tunnel status checked; kill switch understood before you blame the repeater. [5]
- Protections switched back on once browsing works.
Questions before you decide
What does the yellow warning on the repeater mean?
GL.iNet documents the message The interface is connected, but the Internet can't be accessed. It means the router joined the upstream Wi-Fi but cannot reach the internet through it. GL.iNet says to confirm the upstream network has internet access and check the repeater status on the Multi-WAN page.
Should I turn off my VPN to log in to hotel Wi-Fi?
Yes. GL.iNet's captive portal guide says to make sure all VPN connections are disabled under VPN Dashboard, and to disable AdGuard Home, before re-opening the login page. On firmware 4.6 and later, Auto-Enable Login Mode for Public Hotspots suspends some services and switches DNS to automatic when the router detects a hotspot without internet.
Why does the router say LAN subnet is in conflict with the WAN subnet?
GL.iNet says this appears when the upstream router uses the same LAN range as the GL.iNet router. The fix is to change the number after the second dot of the router's LAN address, for example to 192.168.10.1, and log in at the new address.
Can DNS Rebinding Attack Protection break hotel Wi-Fi?
GL.iNet's DNS guide says that if your network has a captive portal you should disable DNS Rebinding Attack Protection, because turning it on may cause private DNS lookup failure.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- GL.iNet Router Docs 4: Repeater Accessed 30 Oct 2026
- GL.iNet Router Docs 4: Connect to a public hotspot with captive portal Accessed 30 Oct 2026
- GL.iNet Router Docs 4: DNS Accessed 30 Oct 2026
- GL.iNet Router Docs 4: How to resolve a subnet conflict Accessed 30 Oct 2026
- GL.iNet Router Docs 4: VPN Kill Switch (Block Non-VPN Traffic) Accessed 30 Oct 2026
- GL.iNet Router Docs 4: AdGuard Home Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.