swift       05/06/09 07:33:59

  Modified:    xml/htdocs/doc/en/handbook handbook-alpha.xml
                        handbook-amd64.xml handbook-hppa.xml
                        handbook-mips.xml handbook-ppc.xml
                        handbook-ppc64.xml handbook-sparc.xml
                        handbook-x86.xml index.xml
  Added:       xml/htdocs/doc/en/handbook hb-net-advanced.xml
                        hb-net-functions.xml hb-net-management.xml
                        hb-net-modules.xml hb-net-start.xml
                        hb-net-wireless.xml
  Log:
  #88188 - New baselayout -> new part on the Gentoo Handbook

Revision  Changes    Path
1.115     +62 -3     xml/htdocs/doc/en/handbook/handbook-alpha.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-alpha.xml?rev=1.115&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-alpha.xml?rev=1.115&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-alpha.xml.diff?r1=1.114&r2=1.115&cvsroot=gentoo

Index: handbook-alpha.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -r1.114 -r1.115
--- handbook-alpha.xml  28 Mar 2005 15:20:51 -0000      1.114
+++ handbook-alpha.xml  9 Jun 2005 07:33:58 -0000       1.115
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v 1.114 
2005/03/28 15:20:51 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-alpha.xml,v 1.115 
2005/06/09 07:33:58 swift Exp $ -->
 
 <book link="handbook-alpha.xml">
 <title>Gentoo Linux Alpha Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -113,8 +116,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.10</version>
-<date>2005-03-28</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -356,4 +359,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.123     +62 -3     xml/htdocs/doc/en/handbook/handbook-amd64.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.123&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.123&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-amd64.xml.diff?r1=1.122&r2=1.123&cvsroot=gentoo

Index: handbook-amd64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -r1.122 -r1.123
--- handbook-amd64.xml  28 Mar 2005 15:20:51 -0000      1.122
+++ handbook-amd64.xml  9 Jun 2005 07:33:58 -0000       1.123
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.122 
2005/03/28 15:20:51 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.123 
2005/06/09 07:33:58 swift Exp $ -->
 
 <book link="handbook-amd64.xml">
 <title>Gentoo Linux AMD64 Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -113,8 +116,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.15</version>
-<date>2005-03-28</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -355,4 +358,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.112     +62 -3     xml/htdocs/doc/en/handbook/handbook-hppa.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-hppa.xml?rev=1.112&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-hppa.xml?rev=1.112&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-hppa.xml.diff?r1=1.111&r2=1.112&cvsroot=gentoo

Index: handbook-hppa.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -r1.111 -r1.112
--- handbook-hppa.xml   4 Jan 2005 18:11:20 -0000       1.111
+++ handbook-hppa.xml   9 Jun 2005 07:33:59 -0000       1.112
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v 1.111 
2005/01/04 18:11:20 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-hppa.xml,v 1.112 
2005/06/09 07:33:59 swift Exp $ -->
 
 <book link="handbook-hppa.xml">
 <title>Gentoo Linux HPPA Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -113,8 +116,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.8</version>
-<date>2005-01-04</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -355,4 +358,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.102     +62 -3     xml/htdocs/doc/en/handbook/handbook-mips.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-mips.xml?rev=1.102&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-mips.xml?rev=1.102&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-mips.xml.diff?r1=1.101&r2=1.102&cvsroot=gentoo

Index: handbook-mips.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- handbook-mips.xml   14 Feb 2005 14:59:19 -0000      1.101
+++ handbook-mips.xml   9 Jun 2005 07:33:59 -0000       1.102
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v 1.101 
2005/02/14 14:59:19 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-mips.xml,v 1.102 
2005/06/09 07:33:59 swift Exp $ -->
 
 <book link="handbook-mips.xml">
 <title>Gentoo Linux/MIPS Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -116,8 +119,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.9</version>
-<date>2005-02-14</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -357,4 +360,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.132     +62 -3     xml/htdocs/doc/en/handbook/handbook-ppc.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.132&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc.xml?rev=1.132&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc.xml.diff?r1=1.131&r2=1.132&cvsroot=gentoo

Index: handbook-ppc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -r1.131 -r1.132
--- handbook-ppc.xml    28 Mar 2005 15:20:51 -0000      1.131
+++ handbook-ppc.xml    9 Jun 2005 07:33:59 -0000       1.132
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.131 
2005/03/28 15:20:51 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc.xml,v 1.132 
2005/06/09 07:33:59 swift Exp $ -->
 
 <book link="handbook-ppc.xml">
 <title>Gentoo Linux PPC Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -116,8 +119,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.13</version>
