output above to begin diagnosis
IPv4: gateway · subnet · APIPA · MTU · DNS
IPv6: scope · SLAAC · overlap · link-local GW
Static analysis only · no packets are sent
⚠️ IMPORTANT DISCLAIMER: The tools, scripts, and command references on this site are provided "AS IS" for educational and administrative purposes.
Always review commands before executing them. By using this site, you assume all risk and agree to our Full Terms of Service.
A wrong subnet mask or a gateway outside the subnet is easy to miss in a wall of ipconfig /all output. Paste the output from Windows, Linux, macOS or a Cisco device and RouteLens checks each interface’s addressing, flags problems and gives the commands to fix them.
Usually a missing or wrong default gateway, or a gateway outside your subnet. Check that the gateway shares the network part of your address (for 192.168.1.50/24, a gateway of 192.168.1.1, not 192.168.0.1), that it answers a ping, and that DNS servers are set.
It’s a link-local (APIPA) address that the machine gives itself when DHCP doesn’t answer. Check the cable or Wi-Fi, the DHCP server and the switch port’s VLAN, then renew with ipconfig /renew on Windows or by restarting the connection on Linux.
ip -br addr lists addresses with their prefix length, ip route shows the default gateway, and resolvectl status shows DNS servers on systemd-based systems. ifconfig is deprecated and often not installed.
Too small a subnet (a /25 instead of /24) and the host thinks local neighbours are remote, sending their traffic to the gateway; too large and it tries to reach remote hosts directly and fails. Both show up as some destinations working and others not.
Yes. It reads IPv6 addresses alongside IPv4 and flags common dual-stack problems, such as having only a link-local fe80:: address and no global one.
Related tools: Subnet Calculator · CIDR Calculator · NetBuilder Pro · All tools A–Z