os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add that formal troubleshooting document which my previous commit message

Browse source 
warned about.
This commit is contained in:
Tom Rhodes 2003-05-20 22:37:24 +00:00
parent 1a19d90d60
commit d72c364f8d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17004
1 changed files with 31 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

31
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -821,6 +821,37 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
<secondary>Troubleshooting</secondary>
</indexterm>
<para>Troubleshooting hardware and software configurations is always
a pain, and a pain which can be alleviated by checking the simple
things first. Is your network cable plugged in? Have you properly
configured the network services? Did you configure the firewall
correctly? Is the card you are using supported by FreeBSD? Always
check the hardware notes before sending off a bug report. Update
your version of FreeBSD to the latest STABLE version. Check the
mailing list archives, or perhaps search the Internet.</para>
<para>If the card works, yet performance is poor, it would be worthwhile
to read over the &man.tuning.7; manual page. You can also check the network
configuration as incorrect network settings can cause slow connections.</para>
<para>Some users experience one or two <quote>device timeouts</quote>, which is normal
for some cards. If they continue, or are bothersome, you may wish to be
sure the device is not conflicting with another device. Double check the
cable connections. Perhaps you may just need to get another card.</para>
<para>At times, users see a few <quote>watchdog timeout</quote> errors.
The first thing to do here is to check your network cable. Many cards require
a PCI slot which supports the Bus Mastering. On some old motherboards, only
one PCI slot allows it (most of time slot 0). Check the network card and
the motherboard documentation to determine if that may be the problem.</para>
<para>No route to host messages occur if the network is either not set up
properly, or if the cable is not plugged in. Its rare when this is the
cards fault.</para>
<para>If you see a <quote>ping: sendto: Permission denied</quote> error,
then its possible your firewall is misconfigured. Read the firewalls
<xref linkend="firewalls"> for more information.</para>
</sect3>
</sect2>