-<date>2005-03-28</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -359,4 +362,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.54      +62 -3     xml/htdocs/doc/en/handbook/handbook-ppc64.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?rev=1.54&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc64.xml?rev=1.54&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-ppc64.xml.diff?r1=1.53&r2=1.54&cvsroot=gentoo

Index: handbook-ppc64.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- handbook-ppc64.xml  28 Mar 2005 15:20:51 -0000      1.53
+++ handbook-ppc64.xml  9 Jun 2005 07:33:59 -0000       1.54
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v 1.53 
2005/03/28 15:20:51 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-ppc64.xml,v 1.54 
2005/06/09 07:33:59 swift Exp $ -->
 
 <book link="handbook-ppc64.xml">
 <title>Gentoo Linux PPC64 Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -113,8 +116,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.14</version>
-<date>2005-03-28</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -357,4 +360,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.115     +62 -3     xml/htdocs/doc/en/handbook/handbook-sparc.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-sparc.xml?rev=1.115&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-sparc.xml?rev=1.115&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-sparc.xml.diff?r1=1.114&r2=1.115&cvsroot=gentoo

Index: handbook-sparc.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -r1.114 -r1.115
--- handbook-sparc.xml  28 Mar 2005 15:20:51 -0000      1.114
+++ handbook-sparc.xml  9 Jun 2005 07:33:59 -0000       1.115
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v 1.114 
2005/03/28 15:20:51 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-sparc.xml,v 1.115 
2005/06/09 07:33:59 swift Exp $ -->
 
 <book link="handbook-sparc.xml">
 <title>Gentoo Linux SPARC Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -113,8 +116,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.9</version>
-<date>2005-03-28</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -355,4 +358,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.142     +62 -3     xml/htdocs/doc/en/handbook/handbook-x86.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.142&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.142&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/handbook-x86.xml.diff?r1=1.141&r2=1.142&cvsroot=gentoo

Index: handbook-x86.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -r1.141 -r1.142
--- handbook-x86.xml    28 Mar 2005 15:20:51 -0000      1.141
+++ handbook-x86.xml    9 Jun 2005 07:33:59 -0000       1.142
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE book SYSTEM "/dtd/book.dtd">
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.141 
2005/03/28 15:20:51 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.142 
2005/06/09 07:33:59 swift Exp $ -->
 
 <book link="handbook-x86.xml">
 <title>Gentoo Linux x86 Handbook</title>
@@ -10,6 +10,9 @@
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
 <author title="Author">
+  <mail link="[EMAIL PROTECTED]">Roy Marples</mail>
+</author>
+<author title="Author">
     <mail link="[EMAIL PROTECTED]">Daniel Robbins</mail>
 </author>
 <author title="Author">
@@ -113,8 +116,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
 <license/>
 
-<version>3.10</version>
-<date>2005-03-28</date>
+<version>4.0</version>
+<date>2005-06-09</date>
 
 <part>
 <title>Installing Gentoo</title>
@@ -355,4 +358,60 @@
 </chapter>
 </part>
 
+<part>
+<title>Gentoo Network Configuration</title>
+<abstract>A comprehensive guide to Networking in Gentoo.</abstract>
+
+<chapter>
+<title>Getting Started</title>
+<abstract>
+A guide to quickly get your network interface up and running in most common
+environments.
+</abstract>
+<include href="hb-net-start.xml"/>
+</chapter>
+
+<chapter>
+<title>Advanced Configuration</title>
+<abstract>
+Here we learn about how the configuration works - you need to know this
+before we learn about modular networking.
+</abstract>
+<include href="hb-net-advanced.xml"/>
+</chapter>
+
+<chapter>
+<title>Modular Networking</title>
+<abstract>
+Gentoo provides you flexible networking - here you are told about choosing
+different DHCP clients, setting up bonding, bridging, VLANs and more.
+</abstract>
+<include href="hb-net-modules.xml"/>
+</chapter>
+
+<chapter>
+<title>Wireless Networking</title>
+<abstract>
+Wireless isn't straight-forward. Hopefully we'll get you working!
+</abstract>
+<include href="hb-net-wireless.xml"/>
+</chapter>
+
+<chapter>
+<title>Adding Functionality</title>
+<abstract>
+If you're feeling adventurous, you can add your own functions to networking.
+</abstract>
+<include href="hb-net-functions.xml"/>
+</chapter>
+
+<chapter>
+<title>Network Management</title>
+<abstract>
+For laptop users or people who move their computer around different networks.
+</abstract>
+<include href="hb-net-management.xml"/>
+</chapter>
+</part>
+
 </book>



