[gentoo-doc-cvs] cvs commit: home-router-howto.xml

public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-08-04  0:18 Mike Frysinger
  0 siblings, 0 replies; 32+ messages in thread
From: Mike Frysinger @ 2005-08-04  0:18 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/08/04 00:18:21

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  add a quick & dirty howto for setting up a local rsync server

Revision  Changes    Path
1.29      +57 -3     xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.29&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.29&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.28&r2=1.29&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- home-router-howto.xml	2 Jul 2005 09:59:11 -0000	1.28
+++ home-router-howto.xml	4 Aug 2005 00:18:20 -0000	1.29
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.28 2005/07/02 09:59:11 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.29 2005/08/04 00:18:20 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.8</version>
-<date>2005-07-02</date>
+<version>1.9</version>
+<date>2005-08-03</date>
 
 <chapter>
 <title>Introduction</title>
@@ -689,6 +689,60 @@
 </section>
 
 <section>
+<title>Rsync Server</title>
+<body>
+
+<p>
+For those who run multiple Gentoo boxes on the same lan, you often want to 
+keep from having every machine running <c>emerge sync</c> with remote 
+servers.  By setting up a local rsync, you save on both your bandwidth and 
+the Gentoo rsync servers' bandwidth.  It's pretty simple to do.
+</p>
+<note>
+For a much more in-depth rsync guide, please see the official <uri 
+link="/doc/en/rsync.xml#doc_chap4">rsync guide</uri>
+</note>
+
+<p>
+Since every Gentoo machine requires rsync, theres no need to emerge it.  Edit 
+the default <path>/etc/rsyncd.conf</path> config file, uncomment the 
+<c>[gentoo-portage]</c> section, and make sure you add an <c>address</c> 
+option.  All the other defaults should be fine.
+</p>
+
+<pre caption="Rsync server config">
+pid file = /var/run/rsyncd.pid
+use chroot = yes
+read only = yes
+address = 192.168.0.1
+
+[gentoo-portage]
+	path = /mnt/space/portage
+	comment = Gentoo Linux Portage tree
+	exclude = /distfiles /packages
+</pre>
+
+<p>
+Then you need to start the service (again, the defaults are OK).
+</p>
+
+<pre caption="Starting the rsync server">
+# <i>/etc/init.d/rsyncd start</i>
+# <i>rc-update add rsyncd default</i>
+</pre>
+
+<p>
+Only thing left is to set tell your clients to sync against the router.
+</p>
+
+<pre caption="Client SYNC settings in make.conf">
+SYNC="rsync://192.168.0.1/gentoo-portage"
+</pre>
+
+</body>
+</section>
+
+<section>
 <title>Mail Server</title>
 <body>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-08-14  4:38 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-08-14  4:38 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/08/14 04:38:49

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  replace eth0 with $LAN and eth1 with $WAN and rename Debugging section to Troubleshooting #102450 by Arnold Miller

Revision  Changes    Path
1.30      +35 -27    xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.30&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.30&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.29&r2=1.30&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- home-router-howto.xml	4 Aug 2005 00:18:20 -0000	1.29
+++ home-router-howto.xml	14 Aug 2005 04:38:48 -0000	1.30
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.29 2005/08/04 00:18:20 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.30 2005/08/14 04:38:48 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.9</version>
-<date>2005-08-03</date>
+<version>1.10</version>
+<date>2005-08-14</date>
 
 <chapter>
 <title>Introduction</title>
@@ -206,7 +206,7 @@
 # <i>nano /etc/conf.d/net</i>
 <comment>Add an entry for config_eth1 and set it to adsl:</comment>
 config_eth1=( "adsl" )
-# <i>ln -s net.eth0 /etc/init.d/net.eth1</i>
+# <i>ln -s net.lo /etc/init.d/net.eth1</i>
 # <i>rc-update add net.eth1 default</i>
 # <i>/etc/init.d/net.eth1 start</i>
 </pre>
@@ -247,7 +247,7 @@
 nameserver 123.123.123.123
 
 <comment>Dynamic and Static Setup:</comment>
-# <i>ln -s net.eth0 /etc/init.d/net.eth1</i>
+# <i>ln -s net.lo /etc/init.d/net.eth1</i>
 # <i>rc-update add net.eth1 default</i>
 # <i>/etc/init.d/net.eth1 start</i>
 </pre>
@@ -413,24 +413,28 @@
 # <i>iptables -F</i>
 # <i>iptables -t nat -F</i>
 
+<comment>Copy and paste these examples ...</comment>
+# <i>export LAN=eth0</i>
+# <i>export WAN=eth1</i>
+
 <comment>Then we lock our services so they only work from the LAN</comment>
-# <i>iptables -I INPUT 1 -i eth0 -j ACCEPT</i>
+# <i>iptables -I INPUT 1 -i ${LAN} -j ACCEPT</i>
 # <i>iptables -I INPUT 1 -i lo -j ACCEPT</i>
-# <i>iptables -A INPUT -p UDP --dport bootps -i ! eth0 -j REJECT</i>
-# <i>iptables -A INPUT -p UDP --dport domain -i ! eth0 -j REJECT</i>
+# <i>iptables -A INPUT -p UDP --dport bootps -i ! ${LAN} -j REJECT</i>
+# <i>iptables -A INPUT -p UDP --dport domain -i ! ${LAN} -j REJECT</i>
 
 <comment>(Optional) Allow access to our ssh server from the WAN</comment>
-# <i>iptables -A INPUT -p TCP --dport ssh -i eth1 -j ACCEPT</i>
+# <i>iptables -A INPUT -p TCP --dport ssh -i ${WAN} -j ACCEPT</i>
 
 <comment>Drop TCP / UDP packets to privileged ports</comment>
-# <i>iptables -A INPUT -p TCP -i ! eth0 -d 0/0 --dport 0:1023 -j DROP</i>
-# <i>iptables -A INPUT -p UDP -i ! eth0 -d 0/0 --dport 0:1023 -j DROP</i>
+# <i>iptables -A INPUT -p TCP -i ! ${LAN} -d 0/0 --dport 0:1023 -j DROP</i>
+# <i>iptables -A INPUT -p UDP -i ! ${LAN} -d 0/0 --dport 0:1023 -j DROP</i>
 
 <comment>Finally we add the rules for NAT</comment>
-# <i>iptables -I FORWARD -i eth0 -d 192.168.0.0/255.255.0.0 -j DROP</i>
-# <i>iptables -A FORWARD -i eth0 -s 192.168.0.0/255.255.0.0 -j ACCEPT</i>
-# <i>iptables -A FORWARD -i eth1 -d 192.168.0.0/255.255.0.0 -j ACCEPT</i>
-# <i>iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE</i>
+# <i>iptables -I FORWARD -i ${LAN} -d 192.168.0.0/255.255.0.0 -j DROP</i>
+# <i>iptables -A FORWARD -i ${LAN} -s 192.168.0.0/255.255.0.0 -j ACCEPT</i>
+# <i>iptables -A FORWARD -i ${WAN} -d 192.168.0.0/255.255.0.0 -j ACCEPT</i>
+# <i>iptables -t nat -A POSTROUTING -o ${WAN} -j MASQUERADE</i>
 <comment>Tell the kernel that ip forwarding is OK</comment>
 # <i>echo 1 > /proc/sys/net/ipv4/ip_forward</i>
 # <i>for f in /proc/sys/net/ipv4/conf/*/rp_filter ; do echo 1 > $f ; done</i>
@@ -486,7 +490,7 @@
 
 <p>
 All the port forwarding rules are of the form <c>iptables -t nat -A PREROUTING
-[-p protocol] --dport [external port on router] -i eth1 -j DNAT --to [ip/port
+[-p protocol] --dport [external port on router] -i ${WAN} -j DNAT --to [ip/port
 to forward to]</c>.  iptables does not accept hostnames when port forwarding.
 If you are forwarding an external port to the same port on the internal
 machine, you can omit the destination port.  See the iptables(8) page for more
@@ -494,29 +498,33 @@
 </p>
 
 <pre caption="Running the iptables commands">
+<comment>Copy and paste these examples ...</comment>
+# <i>export LAN=eth0</i>
+# <i>export WAN=eth1</i>
+
 <comment>Forward port 2 to ssh on an internal host</comment>
-# <i>iptables -t nat -A PREROUTING -p tcp --dport 2 -i eth1 -j DNAT --to 192.168.0.2:22</i>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 2 -i ${WAN} -j DNAT --to 192.168.0.2:22</i>
 
 <comment>FTP forwarding to an internal host</comment>
-# <i>iptables -t nat -A PREROUTING -p tcp --dport 21 -i eth1 -j DNAT --to 192.168.0.56</i>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 21 -i ${WAN} -j DNAT --to 192.168.0.56</i>
 
 <comment>HTTP forwarding to an internal host</comment>
-# <i>iptables -t nat -A PREROUTING -p tcp --dport 80 -i eth1 -j DNAT --to 192.168.0.56</i>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 80 -i ${WAN} -j DNAT --to 192.168.0.56</i>
 
 <comment>VNC forwarding for internal hosts</comment>
-# <i>iptables -t nat -I PREROUTING -p tcp --dport 5900 -i eth1 -j DNAT --to 192.168.0.2</i>
-# <i>iptables -t nat -I PREROUTING -p tcp --dport 5901 -i eth1 -j DNAT --to 192.168.0.3:5900</i>
+# <i>iptables -t nat -I PREROUTING -p tcp --dport 5900 -i ${WAN} -j DNAT --to 192.168.0.2</i>
+# <i>iptables -t nat -I PREROUTING -p tcp --dport 5901 -i ${WAN} -j DNAT --to 192.168.0.3:5900</i>
 <comment>If you want to VNC in to 192.168.0.3, then just add ':1' to the router's hostname</comment>
 
 <comment>Bittorrent forwarding</comment>
-# <i>iptables -t nat -A PREROUTING -p tcp --dport 6881:6889 -i eth1 -j DNAT --to 192.168.0.2</i>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 6881:6889 -i ${WAN} -j DNAT --to 192.168.0.2</i>
 
 <comment>Game Cube Warp Pipe support</comment>
-# <i>iptables -t nat -A PREROUTING -p udp --dport 4000 -i eth1 -j DNAT --to 192.168.0.56</i>
+# <i>iptables -t nat -A PREROUTING -p udp --dport 4000 -i ${WAN} -j DNAT --to 192.168.0.56</i>
 
 <comment>Playstation2 Online support</comment>
-# <i>iptables -t nat -A PREROUTING -p tcp --dport 10070:10080 -i eth1 -j DNAT --to 192.168.0.11</i>
-# <i>iptables -t nat -A PREROUTING -p udp --dport 10070:10080 -i eth1 -j DNAT --to 192.168.0.11</i>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>
+# <i>iptables -t nat -A PREROUTING -p udp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>
 </pre>
 
 <note>
@@ -760,7 +768,7 @@
 # <i>emerge qmail</i>
 <comment>make sure the output of `hostname` is correct</comment>
 # <i>ebuild /var/db/pkg/*-*/qmail-1.03-r*/*.ebuild config</i>
-# <i>iptables -I INPUT -p tcp --dport smtp -i ! eth0 -j REJECT</i>
+# <i>iptables -I INPUT -p tcp --dport smtp -i ! ${LAN} -j REJECT</i>
 # <i>ln -s /var/qmail/supervise/qmail-send /service/qmail-send</i>
 # <i>ln -s /var/qmail/supervise/qmail-smtpd /service/qmail-smtpd</i>
 <!--
@@ -811,7 +819,7 @@
 </chapter>
 
 <chapter>
-<title>Debugging</title>
+<title>Troubleshooting</title>
 
 <section>
 <title>Useful Tools</title>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-08-17 22:42 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-08-17 22:42 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/08/17 22:42:01

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  add a section on troubleshooting dhcpd

Revision  Changes    Path
1.31      +31 -4     xml/htdocs/doc/en/home-router-howto.xml

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
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
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

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- home-router-howto.xml	14 Aug 2005 04:38:48 -0000	1.30
+++ home-router-howto.xml	17 Aug 2005 22:42:01 -0000	1.31
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.30 2005/08/14 04:38:48 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.31 2005/08/17 22:42:01 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.10</version>
-<date>2005-08-14</date>
+<version>1.11</version>
+<date>2005-08-17</date>
 
 <chapter>
 <title>Introduction</title>
@@ -332,7 +332,7 @@
 watch them work!  With Windows systems you should go into the TCP/IP Properties
 and select the 'Obtain an IP address automatically' and 'Obtain DNS server
 address automatically' options.  Sometimes the changes aren't instantaneous, so
-you may have to run a command prompt and run <c>ipconfig /release</c> and
+you may have to open a command prompt and run <c>ipconfig /release</c> and
 <c>ipconfig /renew</c>.  But enough about Windows, let's get back to our
 favorite penguin.
 </p>
@@ -858,6 +858,33 @@
 </section>
 
 <section>
+<title>DHCP Fails To Start</title>
+<body>
+
+<p>
+When starting the dhcp init.d script for the first time, it may fail to load 
+but neglect to give you any useful info.
+</p>
+
+<pre caption="DHCP Failing Example">
+# <i>/etc/init.d/dhcp start</i>
+ * Setting ownership on dhcp.leases ...          [ ok ]
+ * Starting dhcpd ...                            [ !! ]
+</pre>
+
+<p>
+The trick is to know where dhcpd is sending its output.  Simply browse to 
+/var/log and read the log files.  Since the exact log file depends on the 
+package you are using as a syslog, try running <c>grep -Rl dhcpd /var/log</c> 
+to narrow down the possibilities.  Chances are you made a typo in your config 
+file.  You could also try running <c>dhcpd -d -f</c> (short for debug / 
+foreground) and debug the error based upon the output.
+</p>
+
+</body>
+</section>
+
+<section>
 <title>Incorrect MTU Value</title>
 <body>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-09-06  3:03 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-09-06  3:03 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/09/06 03:03:19

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  forgot to copy & paste default policy settings

Revision  Changes    Path
1.32      +8 -3      xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.32&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.32&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.31&r2=1.32&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- home-router-howto.xml	17 Aug 2005 22:42:01 -0000	1.31
+++ home-router-howto.xml	6 Sep 2005 03:03:19 -0000	1.32
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.31 2005/08/17 22:42:01 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.32 2005/09/06 03:03:19 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.11</version>
-<date>2005-08-17</date>
+<version>1.12</version>
+<date>2005-09-05</date>
 
 <chapter>
 <title>Introduction</title>
@@ -413,6 +413,11 @@
 # <i>iptables -F</i>
 # <i>iptables -t nat -F</i>
 
+<comment>Setup default policies to handle not matched by any rules</comment>
+# <i>iptables -P INPUT ACCEPT</i>
+# <i>iptables -P OUTPUT ACCEPT</i>
+# <i>iptables -P FORWARD DROP</i>
+
 <comment>Copy and paste these examples ...</comment>
 # <i>export LAN=eth0</i>
 # <i>export WAN=eth1</i>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-09-17  7:40 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-09-17  7:40 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/09/17 07:40:13

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  replace the dhcp section with the dhcp server from dnsmasq as suggested by many peeps, move the old dhcp section to the Fun section, touchup grammer in a few sections, and add an example iptables rule for edonkey

Revision  Changes    Path
1.33      +90 -55    xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.33&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.33&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.32&r2=1.33&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- home-router-howto.xml	6 Sep 2005 03:03:19 -0000	1.32
+++ home-router-howto.xml	17 Sep 2005 07:40:13 -0000	1.33
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.32 2005/09/06 03:03:19 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.33 2005/09/17 07:40:13 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.12</version>
-<date>2005-09-05</date>
+<version>1.20</version>
+<date>2005-09-17</date>
 
 <chapter>
 <title>Introduction</title>
@@ -299,32 +299,32 @@
 <p>
 DHCP is exactly what its name implies.  It's a protocol that allows you 
 to dynamically configure other hosts automatically.  You run a DHCP server on
-the router (dhcpd), give it all the information about your network (valid IPs,
+the router, give it all the information about your network (valid IPs,
 DNS servers, gateways, etc...), and then when the other hosts start up, they
 run a DHCP client to automatically configure themselves.  No fuss, no muss!
 For more information about DHCP, you can always visit <uri
 link="http://en.wikipedia.org/wiki/DHCP">Wikipedia</uri>.
 </p>
 
-<pre caption="Setting up dhcpd">
-# <i>emerge dhcp</i>
-# <i>nano /etc/dhcp/dhcpd.conf</i>
-<comment>(Here is a sample configuration file:)</comment>
-authoritative;
-ddns-update-style interim;
-subnet 192.168.0.0 netmask 255.255.255.0 {
-    range 192.168.0.100 192.168.0.250;
-    default-lease-time 259200;
-    max-lease-time 518400;
-    option subnet-mask 255.255.255.0;
-    option broadcast-address 192.168.0.255;
-    option routers 192.168.0.1;
-    option domain-name-servers 192.168.0.1;
-}
-# <i>nano /etc/conf.d/dhcp</i>
-<comment>(Set IFACE="eth0")</comment>
-# <i>rc-update add dhcp default</i>
-# <i>/etc/init.d/dhcp start</i>
+<p>
+We'll use a package called dnsmasq which provides both DHCP and DNS services.
+For now lets just focus on the DHCP aspect.  Note that if you want to run a
+different DHCP server, you can find another example in the Fun Things chapter.
+Also, if you wish to tinker with the DHCP server settings, just read the 
+comments in <path>/etc/dnsmasq.conf</path>.  All the defaults should work fine 
+though.
+</p>
+
+<pre caption="Setting up a DHCP server">
+# <i>emerge dnsmasq</i>
+# <i>nano /etc/dnsmasq.conf</i>
+<comment>You should need to just add this one line:</comment>
+dhcp-range=192.168.0.100,192.168.0.250,72h
+
+# <i>nano /etc/conf.d/dnsmasq</i>
+<comment>Add "-i eth0" to DNSMASQ_OPTS</comment>
+# <i>rc-update add dnsmasq default</i>
+# <i>/etc/init.d/dnsmasq start</i>
 </pre>
 
 <p>
@@ -346,7 +346,7 @@
 
 <p>
 When people want to visit a place on the internet, they remember names, not a
-string of useless numbers.  After all, what's easier to remember, ebay.com or
+string of funky numbers.  After all, what's easier to remember, ebay.com or
 66.135.192.87?  This is where the DNS steps in.  DNS servers run all over the
 internet, and whenever someone wants to visit 'ebay.com', these servers turn
 'ebay.com' (what we understand) into '66.135.192.87' (what our computers
@@ -355,28 +355,17 @@
 </p>
 
 <p>
-You may have noticed in the previous section that we told the DHCP clients we
-have a DNS server at 192.168.0.1.  You may also remember that 192.168.0.1 is
-our little router that we're making.  I don't remember setting up a DNS server
-... so let's do so now!
+Since we're using dnsmasq for our DHCP server, and it includes a DNS server,
+you've got nothing left to do here!  Your little router is already providing
+DNS to its DHCP clients.  Bet you wish everything was this easy ;).
 </p>
 
-<pre caption="Setting up dnsmasq">
-# <i>emerge dnsmasq</i>
-# <i>nano /etc/conf.d/dnsmasq</i>
-<comment>Add "-i eth0" to DNSMASQ_OPTS</comment>
-# <i>rc-update add dnsmasq default</i>
-# <i>/etc/init.d/dnsmasq start</i>
-</pre>
-
 <p>
-Well that was quick, but what did we do?  The great thing is, we didn't have to
-do very much!  You're welcome to choose other DNS servers if you're more
-comfortable with them, but the reason dnsmasq is great is because it was
-designed to do exactly what we want and nothing more.  It's a little DNS
-caching/forwarding server for local networks.  We're not looking to provide DNS
-for our own domain here, just offer simple DNS services to everyone else on our
-LAN.
+You're welcome to choose other DNS servers if you're more comfortable with 
+them, but the reason dnsmasq is great is because it was designed to do exactly 
+what we want and nothing more.  It's a little DNS caching/forwarding server for 
+local networks.  We're not looking to provide DNS for our own domain here, just 
+offer simple DNS services to everyone else on our LAN.
 </p>
 
 </body>
@@ -394,12 +383,12 @@
 </p>
 
 <p>
-This is where NAT steps in.  NAT is a way of connecting multiple computers in a
-private LAN to the internet when you only have a smaller number of IP addresses
-availabe to you.  Typically you were given 1 IP by your ISP, but you want to
-let your whole house connect to the internet.  NAT is the magic that makes this
-possible.  For more information about NAT, you can always visit <uri
-link="http://en.wikipedia.org/wiki/NAT">Wikipedia</uri>.
+This is where Network Address Translation (NAT) steps in.  NAT is a way of 
+connecting multiple computers in a private LAN to the internet when you have a 
+smaller number of public IP addresses available to you.  Typically you are given 
+1 IP by your ISP, but you want to let your whole house connect to the internet.
+NAT is the magic that makes this possible.  For more information about NAT, you 
+can always visit <uri link="http://en.wikipedia.org/wiki/NAT">Wikipedia</uri>.
 </p>
 
 <note>
@@ -413,7 +402,7 @@
 # <i>iptables -F</i>
 # <i>iptables -t nat -F</i>
 
-<comment>Setup default policies to handle not matched by any rules</comment>
+<comment>Setup default policies to handle unmatched traffic</comment>
 # <i>iptables -P INPUT ACCEPT</i>
 # <i>iptables -P OUTPUT ACCEPT</i>
 # <i>iptables -P FORWARD DROP</i>
@@ -496,10 +485,10 @@
 <p>
 All the port forwarding rules are of the form <c>iptables -t nat -A PREROUTING
 [-p protocol] --dport [external port on router] -i ${WAN} -j DNAT --to [ip/port
-to forward to]</c>.  iptables does not accept hostnames when port forwarding.
-If you are forwarding an external port to the same port on the internal
-machine, you can omit the destination port.  See the iptables(8) page for more
-information.
+to forward to]</c>.  Unfortunately, iptables does not accept hostnames when port
+forwarding.  If you are forwarding an external port to the same port on the 
+internal machine, you can omit the destination port.  See the iptables(8) man 
+page for more information.
 </p>
 
 <pre caption="Running the iptables commands">
@@ -524,10 +513,13 @@
 <comment>Bittorrent forwarding</comment>
 # <i>iptables -t nat -A PREROUTING -p tcp --dport 6881:6889 -i ${WAN} -j DNAT --to 192.168.0.2</i>
 
+<comment>eDonkey/eMule forwarding</comment>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 4662 -i ${WAN} -j DNAT --to 192.168.0.55</i>
+
 <comment>Game Cube Warp Pipe support</comment>
 # <i>iptables -t nat -A PREROUTING -p udp --dport 4000 -i ${WAN} -j DNAT --to 192.168.0.56</i>
 
-<comment>Playstation2 Online support</comment>
+<comment>Playstation 2 Online support</comment>
 # <i>iptables -t nat -A PREROUTING -p tcp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>
 # <i>iptables -t nat -A PREROUTING -p udp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>
 </pre>
@@ -821,6 +813,49 @@
 </section>
 -->
 
+<section>
+<title>Full DHCP Server</title>
+<body>
+
+<p>
+Earlier we used dnsmasq to provide DHCP service to all our clients.  For most
+people with a simple small LAN, this is perfect.  But you may need something 
+with more features.  Thus we turn to a full-featured DHCP server as provided 
+by the <uri link="http://www.isc.org/products/DHCP">ISC</uri> folks.
+</p>
+
+<pre caption="Setting up dhcpd">



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-10-11  1:02 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-10-11  1:02 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/10/11 01:02:53

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  add example for Xbox Live from Chris Slycord

Revision  Changes    Path
1.34      +8 -3      xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.34&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.34&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.33&r2=1.34&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- home-router-howto.xml	17 Sep 2005 07:40:13 -0000	1.33
+++ home-router-howto.xml	11 Oct 2005 01:02:53 -0000	1.34
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.33 2005/09/17 07:40:13 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.34 2005/10/11 01:02:53 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.20</version>
-<date>2005-09-17</date>
+<version>1.21</version>
+<date>2005-10-10</date>
 
 <chapter>
 <title>Introduction</title>
@@ -522,6 +522,11 @@
 <comment>Playstation 2 Online support</comment>
 # <i>iptables -t nat -A PREROUTING -p tcp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>
 # <i>iptables -t nat -A PREROUTING -p udp --dport 10070:10080 -i ${WAN} -j DNAT --to 192.168.0.11</i>
+
+<comment>Xbox Live</comment>
+# <i>iptables -t nat -A PREROUTING -p tcp --dport 3074 -i ${WAN} -j DNAT --to 192.168.0.69</i>
+# <i>iptables -t nat -A PREROUTING -p udp --dport 3074 -i ${WAN} -j DNAT --to 192.168.0.69</i>
+# <i>iptables -t nat -A PREROUTING -p udp --dport 88 -i ${WAN} -j DNAT --to 192.168.0.69</i>
 </pre>
 
 <note>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-11-05  2:45 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-11-05  2:45 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/11/05 02:45:18

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  add info for kernel features that adsl/pppoe require as noted by Jonathan Schmieg

Revision  Changes    Path
1.35      +16 -7     xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.35&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.35&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.34&r2=1.35&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- home-router-howto.xml	11 Oct 2005 01:02:53 -0000	1.34
+++ home-router-howto.xml	5 Nov 2005 02:45:18 -0000	1.35
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.34 2005/10/11 01:02:53 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.35 2005/11/05 02:45:18 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/home-router-howto.xml">
@@ -15,8 +15,8 @@
 for connecting your home network to the internet.
 </abstract>
 
-<version>1.21</version>
-<date>2005-10-10</date>
+<version>1.22</version>
+<date>2005-11-04</date>
 
 <chapter>
 <title>Introduction</title>
@@ -109,10 +109,11 @@
 
 <p>
 The next thing you'll need is support for iptables and NAT (and packet shaping
-if you want).  The following list is split up into required (*), suggested (x),
-and shaper (s) features.  It does not matter whether you build the features
-into the kernel or as a module so long as when the feature is needed, the
-correct module(s) are loaded (module loading is left to the reader as a fun
+if you want).  The following list is split up into always required (*), 
+required only for adsl via PPPoE (a), suggested for everyone (x), and only 
+for shaper (s) features.  It does not matter whether you build the features 
+into the kernel or as a module so long as when the feature is needed, the 
+correct module(s) are loaded (module loading is left to the reader as a fun 
 exercise however).
 </p>
 
