/[gentoo]/xml/htdocs/doc/en/home-router-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/home-router-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.48 Revision 1.49
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.48 2006/08/12 12:18:55 jkt Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.49 2006/08/21 10:21:57 vapier Exp $ -->
4 4
5<guide link="/doc/en/home-router-howto.xml" lang="en"> 5<guide link="/doc/en/home-router-howto.xml" lang="en">
6<title>Home Router Guide</title> 6<title>Home Router Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
102 Interrupt:10 Base address:0x9400 102 Interrupt:10 Base address:0x9400
103</pre> 103</pre>
104 104
105<p> 105<p>
106If you do not see your two cards showing up and you're not sure what kind of 106If you do not see your two cards showing up and you're not sure what kind of
107cards you have, try running <c>lspci | grep Ethernet</c>. You can get that from 107cards you have, try running <c>lspci | grep Ethernet</c>. You can get that
108<c>emerge pciutils</c>. Once you have this information, go into your kernel and 108from <c>emerge pciutils</c>. Once you have this information, go into your
109add support for the correct drivers. 109kernel and add support for the correct drivers.
110</p> 110</p>
111 111
112<p> 112<p>
113The next thing you'll need is support for iptables and NAT (and packet shaping 113The next thing you'll need is support for iptables and NAT (and packet shaping
114if you want). The following list is split up into always required (*), 114if you want). The following list is split up into always required (*),
963 * Setting ownership on dhcp.leases ... [ ok ] 963 * Setting ownership on dhcp.leases ... [ ok ]
964 * Starting dhcpd ... [ !! ] 964 * Starting dhcpd ... [ !! ]
965</pre> 965</pre>
966 966
967<p> 967<p>
968The trick is to know where dhcpd is sending its output. Simply browse to 968The trick is to know where dhcpd is sending its output. Simply browse to
969<path>/var/log</path> and read the log files. Since the exact log file depends 969<path>/var/log</path> and read the log files. Since the exact log file depends
970on the package you are using as a syslog, try running <c>grep -Rl dhcpd 970on the package you are using as a syslog, try running <c>grep -Rl dhcpd
971/var/log</c> to narrow down the possibilities. Chances are you made a typo in 971/var/log</c> to narrow down the possibilities. Chances are you made a typo in
972your config file. You could also try running <c>dhcpd -d -f</c> (short for 972your config file. You could also try running <c>dhcpd -d -f</c> (short for
973debug / foreground) and debug the error based upon the output. 973debug / foreground) and debug the error based upon the output.
974</p> 974</p>
975 975
976</body> 976</body>
977</section> 977</section>

Legend:
Removed from v.1.48  
changed lines
  Added in v.1.49

  ViewVC Help
Powered by ViewVC 1.1.20