1.52      +7 -6      xml/htdocs/doc/en/handbook/index.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/index.xml?rev=1.52&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/index.xml?rev=1.52&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/index.xml.diff?r1=1.51&r2=1.52&cvsroot=gentoo

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- index.xml   25 May 2005 10:18:28 -0000      1.51
+++ index.xml   9 Jun 2005 07:33:59 -0000       1.52
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.51 
2005/05/25 10:18:28 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/index.xml,v 1.52 
2005/06/09 07:33:59 swift Exp $ -->
 
 <guide link="index.xml">
 <title>Gentoo Handbook</title>
@@ -19,8 +19,8 @@
 
 <license/>
 
-<version>0.26</version>
-<date>2005-05-25</date>
+<version>0.27</version>
+<date>2005-06-09</date>
 
 <chapter>
 <title>The Gentoo Handbook Effort</title>
@@ -210,9 +210,10 @@
 <body>
 
 <p>
-At this time, the third part on <uri link="handbook-x86.xml?part=3">Working
-with Portage</uri> is finished and officially available. This part contains
-an in-depth coverage of Portage aspects.
+At this time, the fourth part on <uri link="handbook-x86.xml?part=4">Gentoo
+Network Configuration</uri> is finished and officially available. This part 
+contains an in-depth coverage of the networking configuration options for the
+now stable baselayout.
 </p>
 
 <p>



1.1                  xml/htdocs/doc/en/handbook/hb-net-advanced.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-net-advanced.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->

<sections>

<version>1.0</version>
<date>2005-06-06</date>

<section>
<title>Advanced Configuration</title>
<body>

<p>
The config_eth0 variable is the heart of an interface's configuration.
It's a high level instruction list for configuring the interface (eth0 in
this case). Each command in the instruction list is performed sequentially.
The interface is deemed OK if at least one command works.
</p>

<p>
Here's a list of in-built instructions.
</p>

<table>
  <tr>
    <th>Command</th>
    <th>Description</th>
  </tr>
  <tr>
    <ti>null</ti>
    <ti>Do nothing</ti>
  </tr>
  <tr>
    <ti>noop</ti>
    <ti>
      If the interface is up and there is an address then abort configuration
      successfully
    </ti>
  </tr>
  <tr>
    <ti>an IPv4 or IPv6 address</ti>
    <ti>Add the address to the interface</ti>
  </tr>
  <tr>
    <ti>
      dhcp, adsl or apipa<br/>
      (or a custom command from a 3rd party module)
    </ti>
    <ti>
      Run the module which provides the command. For example "dhcp" will
      run a module that provides dhcp which can be one of either dhcpcd,
      udhcpc, dhclient or pump.
    </ti>
  </tr>
</table>

<p>
If a command fails, you can specify a fallback command. The fallback has to
match the config structure exactly.
</p>

<p>
You can chain these commands together. Here are some real world some examples.
</p>

<pre caption="config examples">
<comment># Adding three IPv4 addresses</comment>
config_eth0=(
        "192.168.0.2/24"
        "192.168.0.3/24"
        "192.168.0.4/24"
)

<comment># Adding an IPv4 address and two IPv6 addresses</comment>
config_eth0=(
        "192.168.0.2/24"
        "4321:0:1:2:3:4:567:89ab"
        "4321:0:1:2:3:4:567:89ac"
)

<comment># Keep our kernel assigned address, unless the interface goes
# down so assign another via DHCP. If DHCP fails then add a
# static address determined by APIPA</comment>
config_eth0=(
        "noop"
        "dhcp"
)
fallback_eth0=(
        "null"
        "apipa"
)
</pre>

<note>
When using the ifconfig module and adding more than one address, interface
aliases are created for each extra address. So with the above two examples you
will get interfaces eth0, eth0:1 and eth0:2.
You cannot do anything special with these interfaces as the kernel and other
programs will just treat eth0:1 and eth0:2 as eth0
</note>

<impo>
The fallback order is important! If we did not specify the "null" option then
the "apipa" command would only be run if the "noop" command failed.
</impo>

<note>
<uri link="?part=3&amp;chap=3#apipa">APIPA</uri> and
<uri link="?part=3&amp;chap=3#dhcp">DHCP</uri> are discussed later
</note>

</body>
</section>

<section>
<title>Network Dependencies</title>
<body>

<p>Init scripts in <path>/etc/init.d</path> can depend on a specific network
interface or just net. "net" can be defined in <path>/etc/conf.d/rc</path> to
mean different things using the <c>RC_NET_STRICT_CHECKING</c> variable.
</p>