@@ -145,6 +146,14 @@
       [s] QoS and/or fair queueing
          [s] HTB packet scheduler
          [s] Ingress Qdisc
+
+   [a] PPP (point-to-point protocol) support
+      [a] PPP filtering
+      [a] PPP support for async serial ports
+      [a] PPP support for sync tty ports
+      [a] PPP Deflate compression
+      [a] PPP BSD-Compress compression
+      [a] PPP over Ethernet
 </pre>
 
 <note>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-11-09  3:59 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-11-09  3:59 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/11/09 03:59:41

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  add license tag and touchup internal format

Revision  Changes    Path
1.36      +5 -3      xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.36&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.36&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.35&r2=1.36&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- home-router-howto.xml	5 Nov 2005 02:45:18 -0000	1.35
+++ home-router-howto.xml	9 Nov 2005 03:59:40 -0000	1.36
@@ -1,9 +1,8 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.35 2005/11/05 02:45:18 vapier Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.36 2005/11/09 03:59:40 vapier Exp $ -->
 
-<guide link="/doc/en/home-router-howto.xml">
-
+<guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
 
 <author title="Author">
@@ -15,6 +14,9 @@
 for connecting your home network to the internet.
 </abstract>
 
+<!-- The content of this document is released into the public domain -->
+<license/>
+
 <version>1.22</version>
 <date>2005-11-04</date>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-12-05 13:34 Xavier Neys
  0 siblings, 0 replies; 32+ messages in thread
