Wi-Fi Connected But No Internet: The Layer 2 vs Layer 3 Triage Protocol
Quick answer: “Connected, no internet” means the 802.11 Layer 2 association succeeded, but Layer 3 connectivity failed. The usual cause is a missing or invalid default gateway, failed DHCP lease, WAN authentication loss, blocked DNS, or an upstream routing fault. Test the gateway, a public IP, and DNS in that exact order.
Why the OS Reports “Connected”
Operating systems generally report Wi-Fi as connected after the wireless adapter completes association with the access point. At that point, the client and router have established Layer 2 communication, often including WPA2 or WPA3 key exchange.
That status does not prove any of the following:
- The client received a valid IPv4 address from DHCP.
- The client has a usable default gateway.
- The router has a working WAN connection.
- The router can forward packets beyond its LAN interface.
- DNS resolution works.
- NAT is translating private addresses to a public address.
A device can show full Wi-Fi bars, receive an address such as 192.168.1.100, and still have no internet because the router lost its PPPoE session, lacks a WAN VLAN tag, or cannot forward traffic beyond the LAN.
The Correct Triage Order
Do not begin by changing DNS servers or resetting the router. Test each layer in sequence.
| Symptom | OSI Layer | Diagnostic Test and Fix |
|---|---|---|
| No IP address, APIPA address, or missing default gateway | Layer 3, DHCP | Renew the DHCP lease; inspect router DHCP service and LAN subnet |
| Client has an IP but cannot ping the gateway | Layer 2 or Layer 3 | Check Wi-Fi association, ARP entry, client firewall, and router LAN interface |
| Gateway pings, public IP does not | Layer 3, WAN routing | Inspect router WAN status, PPPoE session, static route, and ISP outage |
| Public IP pings, domain lookup fails | Layer 3 transport and DNS | Test DNS directly; replace or correct DNS servers |
| Some sites load, others fail | Layer 3, MTU or DNS | Test MTU path discovery and DNS resolution |
| Multiple devices fail, one device works | Router, WAN, or ISP | Focus on the router and upstream connection, not the failing clients |
| One device fails, others work | Client adapter, driver, proxy, VPN, or local DNS | Renew lease, disable VPN/proxy, inspect adapter settings |
Establish a Known-Good Baseline
Use a wired Ethernet connection when possible. Wi-Fi adds RF interference, roaming behavior, band steering, and driver variables that can obscure the underlying fault.
Before running commands, collect these facts:
| Item | Why It Matters |
|---|---|
| Client IP address | Confirms whether DHCP issued a usable address |
| Subnet mask | Determines the local network boundary |
| Default gateway | Identifies the router the client must use |
| DNS servers | Determines whether name resolution can work |
| Router WAN status | Shows whether the router obtained a public connection |
| ISP connection type | Determines whether PPPoE, DHCP, static IP, or VLAN tagging is required |
DHCP is a client-server protocol that assigns reusable network addresses and delivers configuration parameters, including the information needed for IP operation. The Dynamic Host Configuration Protocol (RFC 2131) defines the lease-based allocation process used by most home and business networks. [29]
Windows Triage
Open Command Prompt as a standard user. Replace 192.168.1.1 with the actual default gateway shown by ipconfig.
ipconfig /all
ipconfig /release
ipconfig /renew
ping 192.168.1.1
ping 1.1.1.1
nslookup routeripguide.com
tracert -d 1.1.1.1
arp -a
Interpret the output in this order:
-
ipconfig /all: Confirm the adapter has an IPv4 address, subnet mask, default gateway, and DNS server. -
ipconfig /releaseandipconfig /renew: Force a new DHCP lease. -
ping 192.168.1.1: Test Layer 2 and Layer 3 reachability to the router. -
ping 1.1.1.1: Test routing beyond the router. -
nslookup routeripguide.com: Test DNS independently of raw IP connectivity. -
tracert -d 1.1.1.1: Identify the first hop where forwarding stops. -
arp -a: Verify that the client resolved the router’s MAC address.
Linux and macOS Triage
On Linux, run:
ip addr show
ip route show
sudo dhclient -v -r
sudo dhclient -v
ping -c 4 192.168.1.1
ping -c 4 1.1.1.1
dig routeripguide.com
traceroute -n 1.1.1.1
ip neigh show
On macOS, run:
ifconfig
netstat -rn
sudo ipconfig set en0 DHCP
ping -c 4 192.168.1.1
ping -c 4 1.1.1.1
dscacheutil -q host -a name routeripguide.com
traceroute -n 1.1.1.1
arp -a
Replace en0 with the active Wi-Fi interface if necessary. Use networksetup -listallhardwareports to identify it.
Failure Mode 1: Carrier PPPoE Authentication Loss
PPPoE is common on DSL and some fiber installations. The router must authenticate with the ISP using a username and password before it can establish a session and receive routing information.
A factory reset, firmware update, ISP password change, or expired account can remove or invalidate those credentials. The result is a router that still serves DHCP and Wi-Fi on the LAN but has no upstream route.
Typical symptoms include:
- Every device shows “Connected, no internet.”
- The router WAN status shows “Connecting,” “Authentication failed,” or no public IP.
- The client can ping the router but not a public IP address.
- Traceroute stops at the first hop.
Fix the WAN configuration before changing client settings. Confirm the connection type, PPPoE username, PPPoE password, and any ISP-required service name. Do not assume the ISP login equals the Wi-Fi password or router administrator password.
Failure Mode 2: Missing 802.1Q WAN VLAN Tag
Some ISPs require a VLAN tag on the WAN interface. IEEE 802.1Q inserts a four-byte tag into the Ethernet frame, allowing one physical link to carry separately identified logical networks.
If the router loses the required VLAN ID after a reset, the WAN port may show a physical link while DHCP discovery or PPPoE discovery receives no response.
| Condition | Expected Result | Actual Result With Missing VLAN |
|---|---|---|
| WAN cable connected | Physical link LED is on | Physical link LED is on |
| Router sends DHCP discovery | ISP responds with an offer | No DHCP offer is received |
| Router sends PPPoE discovery | Access concentrator responds | PPPoE discovery times out |
| Router obtains WAN IP | Router installs a default route | Router has no WAN route |
| Client tests internet | Traffic reaches the ISP | Traffic stops at the router |
If the ISP specifies a VLAN ID, restore it exactly. A VLAN tag is not optional when the provider requires it. Do not add a VLAN tag unless the ISP confirms that one is required.
Failure Mode 3: ARP Cache Collisions and Poisoning
ARP maps an IPv4 address to a MAC address on the local network. If two devices claim the same IP address, ARP replies can alternate between different MAC addresses. The client may reach the gateway intermittently or not at all.
This is common when a static IP is assigned inside the DHCP pool, a forgotten device reuses an address, or a virtual machine bridge shares an IP with the host.
On Windows, clear and rebuild the ARP cache:
arp -d *
ipconfig /release
ipconfig /renew
ping 192.168.1.1
arp -a
On Linux or macOS:
sudo ip neigh flush all
sudo dhclient -r
sudo dhclient
ping -c 4 192.168.1.1
ip neigh show
If the MAC address associated with the gateway changes between pings, investigate duplicate IP assignment. Assign infrastructure devices addresses outside the DHCP range or create DHCP reservations.
Failure Mode 4: Captive Portal DNS Hijacking
Hotel, airport, campus, and some ISP networks intercept DNS queries before full internet access is granted. The network may return a captive-portal IP address for every domain, causing a browser to open a login page while normal applications fail.
This is not always a router fault. The client may be associated to Wi-Fi, receive an address, and have a default gateway, but the upstream network blocks DNS or HTTP traffic until authentication completes.
Test DNS directly:
nslookup routeripguide.com
nslookup routeripguide.com 1.1.1.1
dig routeripguide.com
dig @1.1.1.1 routeripguide.com
If both queries return an unexpected internal address or the same IP address for unrelated domains, a captive portal or DNS interceptor is likely active. Open a plain HTTP page, complete the portal login, then retest.
Why the 30-30-30 Reset Is Harmful
The legacy “30-30-30” reset method is not a universal procedure for modern flash-based routers. Modern devices often use NAND or NOR flash storage, staged bootloaders, and separate configuration partitions.
Holding Reset too briefly may only reboot the router. Holding it too long can interrupt a firmware-related process or place certain models into recovery mode. The correct reset duration is model-specific.
Use this safer sequence:
- Keep the router powered on.
- Locate the recessed Reset button.
- Press and hold it only for the duration stated in the manufacturer manual, commonly around 10 seconds.
- Release when the status LED changes pattern.
- Wait for a complete reboot.
- Reconfigure the WAN connection before changing Wi-Fi or LAN settings.
- Do not remove power during a firmware update or recovery process.
If the router enters a boot loop, use the vendor’s official recovery utility or TFTP procedure only after confirming the exact model and firmware instructions. The directory of default router IP addresses can help identify the correct administration address before recovery.
DNS Is Not Routing
A common mistake is treating DNS failure as proof that the internet is down. DNS and routing are separate services.
| Test | Success Means | Failure Means |
|---|---|---|
ping 192.168.1.1 |
Client can reach the router | LAN, DHCP, Wi-Fi, or client adapter issue |
ping 1.1.1.1 |
Router can forward packets beyond the LAN | WAN authentication, routing, NAT, or ISP issue |
nslookup routeripguide.com |
DNS resolution works | DNS server, DNS forwarding, captive portal, or filtering issue |
If ping 1.1.1.1 succeeds but nslookup routeripguide.com fails, do not reset the router. Inspect DNS settings first.
Final Triage Checklist
- Connect by Ethernet if possible.
- Confirm the client has an IP address, subnet mask, gateway, and DNS server.
- Ping the default gateway.
- Ping a public IP address, such as
1.1.1.1. - Test DNS with
nslookupordig. - Run a traceroute to identify the first failed hop.
- Inspect the router WAN status page.
- Restore PPPoE, static IP, or VLAN settings if the reset removed them.
- Check for duplicate IP addresses and ARP instability.
- Reset the router only after recording the WAN, Wi-Fi, DHCP, DNS, and port-forwarding configuration.
For a practical recovery sequence after a reset, follow the seven-fix walkthrough for Wi-Fi connected with no internet.
This guidance is general and may not match every ISP or router model. Follow the instructions supplied by your internet provider and the documentation for your exact router before resetting or changing WAN settings.
Published by Router IP Guide: Independent Hardware Networking & Gateway Diagnostic Suite.
Top comments (0)