diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.sgml b/en_US.ISO8859-1/books/handbook/config/chapter.sgml
index 4c5043d674..44934c39c5 100644
--- a/en_US.ISO8859-1/books/handbook/config/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/config/chapter.sgml
@@ -936,17 +936,24 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms
At times, users see a few watchdog timeout
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.
- 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.
+ No route to host
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 netstat
+ -rn and make sure there is a valid route to the host
+ you are trying to reach. If there is not, read on to .
- If you see a ping: sendto: Permission denied
error,
- then its possible your firewall is misconfigured. Read the firewalls
- for more information.
+ ping: sendto: Permission denied
error
+ messages are often caused by a misconfigured firewall. If
+ ipfw 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 for more information.