From: Xavier Neys @ 2005-12-05 13:34 UTC (permalink / raw
  To: gentoo-doc-cvs

neysx       05/12/05 13:34:49

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  s/<uri link="mailto:/<mail link="/

Revision  Changes    Path
1.37      +3 -3      xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.37&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.37&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.36&r2=1.37&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- home-router-howto.xml	9 Nov 2005 03:59:40 -0000	1.36
+++ home-router-howto.xml	5 Dec 2005 13:34:49 -0000	1.37
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.36 2005/11/09 03:59:40 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.37 2005/12/05 13:34:49 neysx Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -541,8 +541,8 @@
 </pre>
 
 <note>
-If you have other common / cool examples, please <uri
-link="mailto:vapier@gentoo.org">e-mail me</uri>.
+If you have other common / cool examples, please <mail
+link="vapier@gentoo.org">e-mail me</mail>.
 </note>
 
 </body>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-12-12  4:36 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-12-12  4:36 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/12/12 04:36:21

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  add some notes on adding more LANs

Revision  Changes    Path
1.38      +42 -3     xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.38&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.38&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.37&r2=1.38&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- home-router-howto.xml	5 Dec 2005 13:34:49 -0000	1.37
+++ home-router-howto.xml	12 Dec 2005 04:36:21 -0000	1.38
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.37 2005/12/05 13:34:49 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.38 2005/12/12 04:36:21 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.22</version>
-<date>2005-11-04</date>
+<version>1.23</version>
+<date>2005-12-11</date>
 
 <chapter>
 <title>Introduction</title>
@@ -872,6 +872,45 @@
 </body>
 </section>
 
+<section>
+<title>Connect Another LAN (or two or three or ...)</title>
+<body>
+
+<p>
+Sometimes you have need of connecting the router to another LAN.  Maybe you 
+want to hook up a group of friends temporarily, or you're a neat freak and 
+want to section off different groups of computers, or you're just really 
+really bored.  Whatever the reasons, extending the router to other LAN 
+networks should be pretty straightforward.  In the following examples, I will 
+assume that this new network is connected via a third ethernet card, namely 
+<c>eth2</c>.
+</p>
+
+<p>
+First you need to configure the interface.  Just take the instructions in the 
+<uri link="#doc_chap4_pre1">4.1 code listing</uri> and replace <c>eth0</c> 
+with <c>eth2</c> and <c>192.168.0</c> with <c>192.168.1</c>.
+</p>
+
+<p>
+Then you need to tweak dnsmasq to service the new interface.  Just edit the 
+<path>/etc/conf.d/dnsmasq</path> file again and append <c>-i eth2</c> to 
+DNSMASQ_OPTS; using -i multiple times is OK.  Then edit 
+<path>/etc/dnsmasq.conf</path> and add another line like the dhcp-range line 
+in the <uri link="#doc_chap5_pre1">5.1 code listing</uri>, replacing 
+<c>192.168.0</c> with <c>192.168.1</c>.  Having multiple dhcp-range lines is 
+OK too.
+</p>
+
+<p>
+Finally, see the rules in the <uri link="#doc_chap5_pre2">5.2 code 
+listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them.  You 
+may want to create another variable, say <c>LAN2</c>, to make things easier.
+</p>
+
+</body>
+</section>
+
 </chapter>
 
 <chapter>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-12-21  1:09 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2005-12-21  1:09 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      05/12/21 01:09:14

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  update notes to baselayout-1.11.14+

Revision  Changes    Path
1.39      +8 -12     xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.39&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.39&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.38&r2=1.39&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- home-router-howto.xml	12 Dec 2005 04:36:21 -0000	1.38
+++ home-router-howto.xml	21 Dec 2005 01:09:14 -0000	1.39
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.38 2005/12/12 04:36:21 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.39 2005/12/21 01:09:14 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -199,33 +199,29 @@
 </p>
 
 <note>
-In order for the following net.eth1 settings to work, you must have 
-baselayout-1.10.1 or later installed on your system.
+In order for the following net settings to work, you must have 
+baselayout-1.11.14 or later installed on your system.
 </note>
 
 <pre caption="Setting up eth1">
 <comment>(Replace 'vla9h924' with your username and 'password' with your password)</comment>
 
-# <i>nano /etc/ppp/pppoe.conf</i>
-<comment># Ethernet card connected to ADSL modem</comment>
-ETH=eth1
-<comment># ADSL user name.</comment>
-USER=vla9h924
 # <i>nano /etc/ppp/pap-secrets</i>
 <comment># client    server  secret</comment>
 "vla9h924" * "password"
 # <i>nano /etc/conf.d/net</i>
-<comment>Add an entry for config_eth1 and set it to adsl:</comment>
+<comment>Tell baselayout to use adsl for your eth1:</comment>
 config_eth1=( "adsl" )
+user_eth1=( "vla9h924" )
 # <i>ln -s net.lo /etc/init.d/net.eth1</i>
 # <i>rc-update add net.eth1 default</i>
 # <i>/etc/init.d/net.eth1 start</i>
 </pre>
 
 <warn>
-When the DSL interface comes up, it will create ppp0.  Although your NIC 
-is called eth1, the IP is actually bound to ppp0.  From now on, when you 
-see examples that utilize 'eth1', substitute with 'ppp0'.
+When the DSL interface comes up, it will create ppp0.  Although your NIC is 
+called eth1, the IP is actually bound to ppp0.  From now on, when you see 
+examples that utilize 'eth1', substitute with 'ppp0'.
 </warn>
 
 </body>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2005-12-21 11:12 Xavier Neys
  0 siblings, 0 replies; 32+ messages in thread
From: Xavier Neys @ 2005-12-21 11:12 UTC (permalink / raw
  To: gentoo-doc-cvs

neysx       05/12/21 11:12:59

  Modified:    xml/htdocs/doc/en home-router-howto.xml
  Log:
  Should have been bumped

Revision  Changes    Path
1.40      +3 -3      xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.40&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.40&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.39&r2=1.40&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- home-router-howto.xml	21 Dec 2005 01:09:14 -0000	1.39
+++ home-router-howto.xml	21 Dec 2005 11:12:59 -0000	1.40
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.39 2005/12/21 01:09:14 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.40 2005/12/21 11:12:59 neysx Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.23</version>
-<date>2005-12-11</date>
+<version>1.24</version>
+<date>2005-12-20</date>
 
 <chapter>
 <title>Introduction</title>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-03-17 10:17 Xavier Neys
  0 siblings, 0 replies; 32+ messages in thread
From: Xavier Neys @ 2006-03-17 10:17 UTC (permalink / raw
  To: gentoo-doc-cvs

neysx       06/03/17 10:17:04

  Modified:             home-router-howto.xml
  Log:
  #126489 grep lspci output

Revision  Changes    Path
1.42                 xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.42&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.42&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.41&r2=1.42&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- home-router-howto.xml	1 Jan 2006 11:51:43 -0000	1.41
+++ home-router-howto.xml	17 Mar 2006 10:17:04 -0000	1.42
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.41 2006/01/01 11:51:43 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.42 2006/03/17 10:17:04 neysx Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.24</version>
-<date>2005-12-20</date>
+<version>1.25</version>
+<date>2006-03-17</date>
 
 <chapter>
 <title>Introduction</title>
@@ -104,9 +104,9 @@
 
 <p>
 If you do not see your two cards showing up and you're not sure what kind of
-cards you have, try running <c>lspci</c>.  You can get that from <c>emerge
-pciutils</c>.  Look for "Ethernet controller" in the output.  Once you have
-this information, go into your kernel and add support for the correct drivers.
+cards you have, try running <c>lspci | grep Ethernet</c>. You can get that from
+<c>emerge pciutils</c>. Once you have this information, go into your kernel and
+add support for the correct drivers.
 </p>
 
 <p>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-03-29  1:30 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-03-29  1:30 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/03/29 01:30:32

  Modified:             home-router-howto.xml
  Log:
  some baselayout/dnsmasq tweaks from Davide Giannotti

Revision  Changes    Path
1.43                 xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.43&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.43&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.42&r2=1.43&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- home-router-howto.xml	17 Mar 2006 10:17:04 -0000	1.42
+++ home-router-howto.xml	29 Mar 2006 01:30:31 -0000	1.43
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.42 2006/03/17 10:17:04 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.43 2006/03/29 01:30:31 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.25</version>
-<date>2006-03-17</date>
+<version>1.26</version>
+<date>2006-03-28</date>
 
 <chapter>
 <title>Introduction</title>
@@ -247,7 +247,7 @@
 <comment>Static IP Users:</comment>
 # <i>nano /etc/conf.d/net</i>
 <comment>You'll need entries like so:</comment>
-ifconfig_eth1=( "66.92.78.102 broadcast 66.92.78.255 netmask 255.255.255.0" )
+config_eth1=( "66.92.78.102 broadcast 66.92.78.255 netmask 255.255.255.0" )
 routes_eth1=( "default gw 66.92.78.1" )
 # <i>nano /etc/resolv.conf</i>
 <comment>Add one line per DNS server:</comment>
@@ -279,7 +279,7 @@
 <pre caption="Setting up eth0">
 # <i>nano /etc/conf.d/net</i>
 <comment>Add a line like the following:</comment>
-ifconfig_eth0=( "192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" )
+config_eth0=( "192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" )
 # <i>rc-update add net.eth0 default</i>
 # <i>/etc/init.d/net.eth0 start</i>
 </pre>
@@ -325,11 +325,11 @@
 <pre caption="Setting up a DHCP server">
 # <i>emerge dnsmasq</i>
 # <i>nano /etc/dnsmasq.conf</i>
-<comment>You should need to just add this one line:</comment>
+<comment>Add this line to enable dhcp:</comment>
 dhcp-range=192.168.0.100,192.168.0.250,72h
+<comment>Restrict dnsmasq to just the LAN interface</comment>
+interface=eth0
 
-# <i>nano /etc/conf.d/dnsmasq</i>
-<comment>Add "-i eth0" to DNSMASQ_OPTS</comment>
 # <i>rc-update add dnsmasq default</i>
 # <i>/etc/init.d/dnsmasq start</i>
 </pre>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-04-09 17:22 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-04-09 17:22 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/04/09 17:22:49

  Modified:             home-router-howto.xml
  Log:
  fix paths to dhcp server config files as pointed out by Harold Naparst via e-mail

Revision  Changes    Path
1.44                 xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.44&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.44&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.43&r2=1.44&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- home-router-howto.xml	29 Mar 2006 01:30:31 -0000	1.43
+++ home-router-howto.xml	9 Apr 2006 17:22:49 -0000	1.44
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.43 2006/03/29 01:30:31 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.44 2006/04/09 17:22:49 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.26</version>
-<date>2006-03-28</date>
+<version>1.27</version>
+<date>2006-04-09</date>
 
 <chapter>
 <title>Introduction</title>
@@ -851,10 +851,10 @@
     option routers 192.168.0.1;
     option domain-name-servers 192.168.0.1;
 }
-# <i>nano /etc/conf.d/dhcp</i>
+# <i>nano /etc/conf.d/dhcpd</i>
 <comment>(Set IFACE="eth0")</comment>
-# <i>rc-update add dhcp default</i>
-# <i>/etc/init.d/dhcp start</i>
+# <i>rc-update add dhcpd default</i>
+# <i>/etc/init.d/dhcpd start</i>
 </pre>
 
 <p>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-06-13  9:47 Xavier Neys
  0 siblings, 0 replies; 32+ messages in thread
From: Xavier Neys @ 2006-06-13  9:47 UTC (permalink / raw
  To: gentoo-doc-cvs

neysx       06/06/13 09:47:07

  Modified:             home-router-howto.xml
  Log:
  Fixed link to rsync.xml

Revision  Changes    Path
1.45                 xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.45&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.45&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.44&r2=1.45&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- home-router-howto.xml	9 Apr 2006 17:22:49 -0000	1.44
+++ home-router-howto.xml	13 Jun 2006 09:47:07 -0000	1.45
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.44 2006/04/09 17:22:49 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.45 2006/06/13 09:47:07 neysx Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.27</version>
-<date>2006-04-09</date>
+<version>1.28</version>
+<date>2006-06-13</date>
 
 <chapter>
 <title>Introduction</title>
@@ -715,9 +715,10 @@
 servers.  By setting up a local rsync, you save on both your bandwidth and 
 the Gentoo rsync servers' bandwidth.  It's pretty simple to do.
 </p>
+
 <note>
-For a much more in-depth rsync guide, please see the official <uri 
-link="/doc/en/rsync.xml#doc_chap4">rsync guide</uri>
+For a much more in-depth rsync guide, please see the official <uri
+link="/doc/en/rsync.xml#local">rsync guide</uri>.
 </note>
 
 <p>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-06-18 12:21 Lukasz Damentko
  0 siblings, 0 replies; 32+ messages in thread
From: Lukasz Damentko @ 2006-06-18 12:21 UTC (permalink / raw
  To: gentoo-doc-cvs

rane        06/06/18 12:21:24

  Modified:             home-router-howto.xml
  Log:
  added one lacking <path>, removed some double spaces, no content change

Revision  Changes    Path
1.46                 xml/htdocs/doc/en/home-router-howto.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.46&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml?rev=1.46&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/home-router-howto.xml.diff?r1=1.45&r2=1.46&cvsroot=gentoo

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- home-router-howto.xml	13 Jun 2006 09:47:07 -0000	1.45
+++ home-router-howto.xml	18 Jun 2006 12:21:24 -0000	1.46
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.45 2006/06/13 09:47:07 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.46 2006/06/18 12:21:24 rane Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -965,12 +965,12 @@
 </pre>
 
 <p>
-The trick is to know where dhcpd is sending its output.  Simply browse to 
-/var/log and read the log files.  Since the exact log file depends on the 
-package you are using as a syslog, try running <c>grep -Rl dhcpd /var/log</c> 
-to narrow down the possibilities.  Chances are you made a typo in your config 
-file.  You could also try running <c>dhcpd -d -f</c> (short for debug / 
-foreground) and debug the error based upon the output.
+The trick is to know where dhcpd is sending its output. Simply browse to
+<path>/var/log</path> and read the log files. Since the exact log file depends
+on the package you are using as a syslog, try running <c>grep -Rl dhcpd
+/var/log</c> to narrow down the possibilities. Chances are you made a typo in
+your config file. You could also try running <c>dhcpd -d -f</c> (short for
+debug / foreground) and debug the error based upon the output.
 </p>
 
 </body>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-08-04 13:24 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-08-04 13:24 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/08/04 13:24:16

  Modified:             home-router-howto.xml
  Log:
  add a debug section about crossover cables

Revision  Changes    Path
1.47                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.47&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.47&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.46&r2=1.47

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- home-router-howto.xml	18 Jun 2006 12:21:24 -0000	1.46
+++ home-router-howto.xml	4 Aug 2006 13:24:16 -0000	1.47
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.46 2006/06/18 12:21:24 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.47 2006/08/04 13:24:16 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.28</version>
-<date>2006-06-13</date>
+<version>1.29</version>
+<date>2006-08-04</date>
 
 <chapter>
 <title>Introduction</title>
@@ -1002,6 +1002,21 @@
 </body>
 </section>
 
+<section>
+<title>Unable to connect two machines directly</title>
+<body>
+
+<p>
+If (for whatever reason) you want to connect two machines directly together 
+without a hub or switch, a regular ethernet cable will not work.  You will 
+need a different cable called a crossover cable.  This <uri 
+link="http://en.wikipedia.org/wiki/Ethernet_crossover_cable">Wikipedia</uri>
+page explains the low level details.
+</p>
+
+</body>
+</section>
+
 </chapter>
 
 <chapter>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-08-12 12:18 Jan Kundrat
  0 siblings, 0 replies; 32+ messages in thread
From: Jan Kundrat @ 2006-08-12 12:18 UTC (permalink / raw
  To: gentoo-doc-cvs

jkt         06/08/12 12:18:55

  Modified:             home-router-howto.xml
  Log:
  Adding info about auto MDI/MDI-X NICs

Revision  Changes    Path
1.48                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.48&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.48&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.47&r2=1.48

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- home-router-howto.xml	4 Aug 2006 13:24:16 -0000	1.47
+++ home-router-howto.xml	12 Aug 2006 12:18:55 -0000	1.48
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.47 2006/08/04 13:24:16 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.48 2006/08/12 12:18:55 jkt Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.29</version>
-<date>2006-08-04</date>
+<version>1.30</version>
+<date>2006-08-12</date>
 
 <chapter>
 <title>Introduction</title>
@@ -1008,8 +1008,9 @@
 
 <p>
 If (for whatever reason) you want to connect two machines directly together 
-without a hub or switch, a regular ethernet cable will not work.  You will 
-need a different cable called a crossover cable.  This <uri 
+without a hub or switch, a regular ethernet cable will likely not work, unless
+you have an Auto MDI/MDI-X (also known as "autosensing") capable network
+adapter.  You will need a different cable called a crossover cable.  This <uri
 link="http://en.wikipedia.org/wiki/Ethernet_crossover_cable">Wikipedia</uri>
 page explains the low level details.
 </p>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-08-21 10:21 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-08-21 10:21 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/08/21 10:21:57

  Modified:             home-router-howto.xml
  Log:
  add missing spaces

Revision  Changes    Path
1.49                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.49&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.49&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.48&r2=1.49

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- home-router-howto.xml	12 Aug 2006 12:18:55 -0000	1.48
+++ home-router-howto.xml	21 Aug 2006 10:21:57 -0000	1.49
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.48 2006/08/12 12:18:55 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.49 2006/08/21 10:21:57 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -104,9 +104,9 @@
 
 <p>
 If you do not see your two cards showing up and you're not sure what kind of
-cards you have, try running <c>lspci | grep Ethernet</c>. You can get that from
-<c>emerge pciutils</c>. Once you have this information, go into your kernel and
-add support for the correct drivers.
+cards you have, try running <c>lspci | grep Ethernet</c>.  You can get that
+from <c>emerge pciutils</c>.  Once you have this information, go into your
+kernel and add support for the correct drivers.
 </p>
 
 <p>
@@ -965,11 +965,11 @@
 </pre>
 
 <p>
-The trick is to know where dhcpd is sending its output. Simply browse to
-<path>/var/log</path> and read the log files. Since the exact log file depends
+The trick is to know where dhcpd is sending its output.  Simply browse to
+<path>/var/log</path> and read the log files.  Since the exact log file depends
 on the package you are using as a syslog, try running <c>grep -Rl dhcpd
-/var/log</c> to narrow down the possibilities. Chances are you made a typo in
-your config file. You could also try running <c>dhcpd -d -f</c> (short for
+/var/log</c> to narrow down the possibilities.  Chances are you made a typo in
+your config file.  You could also try running <c>dhcpd -d -f</c> (short for
 debug / foreground) and debug the error based upon the output.
 </p>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-08-21 10:47 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-08-21 10:47 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/08/21 10:47:37

  Modified:             home-router-howto.xml
  Log:
  add a small section on ip_dynaddr for Kristian

Revision  Changes    Path
1.50                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.50&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.50&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.49&r2=1.50

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- home-router-howto.xml	21 Aug 2006 10:21:57 -0000	1.49
+++ home-router-howto.xml	21 Aug 2006 10:47:36 -0000	1.50
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.49 2006/08/21 10:21:57 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.50 2006/08/21 10:47:36 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.30</version>
-<date>2006-08-12</date>
+<version>1.31</version>
+<date>2006-08-21</date>
 
 <chapter>
 <title>Introduction</title>
@@ -444,9 +444,12 @@
 # <i>/etc/init.d/iptables save</i>
 # <i>rc-update add iptables default</i>
 # <i>nano /etc/sysctl.conf</i>
-<comment>Add/Uncomment the following lines:
+<comment>Add/Uncomment the following lines:</comment>
 net.ipv4.ip_forward = 1
-net.ipv4.conf.default.rp_filter = 1</comment>
+net.ipv4.conf.default.rp_filter = 1
+
+<comment>If you have a dynamic internet address you probably want to enable this:</comment>
+net.ipv4.ip_dynaddr = 1
 </pre>
 
 <p>
@@ -454,6 +457,13 @@
 to use the internet as if they were directly connected themselves.  
 </p>
 
+<p>
+The ip_dynaddr option is useful for dial on demand systems or when your ISP
+gives out dynamic addresses.  This works around the problem where a connection
+is attempted before the internet interface is fully setup.  Really this just
+provides for a smoother network experience for users behind your router.
+</p>
+
 </body>
 </section>
 </chapter>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-08-21 10:50 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-08-21 10:50 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/08/21 10:50:14

  Modified:             home-router-howto.xml
  Log:
  add a note that even 2.6 kernels move crap around

Revision  Changes    Path
1.51                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.51&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.51&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.50&r2=1.51

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- home-router-howto.xml	21 Aug 2006 10:47:36 -0000	1.50
+++ home-router-howto.xml	21 Aug 2006 10:50:14 -0000	1.51
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.50 2006/08/21 10:47:36 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.51 2006/08/21 10:50:14 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -159,8 +159,9 @@
 </pre>
 
 <note>
-Somethings may be slightly different in a 2.4 vs 2.6 kernel, but you should be
-able to figure it out :).
+Some things may be slightly different in a 2.4 vs 2.6 kernel, but you should be
+able to figure it out :).  Even among 2.6 kernels, these options have a
+tendency to move around.  Good luck!
 </note>
 
 </body>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-09-16  5:29 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-09-16  5:29 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/09/16 05:29:33

  Modified:             home-router-howto.xml
  Log:
  fix a grammar bug pointed out by Michael L.

Revision  Changes    Path
1.52                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.52&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.52&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.51&r2=1.52

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- home-router-howto.xml	21 Aug 2006 10:50:14 -0000	1.51
+++ home-router-howto.xml	16 Sep 2006 05:29:33 -0000	1.52
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.51 2006/08/21 10:50:14 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.52 2006/09/16 05:29:33 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -992,9 +992,9 @@
 <body>
 
 <p>
-If you experience odd errors (such as not being some webpages while others 
-load fine), you may be having Path MTU Discovery trouble.  The quick way to 
-test is to run this iptables command:
+If you experience odd errors (such as not being able to access some webpages
+while others load fine), you may be having Path MTU Discovery trouble.  The
+quick way to test is to run this iptables command:
 </p>
 
 <pre caption="Circumvent MTU issues">



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-10-21 21:04 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2006-10-21 21:04 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      06/10/21 21:04:48

  Modified:             home-router-howto.xml
  Log:
  s/ethereal/wireshark/ as reported by Philip Stone

Revision  Changes    Path
1.53                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.53&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.53&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.52&r2=1.53

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- home-router-howto.xml	16 Sep 2006 05:29:33 -0000	1.52
+++ home-router-howto.xml	21 Oct 2006 21:04:48 -0000	1.53
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.52 2006/09/16 05:29:33 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.53 2006/10/21 21:04:48 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.31</version>
-<date>2006-08-21</date>
+<version>1.32</version>
+<date>2006-10-21</date>
 
 <chapter>
 <title>Introduction</title>
@@ -940,7 +940,7 @@
   <th>Description</th>
 </tr>
 <tr>
-  <ti>ethereal</ti>
+  <ti>wireshark</ti>
   <ti>GUI tool to view all raw network data according to filters</ti>
 </tr>
 <tr>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2006-11-08 19:39 Josh Saddler
  0 siblings, 0 replies; 32+ messages in thread
From: Josh Saddler @ 2006-11-08 19:39 UTC (permalink / raw
  To: gentoo-doc-cvs

nightmorph    06/11/08 19:39:24

  Modified:             home-router-howto.xml
  Log:
  updated home-router-howto for bug 154473

Revision  Changes    Path
1.54                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.54&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.54&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.53&r2=1.54

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- home-router-howto.xml	21 Oct 2006 21:04:48 -0000	1.53
+++ home-router-howto.xml	8 Nov 2006 19:39:24 -0000	1.54
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.53 2006/10/21 21:04:48 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.54 2006/11/08 19:39:24 nightmorph Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.32</version>
-<date>2006-10-21</date>
+<version>1.33</version>
+<date>2006-11-08</date>
 
 <chapter>
 <title>Introduction</title>
@@ -1002,11 +1002,11 @@
 </pre>
 
 <p>
-This will affect all new connections, so just refresh the website you're 
-having problems with in order to test.  In case it helps, the standard MTU 
-value for 100mbit ethernet connections is <c>1500</c> while for PPPoE 
-connections it is <c>1492</c>.  For more info, you should read Chapter 15 
-of the <uri link="http://lartc.org/howto/">Linux Advanced Routing &amp; 
+This will affect all new connections, so just refresh the website you're having
+problems with in order to test. In case it helps, the standard MTU value for
+100mbit ethernet connections is <c>1500</c>; this value also applies to PPPoA.
+For PPPoE connections it is <c>1492</c>. For more info, you should read Chapter
+15 of the <uri link="http://lartc.org/howto/">Linux Advanced Routing &amp;
 Traffic Control HOWTO</uri>.
 </p>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2007-01-28 22:36 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2007-01-28 22:36 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      07/01/28 22:36:37

  Modified:             home-router-howto.xml
  Log:
  add samba port forwarding as suggested by Daniel Meissner

Revision  Changes    Path
1.55                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.55&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.55&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.54&r2=1.55

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- home-router-howto.xml	8 Nov 2006 19:39:24 -0000	1.54
+++ home-router-howto.xml	28 Jan 2007 22:36:37 -0000	1.55
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.54 2006/11/08 19:39:24 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.55 2007/01/28 22:36:37 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.33</version>
-<date>2006-11-08</date>
+<version>1.34</version>
+<date>2007-01-28</date>
 
 <chapter>
 <title>Introduction</title>
@@ -528,6 +528,13 @@
 # <i>iptables -t nat -I PREROUTING -p tcp --dport 5901 -i ${WAN} -j DNAT --to 192.168.0.3:5900</i>
 <comment>If you want to VNC in to 192.168.0.3, then just add ':1' to the router's hostname</comment>
 
+<comment>SAMBA forwarding to an internal host (excess ports to cover Windows)</comment>
+# <i>iptables -t nat -I PREROUTING -p tcp --dport 135 -i ${WAN} -j DNAT --to 192.168.0.2</i>
+# <i>iptables -t nat -I PREROUTING -p tcp --dport 139 -i ${WAN} -j DNAT --to 192.168.0.2</i>
+# <i>iptables -t nat -I PREROUTING -p tcp --dport 445 -i ${WAN} -j DNAT --to 192.168.0.2</i>
+# <i>iptables -t nat -I PREROUTING -p udp --dport 137:138 -i ${WAN} -j DNAT --to 192.168.0.2</i>
+# <i>iptables -t nat -I PREROUTING -p udp --dport 445 -i ${WAN} -j DNAT --to 192.168.0.2</i>
+
 <comment>Bittorrent forwarding</comment>
 # <i>iptables -t nat -A PREROUTING -p tcp --dport 6881:6889 -i ${WAN} -j DNAT --to 192.168.0.2</i>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2007-04-03 23:06 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2007-04-03 23:06 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      07/04/03 23:06:21

  Modified:             home-router-howto.xml
  Log:
  finish converting to netqmail

Revision  Changes    Path
1.57                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.57&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.57&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.56&r2=1.57

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- home-router-howto.xml	7 Mar 2007 21:30:18 -0000	1.56
+++ home-router-howto.xml	3 Apr 2007 23:06:21 -0000	1.57
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.56 2007/03/07 21:30:18 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.57 2007/04/03 23:06:21 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.35</version>
-<date>2007-03-07</date>
+<version>1.36</version>
+<date>2007-04-03</date>
 
 <chapter>
 <title>Introduction</title>
@@ -799,24 +799,25 @@
 # <i>iptables -I INPUT -p tcp --dport smtp -i ! ${LAN} -j REJECT</i>
 # <i>ln -s /var/qmail/supervise/qmail-send /service/qmail-send</i>
 # <i>ln -s /var/qmail/supervise/qmail-smtpd /service/qmail-smtpd</i>
-<!--
 # <i>cd /etc/tcprules.d</i>
 # <i>nano tcp.qmail-smtp</i>
--->
+<!--
 # <i>cd /etc</i>
 # <i>nano tcp.smtp</i>
+-->
 <comment>Add an entry like so to the allow section:</comment>
 192.168.0.:allow,RELAYCLIENT=""
 <!--
 # <i>tcprules tcp.qmail-qmtp.cdb rules.tmp &lt; tcp.qmail-smtp</i>
--->
 # <i>tcprules tcp.smtp.cdb rules.tmp &lt; tcp.smtp</i>
+-->
+# <i>make</i>
 # <i>rc-update add svscan default</i>
 # <i>/etc/init.d/svscan start</i>
 </pre>
 
 <p>
-I'm a huge fan of netqmail, but you're free to use a different mta :).  When you
+I'm a huge fan of qmail, but you're free to use a different mta :).  When you
 setup e-mail on the hosts in your network, tell them that their SMTP server is
 192.168.0.1 and everything should be peachy.  You might want to visit the <uri
 link="http://netqmail.org/">netqmail homepage</uri> for more documentation.



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2007-04-07  2:16 vapier
  0 siblings, 0 replies; 32+ messages in thread
From: vapier @ 2007-04-07  2:16 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      07/04/07 02:16:43

  Modified:             home-router-howto.xml
  Log:
  transition from rp-pppoe/adsl to ppp/pppoe for adsl/pppoe users

Revision  Changes    Path
1.58                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.58&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.58&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.57&r2=1.58

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- home-router-howto.xml	3 Apr 2007 23:06:21 -0000	1.57
+++ home-router-howto.xml	7 Apr 2007 02:16:43 -0000	1.58
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.57 2007/04/03 23:06:21 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.58 2007/04/07 02:16:43 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.36</version>
-<date>2007-04-03</date>
+<version>1.37</version>
+<date>2007-04-06</date>
 
 <chapter>
 <title>Introduction</title>
@@ -191,32 +191,39 @@
 <body>
 
 <p>
-All the fancy PPPoE software has been bundled up into one little nice package
-nowadays called <uri link="http://www.roaringpenguin.com/">Roaring
-Penguin</uri>.  Simply <c>emerge rp-pppoe</c> and you'll be on your way.
-Remember how I said you'll need username/password information?  Well I wasn't
-lying so I hope you have it now!  Load up <path>/etc/ppp/pppoe.conf</path> in
-your favorite editor and set it up.
+All the fancy PPPoE software that used to be provided by rp-pppoe 
+(<uri link="http://www.roaringpenguin.com/">Roaring Penguin</uri>) has been 
+integrated into the <uri link="http://samba.org/ppp/">standard PPP 
+package</uri>.  Simply <c>emerge ppp</c> and you'll be on your way.  Remember 
+how I said you'll need username/password information?  Well I wasn't lying so 
+I hope you have it now!  Load up <path>/etc/conf.d/net</path> in your favorite 
+editor and set it up.
 </p>
 
 <note>
 In order for the following net settings to work, you must have 
-baselayout-1.11.14 or later installed on your system.
+baselayout-1.12.9 or later installed on your system.
 </note>
 
 <pre caption="Setting up eth1">
-<comment>(Replace 'vla9h924' with your username and 'password' with your password)</comment>
+<comment>(Replace 'vla9h924' with your username and 'boogie' with your password)</comment>
 
-# <i>nano /etc/ppp/pap-secrets</i>
-<comment># client    server  secret</comment>
-"vla9h924" * "password"
 # <i>nano /etc/conf.d/net</i>
-<comment>Tell baselayout to use adsl for your eth1:</comment>
-config_eth1=( "adsl" )
-user_eth1=( "vla9h924" )
-# <i>ln -s net.lo /etc/init.d/net.eth1</i>
-# <i>rc-update add net.eth1 default</i>
-# <i>/etc/init.d/net.eth1 start</i>
+<comment>Tell baselayout to use adsl over eth1 for ppp0:</comment>
+config_ppp0=( "ppp" )
+link_ppp0="eth1"
+plugins_ppp0=( "pppoe" )
+pppd_ppp0=(
+	"defaultroute"
+	"usepeerdns"
+	<comment>There may be other settings you want, see /etc/conf.d/net.example</comment>
+)
+username_ppp0="vla9h924"
+password_ppp0="boogie"
+
+# <i>ln -s net.lo /etc/init.d/net.ppp0</i>
+# <i>rc-update add net.ppp0 default</i>
+# <i>/etc/init.d/net.ppp0 start</i>
 </pre>
 
 <warn>
@@ -225,6 +232,17 @@
 examples that utilize 'eth1', substitute with 'ppp0'.
 </warn>
 
+<warn>
+Make sure you change the permissions of the /etc/conf.d/net file so that only 
+root can read/write it since you're sticking your username/password in it.
+</warn>
+
+<warn>
+For people transitioning from the <c>rp-pppoe</c> package, or for people who 
+hit weird connection resets, see the MTU section in the Troubleshooting 
+chapter.
+</warn>
+
 </body>
 </section>
 



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2007-07-27 17:50 Josh Saddler
  0 siblings, 0 replies; 32+ messages in thread
From: Josh Saddler @ 2007-07-27 17:50 UTC (permalink / raw
  To: gentoo-doc-cvs

nightmorph    07/07/27 17:50:59

  Modified:             home-router-howto.xml
  Log:
  no more rp-pppoe, use ppp instead

Revision  Changes    Path
1.59                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.59&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.59&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.58&r2=1.59

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- home-router-howto.xml	7 Apr 2007 02:16:43 -0000	1.58
+++ home-router-howto.xml	27 Jul 2007 17:50:59 -0000	1.59
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.58 2007/04/07 02:16:43 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.59 2007/07/27 17:50:59 nightmorph Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.37</version>
-<date>2007-04-06</date>
+<version>1.38</version>
+<date>2007-07-27</date>
 
 <chapter>
 <title>Introduction</title>
@@ -36,7 +36,7 @@
 <p>
 This guide will show you how to setup Network Address Translation (NAT) on the
 router (kernel and iptables), add and configure common services (Domain Name
-System (DNS) via dnsmasq, dhcp via dhcpcd, ADSL via rp-pppoe), and conclude
+System (DNS) via dnsmasq, dhcp via dhcpcd, ADSL via ppp), and conclude
 with more elaborate and fun things that can be done (port forwarding, traffic
 shaping, proxies/caching, etc...).
 </p>



-- 
gentoo-doc-cvs@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2008-05-20 18:57 Sven Vermeulen
  0 siblings, 0 replies; 32+ messages in thread
From: Sven Vermeulen @ 2008-05-20 18:57 UTC (permalink / raw
  To: gentoo-doc-cvs

swift       08/05/20 18:57:45

  Modified:             home-router-howto.xml
  Log:
  Coding style

Revision  Changes    Path
1.60                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.60&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.60&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.59&r2=1.60

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- home-router-howto.xml	27 Jul 2007 17:50:59 -0000	1.59
+++ home-router-howto.xml	20 May 2008 18:57:45 -0000	1.60
@@ -1,16 +1,16 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.59 2007/07/27 17:50:59 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.60 2008/05/20 18:57:45 swift Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
 
 <author title="Author">
-  <mail link="vapier@gentoo.org">Mike Frysinger</mail>
+ <mail link="vapier@gentoo.org">Mike Frysinger</mail>
 </author>
 
 <abstract>
-This document details how to turn an old Gentoo machine into a router 
+This document details how to turn an old Gentoo machine into a router
 for connecting your home network to the internet.
 </abstract>
 
@@ -27,8 +27,8 @@
 
 <p>
 Building your own router out of old spare parts has many advantages over buying
-a pre-made canned router by say Linksys.  The biggest one by far is control
-over the connection.  The other advantages are left up to your imagination;
+a pre-made canned router by say Linksys. The biggest one by far is control
+over the connection. The other advantages are left up to your imagination;
 just about anything can be done in this scenario, it's just a matter of needing
 it.
 </p>
@@ -42,10 +42,10 @@
 </p>
 
 <p>
-Before getting started, there's a few basic requirements you must meet.  First,
+Before getting started, there's a few basic requirements you must meet. First,
 you'll need a computer that has at least 2 Network Interface Cards (NICs) in
-it.  Next, you'll need the configuration settings for your internet connection
-(may include things like IP/DNS/Gateway/username/password).  Finally, you'll
+it. Next, you'll need the configuration settings for your internet connection
+(may include things like IP/DNS/Gateway/username/password). Finally, you'll
 need a bit of spare time and some Gentoo loving.
 </p>
 
@@ -64,7 +64,7 @@
 <impo>
 Due to security precautions, I would highly suggest you shut down any unneeded
 services on the router until we have a chance to get the firewall up and
-rolling.  To view the currently running services, just run <c>rc-status</c>.
+rolling. To view the currently running services, just run <c>rc-status</c>.
 </impo>
 
 </body>
@@ -77,91 +77,91 @@
 <body>
 
 <p>
-Your kernel needs to have the drivers running for both your NICs.  To see if
-your cards are already setup, just run <c>ifconfig</c>.  Your output may differ
-slightly from the following, that's fine.  What matters is that the interface
+Your kernel needs to have the drivers running for both your NICs. To see if
+your cards are already setup, just run <c>ifconfig</c>. Your output may differ
+slightly from the following, that's fine. What matters is that the interface
 shows up at all.
 </p>
 
 <pre caption="Checking NICs">
 # <i>ifconfig -a</i>
-eth0      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B8
-          BROADCAST MULTICAST  MTU:1500  Metric:1
-          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000 
-          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
-          Interrupt:11 Base address:0x9800 
-
-eth1      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B9
-          BROADCAST MULTICAST  MTU:1500  Metric:1
-          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
-          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000 
-          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
-          Interrupt:10 Base address:0x9400 
+eth0   Link encap:Ethernet HWaddr 00:60:F5:07:07:B8
+     BROADCAST MULTICAST MTU:1500 Metric:1
+     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+     collisions:0 txqueuelen:1000
+     RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
+     Interrupt:11 Base address:0x9800
+
+eth1   Link encap:Ethernet HWaddr 00:60:F5:07:07:B9
+     BROADCAST MULTICAST MTU:1500 Metric:1
+     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+     collisions:0 txqueuelen:1000
+     RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
+     Interrupt:10 Base address:0x9400
 </pre>
 
 <p>
 If you do not see your two cards showing up and you're not sure what kind of
-cards you have, try running <c>lspci | grep Ethernet</c>.  You can get that
-from <c>emerge pciutils</c>.  Once you have this information, go into your
+cards you have, try running <c>lspci | grep Ethernet</c>. You can get that
+from <c>emerge pciutils</c>. Once you have this information, go into your
 kernel and add support for the correct drivers.
 </p>
 
 <p>
 The next thing you'll need is support for iptables and NAT (and packet shaping
-if you want).  The following list is split up into always required (*), 
-required only for adsl via PPPoE (a), suggested for everyone (x), and only 
-for shaper (s) features.  It does not matter whether you build the features 
-into the kernel or as a module so long as when the feature is needed, the 
-correct module(s) are loaded (module loading is left to the reader as a fun 
+if you want). The following list is split up into always required (*),
+required only for adsl via PPPoE (a), suggested for everyone (x), and only
+for shaper (s) features. It does not matter whether you build the features
+into the kernel or as a module so long as when the feature is needed, the
+correct module(s) are loaded (module loading is left to the reader as a fun
 exercise however).
 </p>
 
 <pre caption="Network Options">
-Networking options  ---&gt;
-   [*] TCP/IP networking
-      [*] IP: advanced router
-   [*] Network packet filtering (replaces ipchains)
+Networking options ---&gt;
+  [*] TCP/IP networking
+   [*] IP: advanced router
+  [*] Network packet filtering (replaces ipchains)
 <comment>If you use 2.4.x, you have to enable the following for DHCP:</comment>
-   [*] Socket Filtering
+  [*] Socket Filtering
 
-   IP: Netfilter Configuration  ---&gt;
-      [*] Connection tracking (required for masq/NAT)
-         [x] FTP protocol support
-         [x] IRC protocol support
-      [*] IP tables support (required for filtering/masq/NAT)
-         [*] IP range match support
-         [x] MAC address match support
-         [*] Multiple port match support
-         [*] Packet filtering
-            [*] REJECT target support
-            [x] REDIRECT target support
-         [*] Full NAT
-            [*] MASQUERADE target support
-         [s] Packet mangling
-            [s] MARK target support
-         [x] LOG target support
-
-   QoS and/or fair queueing  ---&gt;
-      [s] QoS and/or fair queueing
-         [s] HTB packet scheduler
-         [s] Ingress Qdisc
-
-   [a] PPP (point-to-point protocol) support
-      [a] PPP filtering
-      [a] PPP support for async serial ports
-      [a] PPP support for sync tty ports
-      [a] PPP Deflate compression
-      [a] PPP BSD-Compress compression
-      [a] PPP over Ethernet
+  IP: Netfilter Configuration ---&gt;
+   [*] Connection tracking (required for masq/NAT)
+     [x] FTP protocol support
+     [x] IRC protocol support
+   [*] IP tables support (required for filtering/masq/NAT)
+     [*] IP range match support
+     [x] MAC address match support
+     [*] Multiple port match support
+     [*] Packet filtering
+      [*] REJECT target support
+      [x] REDIRECT target support
+     [*] Full NAT
+      [*] MASQUERADE target support
+     [s] Packet mangling
+      [s] MARK target support
+     [x] LOG target support
+
+  QoS and/or fair queueing ---&gt;
+   [s] QoS and/or fair queueing
+     [s] HTB packet scheduler
+     [s] Ingress Qdisc
+
+  [a] PPP (point-to-point protocol) support
+   [a] PPP filtering
+   [a] PPP support for async serial ports
+   [a] PPP support for sync tty ports
+   [a] PPP Deflate compression
+   [a] PPP BSD-Compress compression
+   [a] PPP over Ethernet
 </pre>
 
 <note>
 Some things may be slightly different in a 2.4 vs 2.6 kernel, but you should be
-able to figure it out :).  Even among 2.6 kernels, these options have a
-tendency to move around.  Good luck!
+able to figure it out :). Even among 2.6 kernels, these options have a
+tendency to move around. Good luck!
 </note>
 
 </body>
@@ -177,10 +177,10 @@
 
 <p>
 There are many ways to connect to the internet so I'll just cover the ones I'm
-familiar with.  That leaves us with ADSL (PPPoE) and cable modems
-(static/dynamic).  If there are other methods out there, feel free to write up
-a little blurb and e-mail me.  Feel free to skip any of the following sections
-in this chapter that don't apply to you.  This chapter is just about getting
+familiar with. That leaves us with ADSL (PPPoE) and cable modems
+(static/dynamic). If there are other methods out there, feel free to write up
+a little blurb and e-mail me. Feel free to skip any of the following sections
+in this chapter that don't apply to you. This chapter is just about getting
 the router connected to the internet via eth1.
 </p>
 
@@ -191,17 +191,17 @@
 <body>
 
 <p>
-All the fancy PPPoE software that used to be provided by rp-pppoe 
-(<uri link="http://www.roaringpenguin.com/">Roaring Penguin</uri>) has been 
-integrated into the <uri link="http://samba.org/ppp/">standard PPP 
-package</uri>.  Simply <c>emerge ppp</c> and you'll be on your way.  Remember 
-how I said you'll need username/password information?  Well I wasn't lying so 
-I hope you have it now!  Load up <path>/etc/conf.d/net</path> in your favorite 
+All the fancy PPPoE software that used to be provided by rp-pppoe
+(<uri link="http://www.roaringpenguin.com/">Roaring Penguin</uri>) has been
+integrated into the <uri link="http://samba.org/ppp/">standard PPP
+package</uri>. Simply <c>emerge ppp</c> and you'll be on your way. Remember
+how I said you'll need username/password information? Well I wasn't lying so
+I hope you have it now! Load up <path>/etc/conf.d/net</path> in your favorite
 editor and set it up.
 </p>
 
 <note>
-In order for the following net settings to work, you must have 
+In order for the following net settings to work, you must have
 baselayout-1.12.9 or later installed on your system.
 </note>
 
@@ -214,9 +214,9 @@
 link_ppp0="eth1"
 plugins_ppp0=( "pppoe" )
 pppd_ppp0=(
-	"defaultroute"
-	"usepeerdns"
-	<comment>There may be other settings you want, see /etc/conf.d/net.example</comment>
+ "defaultroute"
+ "usepeerdns"
+ <comment>There may be other settings you want, see /etc/conf.d/net.example</comment>
 )
 username_ppp0="vla9h924"
 password_ppp0="boogie"
@@ -227,19 +227,19 @@
 </pre>
 
 <warn>
-When the DSL interface comes up, it will create ppp0.  Although your NIC is 
-called eth1, the IP is actually bound to ppp0.  From now on, when you see 
+When the DSL interface comes up, it will create ppp0. Although your NIC is
+called eth1, the IP is actually bound to ppp0. From now on, when you see
 examples that utilize 'eth1', substitute with 'ppp0'.
 </warn>
 
 <warn>
-Make sure you change the permissions of the /etc/conf.d/net file so that only 
+Make sure you change the permissions of the /etc/conf.d/net file so that only
 root can read/write it since you're sticking your username/password in it.
 </warn>
 
 <warn>
-For people transitioning from the <c>rp-pppoe</c> package, or for people who 
-hit weird connection resets, see the MTU section in the Troubleshooting 
+For people transitioning from the <c>rp-pppoe</c> package, or for people who
+hit weird connection resets, see the MTU section in the Troubleshooting
 chapter.
 </warn>
 
@@ -251,8 +251,8 @@
 <body>
 
 <p>
-If you have a static IP then you will need a few more details than if 
-you have a dynamic IP.  For static users, you will need your IP, 
+If you have a static IP then you will need a few more details than if
+you have a dynamic IP. For static users, you will need your IP,
 gateway, and DNS servers.
 </p>
 
@@ -316,28 +316,28 @@
 
 <p>
 I bet it'd be nice if everyone else in your house could just plug their
-computers into the network and things would just work.  No need to remember
+computers into the network and things would just work. No need to remember
 mind-numbing details or make them stare at confusing configuration screens!
-Life would be grand eh?  Introducing the Dynamic Host Configuration Protocol
+Life would be grand eh? Introducing the Dynamic Host Configuration Protocol
 (DHCP) and why you should care.
 </p>
 
 <p>
-DHCP is exactly what its name implies.  It's a protocol that allows you 
-to dynamically configure other hosts automatically.  You run a DHCP server on
+DHCP is exactly what its name implies. It's a protocol that allows you
+to dynamically configure other hosts automatically. You run a DHCP server on
 the router, give it all the information about your network (valid IPs,
 DNS servers, gateways, etc...), and then when the other hosts start up, they
-run a DHCP client to automatically configure themselves.  No fuss, no muss!
+run a DHCP client to automatically configure themselves. No fuss, no muss!
 For more information about DHCP, you can always visit <uri
 link="http://en.wikipedia.org/wiki/DHCP">Wikipedia</uri>.
 </p>
 
 <p>
 We'll use a package called dnsmasq which provides both DHCP and DNS services.
-For now lets just focus on the DHCP aspect.  Note that if you want to run a
+For now lets just focus on the DHCP aspect. Note that if you want to run a
 different DHCP server, you can find another example in the Fun Things chapter.
-Also, if you wish to tinker with the DHCP server settings, just read the 
-comments in <path>/etc/dnsmasq.conf</path>.  All the defaults should work fine 
+Also, if you wish to tinker with the DHCP server settings, just read the
+comments in <path>/etc/dnsmasq.conf</path>. All the defaults should work fine
 though.
 </p>
 
@@ -354,12 +354,12 @@
 </pre>
 
 <p>
-Now your little router is a bona-fide DHCP server!  Plugin those computers and
-watch them work!  With Windows systems you should go into the TCP/IP Properties
+Now your little router is a bona-fide DHCP server! Plugin those computers and
+watch them work! With Windows systems you should go into the TCP/IP Properties
 and select the 'Obtain an IP address automatically' and 'Obtain DNS server
-address automatically' options.  Sometimes the changes aren't instantaneous, so
+address automatically' options. Sometimes the changes aren't instantaneous, so
 you may have to open a command prompt and run <c>ipconfig /release</c> and
-<c>ipconfig /renew</c>.  But enough about Windows, let's get back to our
+<c>ipconfig /renew</c>. But enough about Windows, let's get back to our
 favorite penguin.
 </p>
 
@@ -372,25 +372,25 @@
 
 <p>
 When people want to visit a place on the internet, they remember names, not a
-string of funky numbers.  After all, what's easier to remember, ebay.com or
-66.135.192.87?  This is where the DNS steps in.  DNS servers run all over the
+string of funky numbers. After all, what's easier to remember, ebay.com or
+66.135.192.87? This is where the DNS steps in. DNS servers run all over the
 internet, and whenever someone wants to visit 'ebay.com', these servers turn
 'ebay.com' (what we understand) into '66.135.192.87' (what our computers
-understand).  For more information about DNS, you can always visit <uri
+understand). For more information about DNS, you can always visit <uri
 link="http://en.wikipedia.org/wiki/DNS">Wikipedia</uri>.
 </p>
 
 <p>
 Since we're using dnsmasq for our DHCP server, and it includes a DNS server,
