Network, troubleshooting - Revision history

Sidetone: /* See also */ link to network wireless

2015-10-21T16:05:58Z

Sidetone: /* etc/ */

2015-01-06T07:19:00Z

etc/

Sidetone: /* rc.conf */

2014-12-22T14:29:36Z

rc.conf

Sidetone: /* Testing network */

2014-12-22T14:25:11Z

Testing network

Sidetone: Merged from Network configuration, troubleshooting

2014-12-22T14:17:43Z

Merged from Network configuration, troubleshooting

Sidetone: moved Troubleshooting connectivity to Network, troubleshooting: going to merge it.

2014-12-22T14:09:05Z

moved Troubleshooting connectivity to Network, troubleshooting: going to merge it.

Dave at 02:40, 15 April 2006

2006-04-15T02:40:55Z

213.83.138.185 at 21:04, 23 September 2005

2005-09-23T21:04:10Z

Dave at 18:48, 22 September 2005

2005-09-22T18:48:53Z

New page

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 216.239.37.99 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.

[[Category : New_User_Tips_and_FAQs ]]

@@ Line 49: / Line 49: @@
 * [[Network Configuration (manual)]]
 * [[Network Configuration (Advanced)]]
 * [[Network Address Translation]]

@@ Line 16: / Line 16: @@
 ==etc/==
-Here are general configurations. Except for a few exceptions, be sure that custom ''[[etc/]]'' settings are located under ''/usr/local/etc/''. /etc configurations can be updated by running processes. This explains why functionality can break, and may have to be updated if only relying on network configuration files in ''/etc'' .
+Here are general configurations for networks settings which reside in /etc.
 ===rc.conf===
-''[[rc.conf]] is an exception and it belongs in ''/etc'' to be customized by the user.
+''[[rc.conf]] belongs in ''/etc'' to be customized by the user.
 Be sure to have the lines:
@@ Line 33: / Line 33: @@
 ===hosts===
-Edit the file at /usr/local/etc/hosts
+Edit the file ''/etc/hosts''
 The commented out line in ''[[hosts]]'' is artificially added here for explanation:
   #gateway ip     localhost     localhost.namedgateway
 .168.x.x     localhost     localhost.yourgatewayname.com
 ===resolv.conf===
-Edit the file /usr/local/etc/[[resolv.conf]] . A line containing "DNS" may have to be commented out from it, depending on your hardware.
+Edit the file /etc/[[resolv.conf]] . A line containing "DNS" may have to be commented out from it, depending on your hardware.
 resolv.conf should look something like this:
   search gateway.yourgateway.com     # search + gateway. and the word name of your gateway ("gateway" is its localhost)
   nameserver 192.168.x.x             # nameserver + numerical ip of gateway
 ==See also==

@@ Line 26: / Line 26: @@
 To check your hostname, you may type at the command line:
-  # uname -a
+  # uname -n
 These are common settings used for a wireless card; [[WPA Supplicant]] is used here:

@@ Line 7: / Line 7: @@
 # 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 216.239.37.99 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).
 ==etc/==

@@ Line 1: / Line 1: @@
-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?
+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? Then here are common configuration file solutions.
 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 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 216.239.37.99 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.
-# ping a known-pingable IP address on the internet. If you can ping 216.239.37.99 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).
-[[Category : New_User_Tips_and_FAQs ]]
+==etc/==