Updates to the new troubleshooting section:
* Expand on two of the items with more technical details. * Rewrite a sentence with two typos in it, and remove an extraneous word.
This commit is contained in:
parent
d5993cfd23
commit
f1a254043c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17017
1 changed files with 15 additions and 8 deletions
|
@ -936,17 +936,24 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
|
|||
|
||||
<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
|
||||
a PCI slot which supports Bus Mastering. On some old motherboards, only
|
||||
one PCI slot allows it (usually 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><quote>No route to host</quote> messages occur if the
|
||||
system is unable to route a packet to the destination host.
|
||||
This can happen if no default route is specified, or if a
|
||||
cable is unplugged. Check the output of <command>netstat
|
||||
-rn</command> and make sure there is a valid route to the host
|
||||
you are trying to reach. If there is not, read on to <xref
|
||||
linkend="advanced-networking">.</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>
|
||||
<para><quote>ping: sendto: Permission denied</quote> error
|
||||
messages are often caused by a misconfigured firewall. If
|
||||
<command>ipfw</command> is enabled in the kernel but no rules
|
||||
have been defined, then the default policy is to deny all
|
||||
traffic, even ping requests! Read on to <xref
|
||||
linkend="firewalls"> for more information.</para>
|
||||
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
Loading…
Reference in a new issue