-you've got nothing left to do here!  Your little router is already providing
-DNS to its DHCP clients.  Bet you wish everything was this easy ;).
+you've got nothing left to do here! Your little router is already providing
+DNS to its DHCP clients. Bet you wish everything was this easy ;).
 </p>
 
 <p>
-You're welcome to choose other DNS servers if you're more comfortable with 
-them, but the reason dnsmasq is great is because it was designed to do exactly 
-what we want and nothing more.  It's a little DNS caching/forwarding server for 
-local networks.  We're not looking to provide DNS for our own domain here, just 
+You're welcome to choose other DNS servers if you're more comfortable with
+them, but the reason dnsmasq is great is because it was designed to do exactly
+what we want and nothing more. It's a little DNS caching/forwarding server for
+local networks. We're not looking to provide DNS for our own domain here, just
 offer simple DNS services to everyone else on our LAN.
 </p>
 
@@ -409,17 +409,17 @@
 </p>
 
 <p>
-This is where Network Address Translation (NAT) steps in.  NAT is a way of 
-connecting multiple computers in a private LAN to the internet when you have a 
-smaller number of public IP addresses available to you.  Typically you are given 
+This is where Network Address Translation (NAT) steps in. NAT is a way of
+connecting multiple computers in a private LAN to the internet when you have a
+smaller number of public IP addresses available to you. Typically you are given
 1 IP by your ISP, but you want to let your whole house connect to the internet.
