Revision as of 21:40, 14 April 2006 by Dave
If you suddenly can't get to the internet, the best thing to do is to find out exactly what's broken first. Makes sense, right? So, a quick checklist of things:
- run ifconfig and see the state of your interfaces; if a cable's come unplugged, you'll see that the interface isn't connected.
- ping your gateway to see if it's your LAN that's down
- ping something on the other side of your gateway (something in another subnet or outside your network, for example).
- ping a known-pingable IP address on the internet. If you can ping 126.96.36.199 but not google.com, then you know something is wrong with your DNS. Other public places that respond to public pings are: cisco.com, yahoo.com, apple.com, google.com and freebsdwiki.net. It might not be a bad idea to write down the IP addresses of one or two of those places for future reference.
- If it's been narrowed down to DNS, find out if it's your DNS or the DNS lookup itself that's causing a problem: try using dig or nslookup to do lookups against another DNS server.
- ifconfig is your friend, unless it's not: if you've misconfigured the IP and netmask, you may not be able to connect to the machine. Remember to log in to the console or you can always connect a crossover cable and give your laptop/desktop that you've hooked up to it the gateway's IP -- this works when you've given your server a 32-bit netmask (255.255.255.255).