Network, troubleshooting
From FreeBSDwiki
(Difference between revisions)
m (moved Troubleshooting connectivity to Network, troubleshooting: going to merge it.) |
(→See also: link to network wireless) |
||
| (4 intermediate revisions by one user not shown) | |||
| 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. |
| + | |||
| + | ==Testing network== | ||
So, a quick checklist of things: | 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. | # 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 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. |
| − | + | ||
# 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. | # 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). | + | # [[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). |
| + | |||
| + | Examples for steps 1-3: | ||
| + | # ifconfig | ||
| + | # ping 192.168.x.x | ||
| + | # ping cisco.com | ||
| + | # ping 72.163.4.161 | ||
| + | |||
| + | ==etc/== | ||
| + | Here are general configurations for networks settings which reside in /etc. | ||
| + | |||
| + | ===rc.conf=== | ||
| + | ''[[rc.conf]] belongs in ''/etc'' to be customized by the user. | ||
| + | |||
| + | Be sure to have the lines: | ||
| + | defaultrouter="192.168.[your gateway ip address here]" | ||
| + | hostname="[your computer's host name]" | ||
| + | |||
| + | To check your hostname, you may type at the command line: | ||
| + | # uname -n | ||
| + | |||
| + | These are common settings used for a wireless card; [[WPA Supplicant]] is used here: | ||
| + | wlans_ath0="wlan0" | ||
| + | ifconfig_wlan0="WPA DHCP" | ||
| + | |||
| + | ===hosts=== | ||
| + | Edit the file ''/etc/hosts'' | ||
| + | |||
| + | The commented out line in ''[[hosts]]'' is artificially added here for explanation: | ||
| + | #gateway ip localhost localhost.namedgateway | ||
| + | 192.168.x.x localhost localhost.yourgatewayname.com | ||
| + | |||
| + | ===resolv.conf=== | ||
| + | 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== | ||
| + | * [[Network Configuration (basic)]] | ||
| + | * [[Network Configuration (manual)]] | ||
| + | * [[Network Configuration (Advanced)]] | ||
| + | * [[Network, Wireless]] | ||
| + | * [[Network Address Translation]] | ||
| + | |||
| + | ==References== | ||
| + | * Thanks to those who both ask and help answer relevant questions at FreeBSD related forums. | ||
| − | [[Category : New_User_Tips_and_FAQs ]] | + | [[Category:Configuring FreeBSD]] |
| + | [[Category:FreeBSD for Servers]] | ||
| + | [[Category:Important Config Files]] | ||
| + | [[Category:New_User_Tips_and_FAQs]] | ||
Latest revision as of 11:05, 21 October 2015
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.
Contents |
[edit] Testing network
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.
- 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).
Examples for steps 1-3:
# ifconfig # ping 192.168.x.x # ping cisco.com # ping 72.163.4.161
[edit] etc/
Here are general configurations for networks settings which reside in /etc.
[edit] rc.conf
rc.conf belongs in /etc to be customized by the user.
Be sure to have the lines:
defaultrouter="192.168.[your gateway ip address here]" hostname="[your computer's host name]"
To check your hostname, you may type at the command line:
# uname -n
These are common settings used for a wireless card; WPA Supplicant is used here:
wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP"
[edit] hosts
Edit the file /etc/hosts
The commented out line in hosts is artificially added here for explanation:
#gateway ip localhost localhost.namedgateway 192.168.x.x localhost localhost.yourgatewayname.com
[edit] resolv.conf
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
[edit] See also
- Network Configuration (basic)
- Network Configuration (manual)
- Network Configuration (Advanced)
- Network, Wireless
- Network Address Translation
[edit] References
- Thanks to those who both ask and help answer relevant questions at FreeBSD related forums.