-NAT is the magic that makes this possible.  For more information about NAT, you 
+NAT is the magic that makes this possible. For more information about NAT, you
 can always visit <uri link="http://en.wikipedia.org/wiki/NAT">Wikipedia</uri>.
 </p>
 
 <note>
-Before we get started, make sure you have iptables on your system.  Although it
-is automatically installed on most systems, you may not have it.  If you don't,
+Before we get started, make sure you have iptables on your system. Although it
+is automatically installed on most systems, you may not have it. If you don't,
 just run <c>emerge iptables</c>.
 </note>
 
@@ -473,13 +473,13 @@
 
 <p>
 Once you've typed out all of that, the rest of your network should now be able
-to use the internet as if they were directly connected themselves.  
+to use the internet as if they were directly connected themselves.
 </p>
 
 <p>
 The ip_dynaddr option is useful for dial on demand systems or when your ISP
-gives out dynamic addresses.  This works around the problem where a connection
-is attempted before the internet interface is fully setup.  Really this just
+gives out dynamic addresses. This works around the problem where a connection
+is attempted before the internet interface is fully setup. Really this just
 provides for a smoother network experience for users behind your router.
 </p>
 
@@ -495,8 +495,8 @@
 <body>
 
 <p>
-Believe it or not, you're done :).  From here on out, I'll cover a bunch of
-common topics that may interest you.  Everything in this chapter is completely
+Believe it or not, you're done :). From here on out, I'll cover a bunch of
+common topics that may interest you. Everything in this chapter is completely
 optional.
 </p>
 
@@ -509,10 +509,10 @@
 
 <p>
 Sometimes you would like to be able to host services on a computer behind the
-router, or just to make your life easier when connecting remotely.  Perhaps you
+router, or just to make your life easier when connecting remotely. Perhaps you
 want to run a FTP, HTTP, SSH, or VNC server on one or more machines behind your
-router and be able to connect to them all.  The only caveat is that you can
-only have one service/machine combo per port.  For example, there is no
+router and be able to connect to them all. The only caveat is that you can
+only have one service/machine combo per port. For example, there is no
 practical way to setup three FTP servers behind your router and then try to
 connect to them all through port 21; only one can be on port 21 while the
 others would have to be on say port 123 and port 567.
@@ -521,9 +521,9 @@
 <p>
 All the port forwarding rules are of the form <c>iptables -t nat -A PREROUTING
 [-p protocol] --dport [external port on router] -i ${WAN} -j DNAT --to [ip/port
-to forward to]</c>.  Unfortunately, iptables does not accept hostnames when port
-forwarding.  If you are forwarding an external port to the same port on the 
-internal machine, you can omit the destination port.  See the iptables(8) man 
+to forward to]</c>. Unfortunately, iptables does not accept hostnames when port
+forwarding. If you are forwarding an external port to the same port on the
+internal machine, you can omit the destination port. See the iptables(8) man
 page for more information.
 </p>
 
@@ -585,9 +585,9 @@
 <body>
 
 <p>
-Internet Relay Chat utilizes the ident service pretty heavily.  Now that the
+Internet Relay Chat utilizes the ident service pretty heavily. Now that the
 IRC clients are behind the router, we need a way to host ident for both the
-router and the clients.  One such server has been created called
+router and the clients. One such server has been created called
 <c>midentd</c>.
 </p>
 
@@ -598,7 +598,7 @@
 </pre>
 
 <p>
-There are a few other ident servers in portage.  Depending on your needs, I
+There are a few other ident servers in portage. Depending on your needs, I
 would recommend checking out <c>oidentd</c> and <c>fakeidentd</c>.
 </p>
 
@@ -610,43 +610,43 @@
 <title>Traffic Shaping</title>
 <body>
 <p>
-This is an attempt to simply and Gentooify the <uri link="http://www.tldp.org/HOWTO/ADSL-Bandwidth-Management-HOWTO/">ADSL Bandwidth Management HOWTO</uri> 
-found over at the TLDP.  Feel free to refer to the original document 
+This is an attempt to simply and Gentooify the <uri link="http://www.tldp.org/HOWTO/ADSL-Bandwidth-Management-HOWTO/">ADSL Bandwidth Management HOWTO</uri>
+found over at the TLDP. Feel free to refer to the original document
 for more details.
 </p>
 
 <p>
-Here we will be setting up what some people refer to as a "Packet Shaper", 
-<uri link="http://en.wikipedia.org/wiki/Traffic_shaping">"Traffic Shaping"</uri>, 
-or <uri link="http://en.wikipedia.org/wiki/QoS">"Quality of Service"</uri>.  
-Simply put, we want to setup rules on our router that will slow down 
-certain activities (like sending large e-mails or downloading from P2P 
-networks) while keeping other activities (like browsing the web or playing 
-online video games) reasonably fast.  A 30 second difference in a video 
-game is a lot worse than a 30 second difference in downloading large 
+Here we will be setting up what some people refer to as a "Packet Shaper",
+<uri link="http://en.wikipedia.org/wiki/Traffic_shaping">"Traffic Shaping"</uri>,
+or <uri link="http://en.wikipedia.org/wiki/QoS">"Quality of Service"</uri>.
+Simply put, we want to setup rules on our router that will slow down
+certain activities (like sending large e-mails or downloading from P2P
+networks) while keeping other activities (like browsing the web or playing
+online video games) reasonably fast. A 30 second difference in a video
+game is a lot worse than a 30 second difference in downloading large
 files :).
 </p>
 
 <p>
-The first thing is to make sure your kernel has all the features added to 
-it.  See the chapter on <uri link="#doc_chap2">Kernel setup</uri> for more 
-information.  Next, you will need to <c>emerge iptables iputils</c> so that 
-you will have access to the <c>iptables</c>, <c>ip</c>, and <c>tc</c> 
+The first thing is to make sure your kernel has all the features added to
+it. See the chapter on <uri link="#doc_chap2">Kernel setup</uri> for more
+information. Next, you will need to <c>emerge iptables iputils</c> so that
+you will have access to the <c>iptables</c>, <c>ip</c>, and <c>tc</c>
 commands.
 </p>
 
 <p>
-Before we jump into the commands, let's cover a little of the theory.  The 
-way this whole system works is to classify common network streams and then 
-to prioritize them.  You use iptables to classify network streams, iputils 
-to define the different priority levels, and the kernel to adjust speeds.  
-Just remember that although you can control outbound traffic pretty tightly 
-(from the LAN to the WAN), your ability to control inbound traffic (from 
-the WAN to the LAN) is somewhat limited.  Just remember that the following 
-examples are to get your feet wet; if you want more then I'd suggest 
-reading up on the subject.  In this example, we will be using the 
-<uri link="http://luxik.cdi.cz/~devik/qos/htb/">Hierarchical Token Buckets (HTB)</uri> 
-packet scheduling algorithm.  Still with me?  Great, let's start shaping :).
+Before we jump into the commands, let's cover a little of the theory. The
+way this whole system works is to classify common network streams and then
+to prioritize them. You use iptables to classify network streams, iputils
+to define the different priority levels, and the kernel to adjust speeds.
+Just remember that although you can control outbound traffic pretty tightly
+(from the LAN to the WAN), your ability to control inbound traffic (from
+the WAN to the LAN) is somewhat limited. Just remember that the following
+examples are to get your feet wet; if you want more then I'd suggest
+reading up on the subject. In this example, we will be using the
+<uri link="http://luxik.cdi.cz/~devik/qos/htb/">Hierarchical Token Buckets (HTB)</uri>
+packet scheduling algorithm. Still with me? Great, let's start shaping :).
 </p>
 
 <pre caption="Setup">