<table>
  <tr>
    <th>Value</th>
    <th>Description</th>
  </tr>
  <tr>
    <ti>none</ti>
    <ti>The net service is always considered up</ti>
  </tr>
  <tr>
    <ti>no</ti>
    <ti>
      This basically means that at least one net.* service besides net.lo
      must be up.  This can be used by notebook users that have a wifi and
      a static nic, and only wants one up at any given time to have the
      net service seen as up.
    </ti>
  </tr>
  <tr>
    <ti>lo</ti>
    <ti>
      This is the same as the 'no' option, but net.lo is also counted.
      This should be useful to people that do not care about any specific
      interface being up at boot.
    </ti>
  </tr>
  <tr>
    <ti>yes</ti>
    <ti>
      For this ALL network interfaces MUST be up for the 'net' service to
      be considered up.
    </ti>
  </tr>
</table>

<p>
But what about net.br0 depending on net.eth0 and net.eth1?
net.eth1 may be a wireless or ppp device that needs configuration before it
can be added to the bridge.
This cannot be done in <path>/etc/init.d/net.br0</path> as that's a symbolic
link to net.lo
</p>

<p>
The answer is making your own depend() function in <path>/etc/conf.d/net</path>
</p>

<pre caption="net.br0 dependency in /etc/conf.d/net">
<comment># You can use any dependency (use, after, before) as found in current 
scripts</comment>
depend_br0() {
        need net.eth0 net.eth1
}
</pre>

<p>
For a more detailed discussion about dependency,
<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=4#doc_chap4">
consult the Gentoo Handbook</uri>
</p>

</body>
</section>

<section id="variable_name">
<title>Variable names and values</title>
<body>

<p>
Variable names are dynamic. They are normally follow the structure of
<c>variable_${interface|mac|essid|apmac}</c>. For example, the variable
<c>dhcpcd_eth0</c> holds the value for dhcpcd options for eth0 and
<c>dhcpcd_essid</c> holds the value for dhcpcd options when any interface
connects to the essid "essid".
        <<Truncated>>


1.1                  xml/htdocs/doc/en/handbook/hb-net-functions.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-functions.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-functions.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-net-functions.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->

<sections>

<version>1.0</version>
<date>2005-06-06</date>

<section>
<title>Standard function hooks</title>
<body>

<p>
Four functions can be defined which will be called surrounding the
start/stop operations.  The functions are called with the interface
name first so that one function can control multiple adapters.
</p>

<p>
The return values for the preup and predown functions should be 0
(success) to indicate that configuration or deconfiguration of the
interface can continue.  If preup returns a non-zero value, then
interface configuration will be aborted.  If predown returns a
non-zero value, then the interface will not be allowed to continue
deconfiguration.
</p>

<p>
The return values for the postup and postdown functions are ignored
since there's nothing to do if they indicate failure.
</p>

<p>
<c>${IFACE}</c> is set to the interface being brought up/down<br/>
<c>${IFVAR}</c> is <c>${IFACE}</c> converted to variable name bash allows
</p>

<pre caption="pre/post up/down function examples">
preup() {
        <comment># Test for link on the interface prior to bringing it up.  This
        # only works on some network adapters and requires the mii-diag
        # package to be installed.</comment>
        if mii-tool ${IFACE} 2> /dev/null | grep -q 'no link'; then
                ewarn "No link on ${IFACE}, aborting configuration"
                return 1
        fi

        <comment># Test for link on the interface prior to bringing it up.  This
        # only works on some network adapters and requires the ethtool
        # package to be installed.</comment>
        if ethtool ${IFACE} | grep -q 'Link detected: no'; then
                ewarn "No link on ${IFACE}, aborting configuration"
                return 1
        fi

        <comment># Remember to return 0 on success</comment>
        return 0
}

predown() {
        <comment># The default in the script is to test for NFS root and 
disallow
        # downing interfaces in that case.  Note that if you specify a
        # predown() function you will override that logic.  Here it is, in
        # case you still want it...</comment>
        if is_net_fs /; then
                eerror "root filesystem is network mounted -- can't stop 
${IFACE}"
                return 1
        fi

        <comment># Remember to return 0 on success</comment>
        return 0
}

postup() {
        <comment># This function could be used, for example, to register with a
        # dynamic DNS service.  Another possibility would be to
        # send/receive mail once the interface is brought up.</comment>
       return 0
}

postdown() {
        <comment># This function is mostly here for completeness... I haven't
        # thought of anything nifty to do with it yet ;-)</comment>
        return 0
}
</pre>

</body>
</section>

<section>
<title>Wireless Tools function hooks</title>
<body>

<note>
This will not work with WPA Supplicant - but the <c>${ESSID}</c> and
<c>${ESSIDVAR}</c> variables are available in the postup() function
</note>

