1 |
vapier 05/08/17 22:42:01 |
2 |
|
3 |
Modified: xml/htdocs/doc/en home-router-howto.xml |
4 |
Log: |
5 |
add a section on troubleshooting dhcpd |
6 |
|
7 |
Revision Changes Path |
8 |
1.31 +31 -4 xml/htdocs/doc/en/home-router-howto.xml |
9 |
|
10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.31&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.31&content-type=text/plain&cvsroot=gentoo |
12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.30&r2=1.31&cvsroot=gentoo |
13 |
|
14 |
Index: home-router-howto.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v |
17 |
retrieving revision 1.30 |
18 |
retrieving revision 1.31 |
19 |
diff -u -r1.30 -r1.31 |
20 |
--- home-router-howto.xml 14 Aug 2005 04:38:48 -0000 1.30 |
21 |
+++ home-router-howto.xml 17 Aug 2005 22:42:01 -0000 1.31 |
22 |
@@ -1,5 +1,5 @@ |
23 |
<?xml version='1.0' encoding='UTF-8'?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.30 2005/08/14 04:38:48 vapier Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.31 2005/08/17 22:42:01 vapier Exp $ --> |
26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<guide link="/doc/en/home-router-howto.xml"> |
29 |
@@ -15,8 +15,8 @@ |
30 |
for connecting your home network to the internet. |
31 |
</abstract> |
32 |
|
33 |
-<version>1.10</version> |
34 |
-<date>2005-08-14</date> |
35 |
+<version>1.11</version> |
36 |
+<date>2005-08-17</date> |
37 |
|
38 |
<chapter> |
39 |
<title>Introduction</title> |
40 |
@@ -332,7 +332,7 @@ |
41 |
watch them work! With Windows systems you should go into the TCP/IP Properties |
42 |
and select the 'Obtain an IP address automatically' and 'Obtain DNS server |
43 |
address automatically' options. Sometimes the changes aren't instantaneous, so |
44 |
-you may have to run a command prompt and run <c>ipconfig /release</c> and |
45 |
+you may have to open a command prompt and run <c>ipconfig /release</c> and |
46 |
<c>ipconfig /renew</c>. But enough about Windows, let's get back to our |
47 |
favorite penguin. |
48 |
</p> |
49 |
@@ -858,6 +858,33 @@ |
50 |
</section> |
51 |
|
52 |
<section> |
53 |
+<title>DHCP Fails To Start</title> |
54 |
+<body> |
55 |
+ |
56 |
+<p> |
57 |
+When starting the dhcp init.d script for the first time, it may fail to load |
58 |
+but neglect to give you any useful info. |
59 |
+</p> |
60 |
+ |
61 |
+<pre caption="DHCP Failing Example"> |
62 |
+# <i>/etc/init.d/dhcp start</i> |
63 |
+ * Setting ownership on dhcp.leases ... [ ok ] |
64 |
+ * Starting dhcpd ... [ !! ] |
65 |
+</pre> |
66 |
+ |
67 |
+<p> |
68 |
+The trick is to know where dhcpd is sending its output. Simply browse to |
69 |
+/var/log and read the log files. Since the exact log file depends on the |
70 |
+package you are using as a syslog, try running <c>grep -Rl dhcpd /var/log</c> |
71 |
+to narrow down the possibilities. Chances are you made a typo in your config |
72 |
+file. You could also try running <c>dhcpd -d -f</c> (short for debug / |
73 |
+foreground) and debug the error based upon the output. |
74 |
+</p> |
75 |
+ |
76 |
+</body> |
77 |
+</section> |
78 |
+ |
79 |
+<section> |
80 |
<title>Incorrect MTU Value</title> |
81 |
<body> |
82 |
|
83 |
|
84 |
|
85 |
|
86 |
-- |
87 |
gentoo-doc-cvs@g.o mailing list |