@@ -654,20 +654,20 @@
 RATE_OUT=100 <comment>Available outbound bandwidth (in kilobits [kb])</comment>
 RATE_IN=1400 <comment>Available inbound bandwidth (in kb)</comment>
 
-<comment>Here we initialize the priority system.  The 45 is used to set the default classification level.</comment>
+<comment>Here we initialize the priority system. The 45 is used to set the default classification level.</comment>
 ip link set dev ${DEV} qlen 30
 tc qdisc add dev ${DEV} root handle 1: htb default 45
 tc class add dev ${DEV} parent 1: classid 1:1 htb rate ${RATE_OUT}kbit
 </pre>
 
 <p>
-Here we initialized the system which will be used to prioritize all of 
-our network traffic.  We created our queue, told it to use the HTB 
-algorithm, and set the default classification level to '45'.  The 
-default is completely arbitrary, as are the levels we choose from 
-here on out.  The only thing that matters is how the levels compare 
-relatively; a level '10' packet will be given preference over a 
-level '45' packet.  Let's move on to declaring different levels.
+Here we initialized the system which will be used to prioritize all of
+our network traffic. We created our queue, told it to use the HTB
+algorithm, and set the default classification level to '45'. The
+default is completely arbitrary, as are the levels we choose from
+here on out. The only thing that matters is how the levels compare
+relatively; a level '10' packet will be given preference over a
+level '45' packet. Let's move on to declaring different levels.
 </p>
 
 <pre caption="Declaring levels">
@@ -690,14 +690,14 @@
 </p>
 
 <p>
-Many people run ntp clients on their computers.  Obviously, the more clients in
-the world, the larger the load the ntp servers need to shoulder.  In
+Many people run ntp clients on their computers. Obviously, the more clients in
+the world, the larger the load the ntp servers need to shoulder. In
 environments like home networks though, we can help keep the load down on
-public servers while still providing the proper time to all our computers.  As
+public servers while still providing the proper time to all our computers. As
 an added bonus, our private updates will be a lot faster for the clients too!
 All we have to do is run a ntp server on our router that synchronizes itself
 with the public internet servers while providing the time to the rest of the
-computers in the network.  To get started, simply <c>emerge ntp</c> on the
+computers in the network. To get started, simply <c>emerge ntp</c> on the
 router.
 </p>
 
@@ -722,12 +722,12 @@
 
 <note>
 You should make sure that you allow inbound and outbound communication on the
-ntp port (123/udp) when setting up the server.  The client just needs outbound
+ntp port (123/udp) when setting up the server. The client just needs outbound
 access on port 123 over udp.
 </note>
 
 <p>
-Now, on your clients, have them <c>emerge ntp</c> also.  However, we will just
+Now, on your clients, have them <c>emerge ntp</c> also. However, we will just
 run the ntp client so setup is a lot simpler.
 </p>
 
@@ -746,10 +746,10 @@
 <body>
 
 <p>
-For those who run multiple Gentoo boxes on the same lan, you often want to 
-keep from having every machine running <c>emerge sync</c> with remote 
-servers.  By setting up a local rsync, you save on both your bandwidth and 
-the Gentoo rsync servers' bandwidth.  It's pretty simple to do.
+For those who run multiple Gentoo boxes on the same lan, you often want to
+keep from having every machine running <c>emerge sync</c> with remote
+servers. By setting up a local rsync, you save on both your bandwidth and
+the Gentoo rsync servers' bandwidth. It's pretty simple to do.
 </p>
 
 <note>
@@ -758,10 +758,10 @@
 </note>
 
 <p>
-Since every Gentoo machine requires rsync, theres no need to emerge it.  Edit 
-the default <path>/etc/rsyncd.conf</path> config file, uncomment the 
-<c>[gentoo-portage]</c> section, and make sure you add an <c>address</c> 
-option.  All the other defaults should be fine.
+Since every Gentoo machine requires rsync, theres no need to emerge it. Edit
+the default <path>/etc/rsyncd.conf</path> config file, uncomment the
+<c>[gentoo-portage]</c> section, and make sure you add an <c>address</c>
+option. All the other defaults should be fine.
 </p>
 
 <pre caption="Rsync server config">
@@ -771,9 +771,9 @@
 address = 192.168.0.1
 
 [gentoo-portage]
-  path = /mnt/space/portage
-  comment = Gentoo Linux Portage tree
-  exclude = /distfiles /packages
+ path = /mnt/space/portage
+ comment = Gentoo Linux Portage tree
+ exclude = /distfiles /packages
 </pre>
 
 <p>
@@ -802,9 +802,9 @@
 
 <p>
 Sometimes it's nice to run your own Simple Mail Transfer Protocol (SMTP) server
-on the router.  You may have your own reason for wanting to do so, but I run it
+on the router. You may have your own reason for wanting to do so, but I run it
 so that the users see mail as being sent instantly and the work of
-retrying/routing is left up to the mail server.  Some ISPs also don't allow for
+retrying/routing is left up to the mail server. Some ISPs also don't allow for
 mail relaying for accounts that aren't part of their network (like Verizon).
 Also, you can easily throttle the delivery of mail so that large attachments
 won't seriously lag your connection for half an hour.
@@ -835,9 +835,9 @@
 </pre>
 
 <p>
-I'm a huge fan of qmail, but you're free to use a different mta :).  When you
+I'm a huge fan of qmail, but you're free to use a different mta :). When you
 setup e-mail on the hosts in your network, tell them that their SMTP server is
-192.168.0.1 and everything should be peachy.  You might want to visit the <uri
+192.168.0.1 and everything should be peachy. You might want to visit the <uri
 link="http://netqmail.org/">netqmail homepage</uri> for more documentation.
 </p>
 
@@ -849,9 +849,9 @@
 <title>E-mail Virus Scanning</title>
 <body>
 <p>
-If you'd like to provide e-mail virus scanning for your users, but 
-don't want to have to install a virus scanner on every single machine, 
-then <c>pop3vscan</c> may just be the thing for you; a transparent 
+If you'd like to provide e-mail virus scanning for your users, but
+don't want to have to install a virus scanner on every single machine,
+then <c>pop3vscan</c> may just be the thing for you; a transparent
 Post Office Protocol (POP) scanner.
 </p>
 
@@ -868,9 +868,9 @@
 <body>
 
 <p>
-Earlier we used dnsmasq to provide DHCP service to all our clients.  For most
-people with a simple small LAN, this is perfect.  But you may need something 
-with more features.  Thus we turn to a full-featured DHCP server as provided 
+Earlier we used dnsmasq to provide DHCP service to all our clients. For most
+people with a simple small LAN, this is perfect. But you may need something
+with more features. Thus we turn to a full-featured DHCP server as provided
 by the <uri link="http://www.isc.org/products/DHCP">ISC</uri> folks.
 </p>
 
@@ -881,13 +881,13 @@
 authoritative;
 ddns-update-style interim;
 subnet 192.168.0.0 netmask 255.255.255.0 {
-    range 192.168.0.100 192.168.0.250;
-    default-lease-time 259200;
-    max-lease-time 518400;
-    option subnet-mask 255.255.255.0;
-    option broadcast-address 192.168.0.255;
-    option routers 192.168.0.1;
-    option domain-name-servers 192.168.0.1;
+  range 192.168.0.100 192.168.0.250;
+  default-lease-time 259200;
+  max-lease-time 518400;
+  option subnet-mask 255.255.255.0;
+  option broadcast-address 192.168.0.255;
+  option routers 192.168.0.1;
+  option domain-name-servers 192.168.0.1;
 }
 # <i>nano /etc/conf.d/dhcpd</i>
 <comment>(Set IFACE="eth0")</comment>
@@ -896,9 +896,9 @@
 </pre>
 
 <p>
-This is the minimal setup required to replace the dnsmasq DHCP functionality 
-that we used earlier.  Speaking of which, you did remember to disable the DHCP 
-features in dnsmasq didn't you?  If not, you should do so now (just comment 
+This is the minimal setup required to replace the dnsmasq DHCP functionality
+that we used earlier. Speaking of which, you did remember to disable the DHCP
+features in dnsmasq didn't you? If not, you should do so now (just comment
 out the <c>dhcp-range</c> setting in <path>/etc/dnsmasq.conf</path> and restart
 the service).
 </p>
@@ -911,34 +911,34 @@
 <body>
 
 <p>
-Sometimes you have need of connecting the router to another LAN.  Maybe you 
-want to hook up a group of friends temporarily, or you're a neat freak and 
-want to section off different groups of computers, or you're just really 
-really bored.  Whatever the reasons, extending the router to other LAN 
-networks should be pretty straightforward.  In the following examples, I will 
-assume that this new network is connected via a third ethernet card, namely 
+Sometimes you have need of connecting the router to another LAN. Maybe you
+want to hook up a group of friends temporarily, or you're a neat freak and
+want to section off different groups of computers, or you're just really
+really bored. Whatever the reasons, extending the router to other LAN
+networks should be pretty straightforward. In the following examples, I will
+assume that this new network is connected via a third ethernet card, namely
 <c>eth2</c>.
 </p>
 
 <p>
-First you need to configure the interface.  Just take the instructions in the 
-<uri link="#doc_chap4_pre1">4.1 code listing</uri> and replace <c>eth0</c> 
+First you need to configure the interface. Just take the instructions in the
+<uri link="#doc_chap4_pre1">4.1 code listing</uri> and replace <c>eth0</c>
 with <c>eth2</c> and <c>192.168.0</c> with <c>192.168.1</c>.
 </p>
 
 <p>
-Then you need to tweak dnsmasq to service the new interface.  Just edit the 
-<path>/etc/conf.d/dnsmasq</path> file again and append <c>-i eth2</c> to 
-DNSMASQ_OPTS; using -i multiple times is OK.  Then edit 
-<path>/etc/dnsmasq.conf</path> and add another line like the dhcp-range line 
-in the <uri link="#doc_chap5_pre1">5.1 code listing</uri>, replacing 
-<c>192.168.0</c> with <c>192.168.1</c>.  Having multiple dhcp-range lines is 
+Then you need to tweak dnsmasq to service the new interface. Just edit the
+<path>/etc/conf.d/dnsmasq</path> file again and append <c>-i eth2</c> to
+DNSMASQ_OPTS; using -i multiple times is OK. Then edit
+<path>/etc/dnsmasq.conf</path> and add another line like the dhcp-range line
+in the <uri link="#doc_chap5_pre1">5.1 code listing</uri>, replacing
+<c>192.168.0</c> with <c>192.168.1</c>. Having multiple dhcp-range lines is
 OK too.
 </p>
 
 <p>
-Finally, see the rules in the <uri link="#doc_chap5_pre2">5.2 code 
-listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them.  You 
+Finally, see the rules in the <uri link="#doc_chap5_pre2">5.2 code
+listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them. You
 may want to create another variable, say <c>LAN2</c>, to make things easier.
 </p>
 
@@ -955,31 +955,31 @@
 <body>
 
 <p>
-If you're having trouble getting your computers to communicate, you may way to 
-try out the following tools (they can all be found in the <c>net-analyzer</c> 
+If you're having trouble getting your computers to communicate, you may way to
+try out the following tools (they can all be found in the <c>net-analyzer</c>
 portage category):
 </p>
 
 <table>
 <tr>
-  <th>Utility</th>
-  <th>Description</th>
+ <th>Utility</th>
+ <th>Description</th>
 </tr>
 <tr>
-  <ti>wireshark</ti>
-  <ti>GUI tool to view all raw network data according to filters</ti>
+ <ti>wireshark</ti>
+ <ti>GUI tool to view all raw network data according to filters</ti>
 </tr>
 <tr>
-  <ti>tcpdump</ti>
-  <ti>Console tool to dump all raw network data according to filters</ti>
+ <ti>tcpdump</ti>
+ <ti>Console tool to dump all raw network data according to filters</ti>
 </tr>
 <tr>
-  <ti>iptraf</ti>
-  <ti>ncurses based IP LAN monitor</ti>
+ <ti>iptraf</ti>
+ <ti>ncurses based IP LAN monitor</ti>
 </tr>
 <tr>
-  <ti>ettercap</ti>
-  <ti>ncurses based network monitor/control</ti>
+ <ti>ettercap</ti>
+ <ti>ncurses based network monitor/control</ti>
 </tr>
 </table>
 
@@ -991,22 +991,22 @@
 <body>
 
 <p>
-When starting the dhcp init.d script for the first time, it may fail to load 
+When starting the dhcp init.d script for the first time, it may fail to load
 but neglect to give you any useful info.
 </p>
 
 <pre caption="DHCP Failing Example">
 # <i>/etc/init.d/dhcp start</i>
- * Setting ownership on dhcp.leases ...          [ ok ]
- * Starting dhcpd ...                            [ !! ]
+ * Setting ownership on dhcp.leases ...     [ ok ]
+ * Starting dhcpd ...              [ !! ]
 </pre>
 
 <p>
-The trick is to know where dhcpd is sending its output.  Simply browse to
-<path>/var/log</path> and read the log files.  Since the exact log file depends
+The trick is to know where dhcpd is sending its output. Simply browse to
+<path>/var/log</path> and read the log files. Since the exact log file depends
 on the package you are using as a syslog, try running <c>grep -Rl dhcpd
-/var/log</c> to narrow down the possibilities.  Chances are you made a typo in
-your config file.  You could also try running <c>dhcpd -d -f</c> (short for
+/var/log</c> to narrow down the possibilities. Chances are you made a typo in
+your config file. You could also try running <c>dhcpd -d -f</c> (short for
 debug / foreground) and debug the error based upon the output.
 </p>
 
@@ -1019,7 +1019,7 @@
 
 <p>
 If you experience odd errors (such as not being able to access some webpages
-while others load fine), you may be having Path MTU Discovery trouble.  The
+while others load fine), you may be having Path MTU Discovery trouble. The
 quick way to test is to run this iptables command:
 </p>
 
@@ -1044,10 +1044,10 @@
 <body>
 
 <p>
-If (for whatever reason) you want to connect two machines directly together 
+If (for whatever reason) you want to connect two machines directly together
 without a hub or switch, a regular ethernet cable will likely not work, unless
 you have an Auto MDI/MDI-X (also known as "autosensing") capable network
-adapter.  You will need a different cable called a crossover cable.  This <uri
+adapter. You will need a different cable called a crossover cable. This <uri
 link="http://en.wikipedia.org/wiki/Ethernet_crossover_cable">Wikipedia</uri>
 page explains the low level details.
 </p>
@@ -1065,7 +1065,7 @@
 <p>
 I have no final notes other than if you experience any troubles with the guide,
 please contact <mail link="vapier@gentoo.org">me</mail> or file a bug with <uri
-link="http://bugs.gentoo.org/">Gentoo's Bugtracking Website</uri>.  If you have
+link="http://bugs.gentoo.org/">Gentoo's Bugtracking Website</uri>. If you have
 some interesting bits you think would enhance this guide, by all means send it
 my way for inclusion.
 </p>



-- 
gentoo-doc-cvs@lists.gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2008-05-20 19:09 Sven Vermeulen
  0 siblings, 0 replies; 32+ messages in thread
From: Sven Vermeulen @ 2008-05-20 19:09 UTC (permalink / raw
  To: gentoo-doc-cvs

swift       08/05/20 19:09:36

  Modified:             home-router-howto.xml
  Log:
  Coding style again (did a bit too much before)

Revision  Changes    Path
1.61                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.61&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.61&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.60&r2=1.61

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- home-router-howto.xml	20 May 2008 18:57:45 -0000	1.60
+++ home-router-howto.xml	20 May 2008 19:09:36 -0000	1.61
@@ -1,12 +1,12 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.60 2008/05/20 18:57:45 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.61 2008/05/20 19:09:36 swift Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
 
 <author title="Author">
- <mail link="vapier@gentoo.org">Mike Frysinger</mail>
+  <mail link="vapier@gentoo.org">Mike Frysinger</mail>
 </author>
 
 <abstract>
@@ -27,8 +27,8 @@
 
 <p>
 Building your own router out of old spare parts has many advantages over buying
-a pre-made canned router by say Linksys. The biggest one by far is control
-over the connection. The other advantages are left up to your imagination;
+a pre-made canned router by say Linksys.  The biggest one by far is control
+over the connection.  The other advantages are left up to your imagination;
 just about anything can be done in this scenario, it's just a matter of needing
 it.
 </p>
@@ -42,10 +42,10 @@
 </p>
 
 <p>
-Before getting started, there's a few basic requirements you must meet. First,
+Before getting started, there's a few basic requirements you must meet.  First,
 you'll need a computer that has at least 2 Network Interface Cards (NICs) in
-it. Next, you'll need the configuration settings for your internet connection
-(may include things like IP/DNS/Gateway/username/password). Finally, you'll
+it.  Next, you'll need the configuration settings for your internet connection
+(may include things like IP/DNS/Gateway/username/password).  Finally, you'll
 need a bit of spare time and some Gentoo loving.
 </p>
 
@@ -64,7 +64,7 @@
 <impo>
 Due to security precautions, I would highly suggest you shut down any unneeded
 services on the router until we have a chance to get the firewall up and
-rolling. To view the currently running services, just run <c>rc-status</c>.
+rolling.  To view the currently running services, just run <c>rc-status</c>.
 </impo>
 
 </body>
@@ -77,91 +77,91 @@
 <body>
 
 <p>
-Your kernel needs to have the drivers running for both your NICs. To see if
-your cards are already setup, just run <c>ifconfig</c>. Your output may differ
-slightly from the following, that's fine. What matters is that the interface
+Your kernel needs to have the drivers running for both your NICs.  To see if
+your cards are already setup, just run <c>ifconfig</c>.  Your output may differ
+slightly from the following, that's fine.  What matters is that the interface
 shows up at all.
 </p>
 
 <pre caption="Checking NICs">
 # <i>ifconfig -a</i>
-eth0   Link encap:Ethernet HWaddr 00:60:F5:07:07:B8
-     BROADCAST MULTICAST MTU:1500 Metric:1
-     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
-     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
-     collisions:0 txqueuelen:1000
-     RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
-     Interrupt:11 Base address:0x9800
-
-eth1   Link encap:Ethernet HWaddr 00:60:F5:07:07:B9
-     BROADCAST MULTICAST MTU:1500 Metric:1
-     RX packets:0 errors:0 dropped:0 overruns:0 frame:0
-     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
-     collisions:0 txqueuelen:1000
-     RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
-     Interrupt:10 Base address:0x9400
+eth0      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B8
+          BROADCAST MULTICAST  MTU:1500  Metric:1
+          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
+          Interrupt:11 Base address:0x9800
+
+eth1      Link encap:Ethernet  HWaddr 00:60:F5:07:07:B9
+          BROADCAST MULTICAST  MTU:1500  Metric:1
+          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+          collisions:0 txqueuelen:1000
+          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
+          Interrupt:10 Base address:0x9400
 </pre>
 
 <p>
 If you do not see your two cards showing up and you're not sure what kind of
-cards you have, try running <c>lspci | grep Ethernet</c>. You can get that
-from <c>emerge pciutils</c>. Once you have this information, go into your
+cards you have, try running <c>lspci | grep Ethernet</c>.  You can get that
+from <c>emerge pciutils</c>.  Once you have this information, go into your
 kernel and add support for the correct drivers.
 </p>
 
 <p>
 The next thing you'll need is support for iptables and NAT (and packet shaping
-if you want). The following list is split up into always required (*),
+if you want).  The following list is split up into always required (*),
 required only for adsl via PPPoE (a), suggested for everyone (x), and only