<p>
Two functions can be defined which will be called surrounding the
associate function.  The functions are called with the interface
name first so that one function can control multiple adapters.
</p>

<p>
The return values for the preassociate function should be 0
(success) to indicate that configuration or deconfiguration of the
interface can continue.  If preassociate returns a non-zero value, then
interface configuration will be aborted.
</p>

<p>
The return value for the postassociate function is ignored
since there's nothing to do if it indicates failure.
</p>

<p>
<c>${ESSID}</c> is set to the exact ESSID of the AP you're connecting to<br/>
<c>${ESSIDVAR}</c> is <c>${ESSID}</c> converted to variable name bash allows
</p>

<pre caption="pre/post association functions">
preassociate() {
        <comment># The below adds two configuration variables leap_user_ESSID
        # and leap_pass_ESSID. When they are both configured for the ESSID
        # being connected to then we run the CISCO LEAP script</comment>

        local user pass
        eval user=\"\$\{leap_user_${ESSIDVAR}\}\"
        eval pass=\"\$\{leap_pass_${ESSIDVAR}\}\"

        if [[ -n ${user} &amp;&amp; -n ${pass} ]]; then
                if [[ ! -x /opt/cisco/bin/leapscript ]]; then
                        eend "For LEAP support, please emerge 
net-misc/cisco-aironet-client-utils"
                        return 1
                fi
                einfo "Waiting for LEAP Authentication on \"${ESSID//\\\\//}\""
                if /opt/cisco/bin/leapscript ${user} ${pass} | grep -q 'Login 
incorrect'; then
                        ewarn "Login Failed for ${user}"
                        return 1
                fi
        fi

        return 0
}

postassociate() {
        <comment># This function is mostly here for completeness... I haven't
        # thought of anything nifty to do with it yet ;-)</comment>

        return 0
}
</pre>

<note>
<c>${ESSID}</c> and <c>${ESSIDVAR}</c> are unavailable in predown() and 
postdown() functions
</note>

</body>
</section>

</sections>



1.1                  xml/htdocs/doc/en/handbook/hb-net-management.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-management.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-management.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-net-management.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->

<sections>

<version>1.0</version>
<date>2005-06-06</date>

<section>
<title>Network Management</title>
<body>

<p>
If you and your computer are always on the move, you may not always have an
ethernet cable or plugged in or an access point available. Also, we may want
networking to automatically work when an ethernet cable is plugged in or an
access point is found.</p>

<p>
Here you can find some tools that helps you manage this.
</p>

<note>
This document only talks about ifplugd, but there are alternatives you can
look into like quickswitch
</note>

</body>
</section>

<section>
<title>ifplugd</title>
<body>

<p>
<uri link="http://0pointer.de/lennart/projects/ifplugd/";>ifplugd</uri> is a
daemon that starts and stops interfaces when an ethernet cable is inserted or
removed. It can also manage detecting association to Access Points or when new
ones come in range.
</p>

<pre caption="install ifplugd">
# <i>emerge sys-apps/ifplugd</i>
</pre>

<p>
Configuration for ifplugd is fairly straightforward too. The configuration file
is held in <path>/etc/conf.d/ifplugd</path><br/>
<c>man ifplugd</c> for details on what the variables do.
</p>

<pre caption="sample ifplug configuration">
<comment># Define which interfaces we monitor</comment>
INTERFACES="eth0"

AUTO="no"
BEEP="yes"
IGNORE_FAIL="yes"
IGNORE_FAIL_POSITIVE="no"
IGNORE_RETVAL="yes"
POLL_TIME="1"
DELAY_UP="0"
DELAY_DOWN="0"
API_MODE="auto"
SHUTDOWN="no"
WAIT_ON_FORK="no"
MONITOR="no"
ARGS=""

<comment># Additional parameters for ifplugd for the specified interface. Note 
that
# the global variable is ignored, when a variable like this is set for an
# interface</comment>
MONITOR_wlan0="yes"
DELAY_UP_wlan0="5"
DELAY_DOWN_wlan0="5"
</pre>

</body>
</section>

</sections>



1.1                  xml/htdocs/doc/en/handbook/hb-net-modules.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-modules.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-modules.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-net-modules.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->

<sections>

<version>1.0</version>
<date>2005-06-06</date>

<section>
<title>Network Modules</title>
<body>

<p>
We now support modular networking scripts, which means we can easily
add support for new interface types and configuration modules while keeping
compatibility with existing ones.
</p>

<p>
Modules load by default if the package they need is installed.  If
you specify a module here that doesn't have its package installed
then you get an error stating which package you need to install.
Ideally, you only use the modules setting when you have two or more
packages installed that supply the same service and you need to prefer
one over the other.
</p>

<pre caption="Module preference">
<comment># Prefer iproute2 over ifconfig</comment>
modules=( "iproute2" )

<comment># You can also specify other modules for an interface
# In this case we prefer udhcpc over dhcpcd</comment>
modules_eth0=( "udhcpc" )

<comment># You can also specify which modules not to use - for example you may 
be
# using a supplicant or linux-wlan-ng to control wireless configuration but
# you still want to configure network settings per ESSID associated 
with.</comment>
modules=( "!iwconfig" )
</pre>

</body>
</section>

<section>
<title>Interface Handlers</title>
<body>

<p>
We provide two interface handlers presently: ifconfig and iproute2.
You need one of these to do any kind of network configuration.
</p>

<p>
ifconfig is the current Gentoo default and it's included in the system 
profile.<br/>
iproute2 is a more powerful and flexible package, but it's not included by 
default.
</p>

<pre caption="To install iproute2">
# <i>emerge sys-apps/iproute2</i>

<comment># To prefer iproute2 over ifconfig if both are installed</comment>
modules=( "iproute2" )
</pre>

<p>
As both ifconfig and iproute2 do very similar things we allow their basic 
configuration
to work with each other. For example both the below code snippets work 
regardless of
which module you are using.
</p>

<pre caption="ifconfig and iproute2 examples">
config_eth0=( "192.168.0.2/24" )
config_eth0=( "192.168.0.2 netmask 255.255.255.0" )

<comment># We can also specify broadcast</comment>
config_eth0=( "192.168.0.2/24 brd 192.168.0.255" )
config_eth0=( "192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255" )
</pre>

</body>
</section>

<section id="dhcp">
<title>DHCP</title>
<body>

<p>
DHCP is a means of obtaining network information (IP address, DNS servers,
Gateway, etc) from a DHCP server. This means that if there is a DHCP server
running on the network, you just have to tell each client to use DHCP and it
sets up the network all by itself. Of course, you will have to configure for
other things like wireless, ppp or other things if required before you can use
DHCP.
</p>

<p>
DHCP can be provided by dhclient, dhcpcd, dhclient, pump or udhcpc. Each DHCP 
module
has its pros and cons - here's a quick run down.
</p>

<table>
  <tr>
    <th>DHCP Module</th>
    <th>Package</th>
    <th>Pros</th>
    <th>Cons</th>
  </tr>
  <tr>
    <ti>dhclient</ti>
    <ti>net-misc/dhcp</ti>
    <ti>
        Made by ISC, the same people who make the BIND DNS software<br />
        Very configurable
    </ti>
    <ti>
        Configuration is overly complex<br />
        Software is quite bloated<br />
        Cannot get NTP servers from DHCP<br />
        Does not send hostname by default
    </ti>
  </tr>
  <tr>
    <ti>dhcpcd</ti>
    <ti>net-misc/dhcpcd</ti>
    <ti>
        Long time Gentoo default<br />
        No reliance on outside tools
    </ti>
    <ti>
        No longer maintained upstream<br />
        Can be slow at times<br />
        Does not daemonize when lease is infinite
    </ti>
  </tr>
  <tr>
    <ti>pump</ti>
    <ti>net-misc/pump</ti>
    <ti>
        Lightweight<br />
        No reliance on outside tools
    </ti>
    <ti>
        No longer maintained upstream<br />
        Unreliable, especially over modems<br />
        Cannot get NIS servers from DHCP
    </ti>
  </tr>
  <tr>
    <ti>udhcpc</ti>
    <ti>net-misc/udhcp</ti>
    <ti>
        Lightweight - smallest dhcp client around<br />
        Made for embedded systems
    </ti>
    <ti>
        Unproven - no distro uses it by default<br />
        Cannot define a timeout beyond 3 seconds
    </ti>
  </tr>
</table>
     
<p>
If you have more than one DHCP client installed, you need to specify which
one to use - otherwise we default to dhcpcd if available.
</p>

<p>
To send specific options to the dhcp module, use module_eth0="..."
<e>(change module to the DHCP module you're using - ie dhcpcd_eth0)</e>
</p>

<p>
We try and make DHCP relatively agnostic - as such we support the following
commands using the dhcp_eth0 variable. The default is not to set any of them
</p>

<ul>
  <li>release - releases the IP address for re-use</li>
  <li>nodns - don't overwrite /etc/resolv.conf</li>
  <li>nontp - don't overwrite /etc/ntp.conf</li>
  <li>nonis - don't overwrite /etc/yp.conf</li>
</ul>

<pre caption="Sample DHCP configuration in /etc/conf.d/net">
<comment># Only needed if you have more than one DHCP module installed</comment>
modules=( "dhcpcd" ) 

config_eth0=( "dhcp" )
dhcpcd_eth0="-t 10" <comment># Timeout after 10 seconds</comment>
dhcp_eth0="release nodns nontp nonis" <comment># Only get an address</comment>
</pre>

<note>
dhcpcd, udhcpc and pump send the current hostname to the DHCP server by
default so you don't need to specify this anymore.
        <<Truncated>>


1.1                  xml/htdocs/doc/en/handbook/hb-net-start.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-start.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-start.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-net-start.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->

<sections>

<version>1.0</version>
<date>2005-06-06</date>

<section>
<title>Getting started</title>
<body>

<note>
This document assumes that you have correctly configured your kernel, its
modules for your hardware and you know the interface name of your hardware.
We also assume that you are configuring eth0, but it could also be
eth1, wlan0, etc.
</note>

<note>
This document requires you are running baselayout-1.11.11 or better.
</note>

<p>
To get started configuring your network card, you need to tell the Gentoo RC
system about it. This is done by creating a symbolic link from <c>net.lo</c>
to <c>net.eth0</c> in <path>/etc/init.d</path>
</p>

<pre>
# <i>cd /etc/init.d</i>
# <i>ln -s net.lo net.eth0</i>
</pre>

<p>
Gentoo's RC system now knows about that interface. It also needs to know how
to configure the new interface. All the network interfaces are configured in
<path>/etc/conf.d/net</path>.<br/>
Below is a sample configuration for DHCP and static addresses.
</p>

<pre caption="Examples for /etc/conf.d/net">
<comment># For DHCP</comment>
config_eth0=( "dhcp" )

<comment># For static IP using CIDR notation</comment>
config_eth0=( "192.168.0.7/24" )
routes_eth0=( "default via 192.168.0.1" )

<comment># For static IP using netmask notation</comment>
config_eth0=( "192.168.0.7 netmask 255.255.255.0" )
routes_eth0=( "default gw 192.168.0.1" )
</pre>

<note>
If you do not specify a configuration for your interface then DHCP is assumed.
</note>

<note>
CIDR stands for Classless InterDomain Routing.<br/>
Originally, IPv4 addresses were classified as A, B, or C.
The early classification system did not envision the massive popularity of the
Internet, and is in danger of running out of new unique addresses. CIDR is an
addressing scheme that allows one IP address to designate many IP addresses.
A CIDR IP address looks like a normal IP address except that it ends with a
slash followed by a number; for example, 192.168.0.0/16.
CIDR is described in <uri link="http://rfc.net/rfc1519.html";>RFC 1519</uri>.
</note>

<p>
Now that we have configured our interface, we can start and stop it using the
below commands
</p>

<pre caption="Starting and stopping network scripts">
# <i>/etc/init.d/net.eth0 start</i>
# <i>/etc/init.d/net.eth0 stop</i>
</pre>

<impo>
When troubleshooting networking, it is recommended to set RC_VERBOSE="yes"
in <path>/etc/conf.d/rc</path> so that you get more information about what's
happening
</impo>

<p>
Now that you have successfully started and stopped your network interface, you
may wish to get it to start when Gentoo boots. Here's how to do this. The last
"rc" command instructs Gentoo to start any scripts in the current runlevel
that have not yet been started.
</p>

<pre caption="Configuring a network interface to load at boot time">
# <i>rc-update add net.eth0 default</i>
# <i>rc</i>
</pre>

</body>
</section>

</sections>



1.1                  xml/htdocs/doc/en/handbook/hb-net-wireless.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo

Index: hb-net-wireless.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->

<sections>

<version>1.0</version>
<date>2005-06-06</date>

<section>
<title>Introduction</title>
<body>

<p>
Currently we support wireless setup either by wireless-tools or
wpa_supplicant. The important thing to remember is that you configure for
wireless networks on a global basis and not an interface basis.
</p>

<p>
wpa_suppliant is the best choice, but it does not support all drivers.
For a list of supported drivers,
<uri link="http://hostap.epitest.fi/wpa_supplicant";>read the wpa_supplicant
site</uri>. Also, wpa_supplicant can currently only connect to SSID's that
you have configured for.
</p>

<p>
wireless-tools supports nearly all cards and drivers, but it cannot connect
to WPA only Access Points.
</p>

<warn>
The linux-wlan-ng driver is not supported by baselayout at this time.
This is because linux-wlan-ng have their own setup and configuration
which is completely different to everyone else's. The linux-wlan-ng devs
are rumoured to be changing their setup over to wireless-tools - when this
happens you may use linux-wlan-ng with baselayout.
</warn>

</body>
</section>

<section>
<title>WPA Supplicant</title>
<body>
<p>
<uri link="http://hostap.epitest.fi/wpa_supplicant";>WPA Supplicant</uri> is
a package that allows you to connect to WPA enabled access points. It's setup
is fairly fluid as it is still in beta - however it works fine for the most
part.
</p>

<pre caption="Install wpa_supplicant">
# <i>emerge net-wireless/wpa_supplicant</i>
</pre>

<impo>
You have to have CONFIG_PACKET enabled in your kernel for wpa_supplicant to work
</impo>

<p>
Now we have to configure <path>/etc/conf.d/net</path> to so that we prefer
wpa_supplicant over wireless-tools (if both are installed, wireless-tools
is the default).
</p>

<pre caption="configure /etc/conf.d/net for wpa_supplicant">
<comment># Prefer wpa_supplicant over wireless-tools</comment>
modules=( "wpa_supplicant" )

<comment># It's important that we tell wpa_supplicant which driver we should
# be using as it's not very good at guessing yet</comment>
wpa_supplicant_eth0="-Dmadwifi"
</pre>

<note>
If you're using the host-ap driver you will need to put the card in Managed
mode before it can be used with wpa_supplicant correctly. You can use
<e>iwconfig_eth0="mode managed"</e> to achieve this in
<c>/etc/conf.d/net</c>.
</note>

<p>
That was simple wasn't it? However, we still have to configure wpa_supplicant
itself which is a bit more tricky depending on how secure the Access Points
are that you are trying to connect to. The below example is taken and
simplified from <path>/etc/wpa_supplicant.conf.example</path> which ships
with wpa_supplicant.
</p>

<pre caption="an example /etc/wpa_supplicant.conf">
<comment># The below line not be changed otherwise we refuse to work</comment>
ctrl_interface=/var/run/wpa_supplicant

<comment># Ensure that only root can read the WPA configuration</comment>
ctrl_interface_group=0

<comment># Let wpa_supplicant take care of scanning and AP selection</comment>
ap_scan=1

<comment># Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid 
ciphers</comment>
network={
        ssid="simple"
        psk="very secret passphrase"
        <comment># The higher the priority the sooner we are matched</comment>
        priority=5
}

<comment># Same as previous, but request SSID-specific scanning (for APs that 
reject
# broadcast SSID)</comment>
network={
        ssid="second ssid"
        scan_ssid=1
        psk="very secret passphrase"
        priority=2
}

<comment># Only WPA-PSK is used. Any valid cipher combination is 
accepted</comment>
network={
        ssid="example"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP WEP104 WEP40
        psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
        priority=2
}

<comment># Plaintext connection (no WPA, no IEEE 802.1X)</comment>
network={
        ssid="plaintext-test"
        key_mgmt=NONE
}

<comment># Shared WEP key connection (no WPA, no IEEE 802.1X)</comment>
network={
        ssid="static-wep-test"
        key_mgmt=NONE
        wep_key0="abcde"
        wep_key1=0102030405
        wep_key2="1234567890123"
        wep_tx_keyidx=0
        priority=5
}

<comment># Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
# IEEE 802.11 authentication</comment>
network={
        ssid="static-wep-test2"
        key_mgmt=NONE
        wep_key0="abcde"
        wep_key1=0102030405
        wep_key2="1234567890123"
        wep_tx_keyidx=0
        priority=5
        auth_alg=SHARED
}

<comment># IBSS/ad-hoc network with WPA-None/TKIP</comment>
network={
        ssid="test adhoc"
        mode=1
        proto=WPA
        key_mgmt=WPA-NONE
        pairwise=NONE
        group=TKIP
        psk="secret passphrase"
}
                                                        
</pre>                                                                  

</body>
</section>

<section>
<title>Wireless Tools</title>

<subsection>
<title>Initial setup and Managed Mode</title>
<body>

<p>
<uri link="http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html";>
Wireless Tools</uri> provide a generic way to configure basic wireless
interfaces up to the WEP security level. While WEP is a weak security method
it's also the most prevalent.
</p>

<p>
Wireless Tools configuration is controlled by a few main variables. The
sample configuration file below should describe all you need. One thing to
bear in mind is that no configuration means "connect to the strongest
unencrypted Access Point" - we will always try and connect you to something.
</p>

<pre caption="Install wireless-tools">
        <<Truncated>>


-- 
[email protected] mailing list

Reply via email to