-for shaper (s) features. It does not matter whether you build the features
+for shaper (s) features.  It does not matter whether you build the features
 into the kernel or as a module so long as when the feature is needed, the
 correct module(s) are loaded (module loading is left to the reader as a fun
 exercise however).
 </p>
 
 <pre caption="Network Options">
-Networking options ---&gt;
-  [*] TCP/IP networking
-   [*] IP: advanced router
-  [*] Network packet filtering (replaces ipchains)
+Networking options  ---&gt;
+   [*] TCP/IP networking
+      [*] IP: advanced router
+   [*] Network packet filtering (replaces ipchains)
 <comment>If you use 2.4.x, you have to enable the following for DHCP:</comment>
-  [*] Socket Filtering
+   [*] Socket Filtering
 
-  IP: Netfilter Configuration ---&gt;
-   [*] Connection tracking (required for masq/NAT)
-     [x] FTP protocol support
-     [x] IRC protocol support
-   [*] IP tables support (required for filtering/masq/NAT)
-     [*] IP range match support
-     [x] MAC address match support
-     [*] Multiple port match support
-     [*] Packet filtering
-      [*] REJECT target support
-      [x] REDIRECT target support
-     [*] Full NAT
-      [*] MASQUERADE target support
-     [s] Packet mangling
-      [s] MARK target support
-     [x] LOG target support
-
-  QoS and/or fair queueing ---&gt;
-   [s] QoS and/or fair queueing
-     [s] HTB packet scheduler
-     [s] Ingress Qdisc
-
-  [a] PPP (point-to-point protocol) support
-   [a] PPP filtering
-   [a] PPP support for async serial ports
-   [a] PPP support for sync tty ports
-   [a] PPP Deflate compression
-   [a] PPP BSD-Compress compression
-   [a] PPP over Ethernet
+   IP: Netfilter Configuration  ---&gt;
+      [*] Connection tracking (required for masq/NAT)
+         [x] FTP protocol support
+         [x] IRC protocol support
+      [*] IP tables support (required for filtering/masq/NAT)
+         [*] IP range match support
+         [x] MAC address match support
+         [*] Multiple port match support
+         [*] Packet filtering
+            [*] REJECT target support
+            [x] REDIRECT target support
+         [*] Full NAT
+            [*] MASQUERADE target support
+         [s] Packet mangling
+            [s] MARK target support
+         [x] LOG target support
+
+   QoS and/or fair queueing  ---&gt;
+      [s] QoS and/or fair queueing
+         [s] HTB packet scheduler
+         [s] Ingress Qdisc
+
+   [a] PPP (point-to-point protocol) support
+      [a] PPP filtering
+      [a] PPP support for async serial ports
+      [a] PPP support for sync tty ports
+      [a] PPP Deflate compression
+      [a] PPP BSD-Compress compression
+      [a] PPP over Ethernet
 </pre>
 
 <note>
 Some things may be slightly different in a 2.4 vs 2.6 kernel, but you should be
-able to figure it out :). Even among 2.6 kernels, these options have a
-tendency to move around. Good luck!
+able to figure it out :).  Even among 2.6 kernels, these options have a
+tendency to move around.  Good luck!
 </note>
 
 </body>
@@ -177,10 +177,10 @@
 
 <p>
 There are many ways to connect to the internet so I'll just cover the ones I'm
-familiar with. That leaves us with ADSL (PPPoE) and cable modems
-(static/dynamic). If there are other methods out there, feel free to write up
-a little blurb and e-mail me. Feel free to skip any of the following sections
-in this chapter that don't apply to you. This chapter is just about getting
+familiar with.  That leaves us with ADSL (PPPoE) and cable modems
+(static/dynamic).  If there are other methods out there, feel free to write up
+a little blurb and e-mail me.  Feel free to skip any of the following sections
+in this chapter that don't apply to you.  This chapter is just about getting
 the router connected to the internet via eth1.
 </p>
 
@@ -194,9 +194,9 @@
 All the fancy PPPoE software that used to be provided by rp-pppoe
 (<uri link="http://www.roaringpenguin.com/">Roaring Penguin</uri>) has been
 integrated into the <uri link="http://samba.org/ppp/">standard PPP
-package</uri>. Simply <c>emerge ppp</c> and you'll be on your way. Remember
-how I said you'll need username/password information? Well I wasn't lying so
-I hope you have it now! Load up <path>/etc/conf.d/net</path> in your favorite
+package</uri>.  Simply <c>emerge ppp</c> and you'll be on your way.  Remember
+how I said you'll need username/password information?  Well I wasn't lying so
+I hope you have it now!  Load up <path>/etc/conf.d/net</path> in your favorite
 editor and set it up.
 </p>
 
@@ -214,9 +214,9 @@
 link_ppp0="eth1"
 plugins_ppp0=( "pppoe" )
 pppd_ppp0=(
- "defaultroute"
- "usepeerdns"
- <comment>There may be other settings you want, see /etc/conf.d/net.example</comment>
+  "defaultroute"
+  "usepeerdns"
+  <comment>There may be other settings you want, see /etc/conf.d/net.example</comment>
 )
 username_ppp0="vla9h924"
 password_ppp0="boogie"
@@ -227,8 +227,8 @@
 </pre>
 
 <warn>
-When the DSL interface comes up, it will create ppp0. Although your NIC is
-called eth1, the IP is actually bound to ppp0. From now on, when you see
+When the DSL interface comes up, it will create ppp0.  Although your NIC is
+called eth1, the IP is actually bound to ppp0.  From now on, when you see
 examples that utilize 'eth1', substitute with 'ppp0'.
 </warn>
 
@@ -252,7 +252,7 @@
 
 <p>
 If you have a static IP then you will need a few more details than if
-you have a dynamic IP. For static users, you will need your IP,
+you have a dynamic IP.  For static users, you will need your IP,
 gateway, and DNS servers.
 </p>
 
@@ -316,28 +316,28 @@
 
 <p>
 I bet it'd be nice if everyone else in your house could just plug their
-computers into the network and things would just work. No need to remember
+computers into the network and things would just work.  No need to remember
 mind-numbing details or make them stare at confusing configuration screens!
-Life would be grand eh? Introducing the Dynamic Host Configuration Protocol
+Life would be grand eh?  Introducing the Dynamic Host Configuration Protocol
 (DHCP) and why you should care.
 </p>
 
 <p>
-DHCP is exactly what its name implies. It's a protocol that allows you
-to dynamically configure other hosts automatically. You run a DHCP server on
+DHCP is exactly what its name implies.  It's a protocol that allows you
+to dynamically configure other hosts automatically.  You run a DHCP server on
 the router, give it all the information about your network (valid IPs,
 DNS servers, gateways, etc...), and then when the other hosts start up, they
-run a DHCP client to automatically configure themselves. No fuss, no muss!
+run a DHCP client to automatically configure themselves.  No fuss, no muss!
 For more information about DHCP, you can always visit <uri
 link="http://en.wikipedia.org/wiki/DHCP">Wikipedia</uri>.
 </p>
 
 <p>
 We'll use a package called dnsmasq which provides both DHCP and DNS services.
-For now lets just focus on the DHCP aspect. Note that if you want to run a
+For now lets just focus on the DHCP aspect.  Note that if you want to run a
 different DHCP server, you can find another example in the Fun Things chapter.
 Also, if you wish to tinker with the DHCP server settings, just read the
-comments in <path>/etc/dnsmasq.conf</path>. All the defaults should work fine
+comments in <path>/etc/dnsmasq.conf</path>.  All the defaults should work fine
 though.
 </p>
 
@@ -354,12 +354,12 @@
 </pre>
 
 <p>
-Now your little router is a bona-fide DHCP server! Plugin those computers and
-watch them work! With Windows systems you should go into the TCP/IP Properties
+Now your little router is a bona-fide DHCP server!  Plugin those computers and
+watch them work!  With Windows systems you should go into the TCP/IP Properties
 and select the 'Obtain an IP address automatically' and 'Obtain DNS server
-address automatically' options. Sometimes the changes aren't instantaneous, so
+address automatically' options.  Sometimes the changes aren't instantaneous, so
 you may have to open a command prompt and run <c>ipconfig /release</c> and
-<c>ipconfig /renew</c>. But enough about Windows, let's get back to our
+<c>ipconfig /renew</c>.  But enough about Windows, let's get back to our
 favorite penguin.
 </p>
 
@@ -372,25 +372,25 @@
 
 <p>
 When people want to visit a place on the internet, they remember names, not a
-string of funky numbers. After all, what's easier to remember, ebay.com or
-66.135.192.87? This is where the DNS steps in. DNS servers run all over the
+string of funky numbers.  After all, what's easier to remember, ebay.com or
+66.135.192.87?  This is where the DNS steps in.  DNS servers run all over the
 internet, and whenever someone wants to visit 'ebay.com', these servers turn
 'ebay.com' (what we understand) into '66.135.192.87' (what our computers
-understand). For more information about DNS, you can always visit <uri
+understand).  For more information about DNS, you can always visit <uri
 link="http://en.wikipedia.org/wiki/DNS">Wikipedia</uri>.
 </p>
 
 <p>
 Since we're using dnsmasq for our DHCP server, and it includes a DNS server,
-you've got nothing left to do here! Your little router is already providing
-DNS to its DHCP clients. Bet you wish everything was this easy ;).
+you've got nothing left to do here!  Your little router is already providing
+DNS to its DHCP clients.  Bet you wish everything was this easy ;).
 </p>
 
 <p>
 You're welcome to choose other DNS servers if you're more comfortable with
 them, but the reason dnsmasq is great is because it was designed to do exactly
-what we want and nothing more. It's a little DNS caching/forwarding server for
-local networks. We're not looking to provide DNS for our own domain here, just
+what we want and nothing more.  It's a little DNS caching/forwarding server for
+local networks.  We're not looking to provide DNS for our own domain here, just
 offer simple DNS services to everyone else on our LAN.
 </p>
 
@@ -409,17 +409,17 @@
 </p>
 
 <p>
-This is where Network Address Translation (NAT) steps in. NAT is a way of
+This is where Network Address Translation (NAT) steps in.  NAT is a way of
 connecting multiple computers in a private LAN to the internet when you have a
-smaller number of public IP addresses available to you. Typically you are given
+smaller number of public IP addresses available to you.  Typically you are given
 1 IP by your ISP, but you want to let your whole house connect to the internet.
-NAT is the magic that makes this possible. For more information about NAT, you
+NAT is the magic that makes this possible.  For more information about NAT, you
 can always visit <uri link="http://en.wikipedia.org/wiki/NAT">Wikipedia</uri>.
 </p>
 
 <note>
-Before we get started, make sure you have iptables on your system. Although it
-is automatically installed on most systems, you may not have it. If you don't,
+Before we get started, make sure you have iptables on your system.  Although it
+is automatically installed on most systems, you may not have it.  If you don't,
 just run <c>emerge iptables</c>.
 </note>
 
@@ -478,8 +478,8 @@
 
 <p>
 The ip_dynaddr option is useful for dial on demand systems or when your ISP
-gives out dynamic addresses. This works around the problem where a connection
-is attempted before the internet interface is fully setup. Really this just
+gives out dynamic addresses.  This works around the problem where a connection
+is attempted before the internet interface is fully setup.  Really this just
 provides for a smoother network experience for users behind your router.
 </p>
 
@@ -495,8 +495,8 @@
 <body>
 
 <p>
-Believe it or not, you're done :). From here on out, I'll cover a bunch of
-common topics that may interest you. Everything in this chapter is completely
+Believe it or not, you're done :).  From here on out, I'll cover a bunch of
+common topics that may interest you.  Everything in this chapter is completely
 optional.
 </p>
 
@@ -509,10 +509,10 @@
 
 <p>
 Sometimes you would like to be able to host services on a computer behind the
-router, or just to make your life easier when connecting remotely. Perhaps you
+router, or just to make your life easier when connecting remotely.  Perhaps you
 want to run a FTP, HTTP, SSH, or VNC server on one or more machines behind your
-router and be able to connect to them all. The only caveat is that you can
-only have one service/machine combo per port. For example, there is no
+router and be able to connect to them all.  The only caveat is that you can
+only have one service/machine combo per port.  For example, there is no
 practical way to setup three FTP servers behind your router and then try to
 connect to them all through port 21; only one can be on port 21 while the
 others would have to be on say port 123 and port 567.
@@ -521,9 +521,9 @@
 <p>
 All the port forwarding rules are of the form <c>iptables -t nat -A PREROUTING
 [-p protocol] --dport [external port on router] -i ${WAN} -j DNAT --to [ip/port
-to forward to]</c>. Unfortunately, iptables does not accept hostnames when port
-forwarding. If you are forwarding an external port to the same port on the
-internal machine, you can omit the destination port. See the iptables(8) man
+to forward to]</c>.  Unfortunately, iptables does not accept hostnames when port
+forwarding.  If you are forwarding an external port to the same port on the
+internal machine, you can omit the destination port.  See the iptables(8) man
 page for more information.
 </p>
 
@@ -585,9 +585,9 @@
 <body>
 
 <p>
-Internet Relay Chat utilizes the ident service pretty heavily. Now that the
+Internet Relay Chat utilizes the ident service pretty heavily.  Now that the
 IRC clients are behind the router, we need a way to host ident for both the
-router and the clients. One such server has been created called
+router and the clients.  One such server has been created called
 <c>midentd</c>.
 </p>
 
@@ -598,7 +598,7 @@
 </pre>
 
 <p>
-There are a few other ident servers in portage. Depending on your needs, I
+There are a few other ident servers in portage.  Depending on your needs, I
 would recommend checking out <c>oidentd</c> and <c>fakeidentd</c>.
 </p>
 
@@ -611,7 +611,7 @@
 <body>
 <p>
 This is an attempt to simply and Gentooify the <uri link="http://www.tldp.org/HOWTO/ADSL-Bandwidth-Management-HOWTO/">ADSL Bandwidth Management HOWTO</uri>
-found over at the TLDP. Feel free to refer to the original document
+found over at the TLDP.  Feel free to refer to the original document
 for more details.
 </p>
 
@@ -622,31 +622,31 @@
 Simply put, we want to setup rules on our router that will slow down
 certain activities (like sending large e-mails or downloading from P2P
 networks) while keeping other activities (like browsing the web or playing
-online video games) reasonably fast. A 30 second difference in a video
+online video games) reasonably fast.  A 30 second difference in a video
 game is a lot worse than a 30 second difference in downloading large
 files :).
 </p>
 
 <p>
 The first thing is to make sure your kernel has all the features added to
-it. See the chapter on <uri link="#doc_chap2">Kernel setup</uri> for more
-information. Next, you will need to <c>emerge iptables iputils</c> so that
+it.  See the chapter on <uri link="#doc_chap2">Kernel setup</uri> for more
+information.  Next, you will need to <c>emerge iptables iputils</c> so that
 you will have access to the <c>iptables</c>, <c>ip</c>, and <c>tc</c>
 commands.
 </p>
 
 <p>
-Before we jump into the commands, let's cover a little of the theory. The
+Before we jump into the commands, let's cover a little of the theory.  The
 way this whole system works is to classify common network streams and then
-to prioritize them. You use iptables to classify network streams, iputils
+to prioritize them.  You use iptables to classify network streams, iputils
 to define the different priority levels, and the kernel to adjust speeds.
 Just remember that although you can control outbound traffic pretty tightly
 (from the LAN to the WAN), your ability to control inbound traffic (from
-the WAN to the LAN) is somewhat limited. Just remember that the following
+the WAN to the LAN) is somewhat limited.  Just remember that the following
 examples are to get your feet wet; if you want more then I'd suggest
-reading up on the subject. In this example, we will be using the
+reading up on the subject.  In this example, we will be using the
 <uri link="http://luxik.cdi.cz/~devik/qos/htb/">Hierarchical Token Buckets (HTB)</uri>
-packet scheduling algorithm. Still with me? Great, let's start shaping :).
+packet scheduling algorithm.  Still with me?  Great, let's start shaping :).
 </p>
 
 <pre caption="Setup">
@@ -654,7 +654,7 @@
 RATE_OUT=100 <comment>Available outbound bandwidth (in kilobits [kb])</comment>
 RATE_IN=1400 <comment>Available inbound bandwidth (in kb)</comment>
 
-<comment>Here we initialize the priority system. The 45 is used to set the default classification level.</comment>
+<comment>Here we initialize the priority system.  The 45 is used to set the default classification level.</comment>
 ip link set dev ${DEV} qlen 30
 tc qdisc add dev ${DEV} root handle 1: htb default 45
 tc class add dev ${DEV} parent 1: classid 1:1 htb rate ${RATE_OUT}kbit
@@ -662,12 +662,12 @@
 
 <p>
 Here we initialized the system which will be used to prioritize all of
-our network traffic. We created our queue, told it to use the HTB
-algorithm, and set the default classification level to '45'. The
+our network traffic.  We created our queue, told it to use the HTB
+algorithm, and set the default classification level to '45'.  The
 default is completely arbitrary, as are the levels we choose from
-here on out. The only thing that matters is how the levels compare
+here on out.  The only thing that matters is how the levels compare
 relatively; a level '10' packet will be given preference over a
-level '45' packet. Let's move on to declaring different levels.
+level '45' packet.  Let's move on to declaring different levels.
 </p>
 
 <pre caption="Declaring levels">
@@ -690,14 +690,14 @@
 </p>
 
 <p>
-Many people run ntp clients on their computers. Obviously, the more clients in
-the world, the larger the load the ntp servers need to shoulder. In
+Many people run ntp clients on their computers.  Obviously, the more clients in
+the world, the larger the load the ntp servers need to shoulder.  In
 environments like home networks though, we can help keep the load down on
-public servers while still providing the proper time to all our computers. As
+public servers while still providing the proper time to all our computers.  As
 an added bonus, our private updates will be a lot faster for the clients too!
 All we have to do is run a ntp server on our router that synchronizes itself
 with the public internet servers while providing the time to the rest of the
-computers in the network. To get started, simply <c>emerge ntp</c> on the
+computers in the network.  To get started, simply <c>emerge ntp</c> on the
 router.
 </p>
 
@@ -722,12 +722,12 @@
 
 <note>
 You should make sure that you allow inbound and outbound communication on the
-ntp port (123/udp) when setting up the server. The client just needs outbound
+ntp port (123/udp) when setting up the server.  The client just needs outbound
 access on port 123 over udp.
 </note>
 
 <p>
-Now, on your clients, have them <c>emerge ntp</c> also. However, we will just
+Now, on your clients, have them <c>emerge ntp</c> also.  However, we will just
 run the ntp client so setup is a lot simpler.
 </p>
 
@@ -748,8 +748,8 @@
 <p>
 For those who run multiple Gentoo boxes on the same lan, you often want to
 keep from having every machine running <c>emerge sync</c> with remote
-servers. By setting up a local rsync, you save on both your bandwidth and
-the Gentoo rsync servers' bandwidth. It's pretty simple to do.
+servers.  By setting up a local rsync, you save on both your bandwidth and
+the Gentoo rsync servers' bandwidth.  It's pretty simple to do.
 </p>
 
 <note>
@@ -758,10 +758,10 @@
 </note>
 
 <p>
-Since every Gentoo machine requires rsync, theres no need to emerge it. Edit
+Since every Gentoo machine requires rsync, theres no need to emerge it.  Edit
 the default <path>/etc/rsyncd.conf</path> config file, uncomment the
 <c>[gentoo-portage]</c> section, and make sure you add an <c>address</c>
-option. All the other defaults should be fine.
+option.  All the other defaults should be fine.
 </p>
 
 <pre caption="Rsync server config">
@@ -771,9 +771,9 @@
 address = 192.168.0.1
 
 [gentoo-portage]
- path = /mnt/space/portage
- comment = Gentoo Linux Portage tree
- exclude = /distfiles /packages
+  path = /mnt/space/portage
+  comment = Gentoo Linux Portage tree
+  exclude = /distfiles /packages
 </pre>
 
 <p>
@@ -802,9 +802,9 @@
 
 <p>
 Sometimes it's nice to run your own Simple Mail Transfer Protocol (SMTP) server
-on the router. You may have your own reason for wanting to do so, but I run it
+on the router.  You may have your own reason for wanting to do so, but I run it
 so that the users see mail as being sent instantly and the work of
-retrying/routing is left up to the mail server. Some ISPs also don't allow for
+retrying/routing is left up to the mail server.  Some ISPs also don't allow for
 mail relaying for accounts that aren't part of their network (like Verizon).
 Also, you can easily throttle the delivery of mail so that large attachments
 won't seriously lag your connection for half an hour.
@@ -835,9 +835,9 @@
 </pre>
 
 <p>
-I'm a huge fan of qmail, but you're free to use a different mta :). When you
+I'm a huge fan of qmail, but you're free to use a different mta :).  When you
 setup e-mail on the hosts in your network, tell them that their SMTP server is
-192.168.0.1 and everything should be peachy. You might want to visit the <uri
+192.168.0.1 and everything should be peachy.  You might want to visit the <uri
 link="http://netqmail.org/">netqmail homepage</uri> for more documentation.
 </p>
 
@@ -868,9 +868,9 @@
 <body>
 
 <p>
-Earlier we used dnsmasq to provide DHCP service to all our clients. For most
-people with a simple small LAN, this is perfect. But you may need something
-with more features. Thus we turn to a full-featured DHCP server as provided
+Earlier we used dnsmasq to provide DHCP service to all our clients.  For most
+people with a simple small LAN, this is perfect.  But you may need something
+with more features.  Thus we turn to a full-featured DHCP server as provided
 by the <uri link="http://www.isc.org/products/DHCP">ISC</uri> folks.
 </p>
 
@@ -881,13 +881,13 @@
 authoritative;
 ddns-update-style interim;
 subnet 192.168.0.0 netmask 255.255.255.0 {
-  range 192.168.0.100 192.168.0.250;
-  default-lease-time 259200;
-  max-lease-time 518400;
-  option subnet-mask 255.255.255.0;
-  option broadcast-address 192.168.0.255;
-  option routers 192.168.0.1;
-  option domain-name-servers 192.168.0.1;
+    range 192.168.0.100 192.168.0.250;
+    default-lease-time 259200;
+    max-lease-time 518400;
+    option subnet-mask 255.255.255.0;
+    option broadcast-address 192.168.0.255;
+    option routers 192.168.0.1;
+    option domain-name-servers 192.168.0.1;
 }
 # <i>nano /etc/conf.d/dhcpd</i>
 <comment>(Set IFACE="eth0")</comment>
@@ -897,8 +897,8 @@
 
 <p>
 This is the minimal setup required to replace the dnsmasq DHCP functionality
-that we used earlier. Speaking of which, you did remember to disable the DHCP
-features in dnsmasq didn't you? If not, you should do so now (just comment
+that we used earlier.  Speaking of which, you did remember to disable the DHCP
+features in dnsmasq didn't you?  If not, you should do so now (just comment
 out the <c>dhcp-range</c> setting in <path>/etc/dnsmasq.conf</path> and restart
 the service).
 </p>
@@ -911,34 +911,34 @@
 <body>
 
 <p>
-Sometimes you have need of connecting the router to another LAN. Maybe you
+Sometimes you have need of connecting the router to another LAN.  Maybe you
 want to hook up a group of friends temporarily, or you're a neat freak and
 want to section off different groups of computers, or you're just really
-really bored. Whatever the reasons, extending the router to other LAN
-networks should be pretty straightforward. In the following examples, I will
+really bored.  Whatever the reasons, extending the router to other LAN
+networks should be pretty straightforward.  In the following examples, I will
 assume that this new network is connected via a third ethernet card, namely
 <c>eth2</c>.
 </p>
 
 <p>
-First you need to configure the interface. Just take the instructions in the
+First you need to configure the interface.  Just take the instructions in the
 <uri link="#doc_chap4_pre1">4.1 code listing</uri> and replace <c>eth0</c>
 with <c>eth2</c> and <c>192.168.0</c> with <c>192.168.1</c>.
 </p>
 
 <p>
-Then you need to tweak dnsmasq to service the new interface. Just edit the
+Then you need to tweak dnsmasq to service the new interface.  Just edit the
 <path>/etc/conf.d/dnsmasq</path> file again and append <c>-i eth2</c> to
-DNSMASQ_OPTS; using -i multiple times is OK. Then edit
+DNSMASQ_OPTS; using -i multiple times is OK.  Then edit
 <path>/etc/dnsmasq.conf</path> and add another line like the dhcp-range line
 in the <uri link="#doc_chap5_pre1">5.1 code listing</uri>, replacing
-<c>192.168.0</c> with <c>192.168.1</c>. Having multiple dhcp-range lines is
+<c>192.168.0</c> with <c>192.168.1</c>.  Having multiple dhcp-range lines is
 OK too.
 </p>
 
 <p>
 Finally, see the rules in the <uri link="#doc_chap5_pre2">5.2 code
-listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them. You
+listing</uri> and duplicate the rules that have <c>-i ${LAN}</c> in them.  You
 may want to create another variable, say <c>LAN2</c>, to make things easier.
 </p>
 
@@ -962,24 +962,24 @@
 
 <table>
 <tr>
- <th>Utility</th>
- <th>Description</th>
+  <th>Utility</th>
+  <th>Description</th>
 </tr>
 <tr>
- <ti>wireshark</ti>
- <ti>GUI tool to view all raw network data according to filters</ti>
+  <ti>wireshark</ti>
+  <ti>GUI tool to view all raw network data according to filters</ti>
 </tr>
 <tr>
- <ti>tcpdump</ti>
- <ti>Console tool to dump all raw network data according to filters</ti>
+  <ti>tcpdump</ti>
+  <ti>Console tool to dump all raw network data according to filters</ti>
 </tr>
 <tr>
- <ti>iptraf</ti>
- <ti>ncurses based IP LAN monitor</ti>
+  <ti>iptraf</ti>
+  <ti>ncurses based IP LAN monitor</ti>
 </tr>
 <tr>
- <ti>ettercap</ti>
- <ti>ncurses based network monitor/control</ti>
+  <ti>ettercap</ti>
+  <ti>ncurses based network monitor/control</ti>
 </tr>
 </table>
 
@@ -997,16 +997,16 @@
 
 <pre caption="DHCP Failing Example">
 # <i>/etc/init.d/dhcp start</i>
- * Setting ownership on dhcp.leases ...     [ ok ]
- * Starting dhcpd ...              [ !! ]
+ * Setting ownership on dhcp.leases ...          [ ok ]
+ * Starting dhcpd ...                            [ !! ]
 </pre>
 
 <p>
-The trick is to know where dhcpd is sending its output. Simply browse to
-<path>/var/log</path> and read the log files. Since the exact log file depends
+The trick is to know where dhcpd is sending its output.  Simply browse to
+<path>/var/log</path> and read the log files.  Since the exact log file depends
 on the package you are using as a syslog, try running <c>grep -Rl dhcpd
-/var/log</c> to narrow down the possibilities. Chances are you made a typo in
-your config file. You could also try running <c>dhcpd -d -f</c> (short for
+/var/log</c> to narrow down the possibilities.  Chances are you made a typo in
+your config file.  You could also try running <c>dhcpd -d -f</c> (short for
 debug / foreground) and debug the error based upon the output.
 </p>
 
@@ -1019,7 +1019,7 @@
 
 <p>
 If you experience odd errors (such as not being able to access some webpages
-while others load fine), you may be having Path MTU Discovery trouble. The
+while others load fine), you may be having Path MTU Discovery trouble.  The
 quick way to test is to run this iptables command:
 </p>
 
@@ -1047,7 +1047,7 @@
 If (for whatever reason) you want to connect two machines directly together
 without a hub or switch, a regular ethernet cable will likely not work, unless
 you have an Auto MDI/MDI-X (also known as "autosensing") capable network
-adapter. You will need a different cable called a crossover cable. This <uri
+adapter.  You will need a different cable called a crossover cable.  This <uri
 link="http://en.wikipedia.org/wiki/Ethernet_crossover_cable">Wikipedia</uri>
 page explains the low level details.
 </p>
@@ -1065,7 +1065,7 @@
 <p>
 I have no final notes other than if you experience any troubles with the guide,
 please contact <mail link="vapier@gentoo.org">me</mail> or file a bug with <uri
-link="http://bugs.gentoo.org/">Gentoo's Bugtracking Website</uri>. If you have
+link="http://bugs.gentoo.org/">Gentoo's Bugtracking Website</uri>.  If you have
 some interesting bits you think would enhance this guide, by all means send it
 my way for inclusion.
 </p>



-- 
gentoo-doc-cvs@lists.gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* [gentoo-doc-cvs] cvs commit: home-router-howto.xml
@ 2008-08-19 14:15 Mike Frysinger
  0 siblings, 0 replies; 32+ messages in thread
From: Mike Frysinger @ 2008-08-19 14:15 UTC (permalink / raw
  To: gentoo-doc-cvs

vapier      08/08/19 14:15:59

  Modified:             home-router-howto.xml
  Log:
  add note for people to try putting the mtu clamp into the mangle table if it doesnt work for them otherwise

Revision  Changes    Path
1.62                 xml/htdocs/doc/en/home-router-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.62&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?rev=1.62&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/home-router-howto.xml?r1=1.61&r2=1.62

Index: home-router-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- home-router-howto.xml	20 May 2008 19:09:36 -0000	1.61
+++ home-router-howto.xml	19 Aug 2008 14:15:59 -0000	1.62
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.61 2008/05/20 19:09:36 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/home-router-howto.xml,v 1.62 2008/08/19 14:15:59 vapier Exp $ -->
 
 <guide link="/doc/en/home-router-howto.xml" lang="en">
 <title>Home Router Guide</title>
@@ -17,8 +17,8 @@
 <!-- The content of this document is released into the public domain -->
 <license/>
 
-<version>1.38</version>
-<date>2007-07-27</date>
+<version>1.39</version>
+<date>2008-08-19</date>
 
 <chapter>
 <title>Introduction</title>
@@ -1036,6 +1036,11 @@
 Traffic Control HOWTO</uri>.
 </p>
 
+<p>
+If that command does not work for you, you may want to try putting the rule
+into the mangle table.  Simply add <c>-t mangle</c> to the command.
+</p>
+
 </body>
 </section>
 






^ permalink raw reply	[flat|nested] 32+ messages in thread

end of thread, other threads:[~2008-08-19 14:16 UTC | newest]

Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-21 10:50 [gentoo-doc-cvs] cvs commit: home-router-howto.xml vapier
  -- strict thread matches above, loose matches on Subject: below --
2008-08-19 14:15 Mike Frysinger
2008-05-20 19:09 Sven Vermeulen
2008-05-20 18:57 Sven Vermeulen
2007-07-27 17:50 Josh Saddler
2007-04-07  2:16 vapier
2007-04-03 23:06 vapier
2007-01-28 22:36 vapier
2006-11-08 19:39 Josh Saddler
2006-10-21 21:04 vapier
2006-09-16  5:29 vapier
2006-08-21 10:47 vapier
2006-08-21 10:21 vapier
2006-08-12 12:18 Jan Kundrat
2006-08-04 13:24 vapier
2006-06-18 12:21 Lukasz Damentko
2006-06-13  9:47 Xavier Neys
2006-04-09 17:22 vapier
2006-03-29  1:30 vapier
2006-03-17 10:17 Xavier Neys
2005-12-21 11:12 Xavier Neys
2005-12-21  1:09 vapier
2005-12-12  4:36 vapier
2005-12-05 13:34 Xavier Neys
2005-11-09  3:59 vapier
2005-11-05  2:45 vapier
2005-10-11  1:02 vapier
2005-09-17  7:40 vapier
2005-09-06  3:03 vapier
2005-08-17 22:42 vapier
2005-08-14  4:38 vapier
2005-08-04  0:18 Mike Frysinger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox