From owner-svn-doc-head@FreeBSD.ORG Fri Oct 18 20:50:46 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5A9B93A4; Fri, 18 Oct 2013 20:50:46 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 39DE12D04; Fri, 18 Oct 2013 20:50:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r9IKok70004471; Fri, 18 Oct 2013 20:50:46 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r9IKok57004470; Fri, 18 Oct 2013 20:50:46 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310182050.r9IKok57004470@svn.freebsd.org> From: Dru Lavigne Date: Fri, 18 Oct 2013 20:50:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43004 - head/en_US.ISO8859-1/books/handbook/ppp-and-slip X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Oct 2013 20:50:46 -0000 Author: dru Date: Fri Oct 18 20:50:45 2013 New Revision: 43004 URL: http://svnweb.freebsd.org/changeset/doc/43004 Log: Begin shuffling content to divide it into basic configuration, advanced configuration, authentication, and dial-ins instead of dial-outs. More shuffling to come. Add more to the intro to help make sense of how everything fits together. General tightening and clarification in sections 26.2.2 and 26.2.3. White space fix won't occur until after next shuffling is complete. Modified: head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Fri Oct 18 19:37:57 2013 (r43003) +++ head/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Fri Oct 18 20:50:45 2013 (r43004) @@ -109,7 +109,15 @@ Configuring <acronym>PPP</acronym> &os; provides built-in support for managing dial-up - PPP connections using &man.ppp.8;. In order + PPP connections using &man.ppp.8;. The + default &os; kernel provides support for + tun which is used to interact with a + modem hardware. Configuration is performed by editing at least + one configuration file, and configuration files containing + examples are provided. Finally, ppp is + used to start and manage connections. + + In order to use a PPP connection, the following items are needed: @@ -198,7 +206,7 @@ - PPP With Static <acronym>IP</acronym> Addresses + PPP With a Static <acronym>IP</acronym> Address PPP @@ -431,8 +439,8 @@ - <acronym>PPP</acronym> With Dynamic - <acronym>IP</acronym> Addresses + <acronym>PPP</acronym> With a Dynamic + <acronym>IP</acronym> Address PPP @@ -445,94 +453,28 @@ If the IP address changes whenever - a connection is made, configure ppp to - negotiate the local and remote addresses. This is done by - guessing an IP address - and allowing ppp to set it up correctly - using the IP Configuration Protocol - (IPCP) after connecting. The - ppp.conf configuration is the same as - that described in , with - the following change: - - 17 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 - - Again, do not include the line number, it is just for - reference. Indentation of at least one space is - required. + a connection is made, change the set ifaddr line + in /etc/ppp/ppp.conf to the following value. + This tells &man.ppp.8; to use the + IP Configuration Protocol + (IPCP) to negotiate the IP address. - - - Line 17: - - - The number after the / - character is the number of bits of the address that - ppp will insist on. Other IP - addresses can be used, but the above example will - always work. - - The last argument (0.0.0.0) - tells PPP to start negotiations using address - 0.0.0.0 rather than - 10.0.0.1 and is - necessary for some ISPs. Do not - use 0.0.0.0 as the first argument - to set ifaddr as it prevents - PPP from setting up an initial route in - mode. - - - + set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 When not running in mode, - create an entry in - /etc/ppp/ppp.linkup as this file is + create + /etc/ppp/ppp.linkup with the following lines. This file is used after a connection has been established. At this - point, ppp will have assigned the - interface addresses and it will now be possible to add the - routing table entries: - - 1 provider: -2 add default HISADDR - - - - Line 1: - - - On establishing a connection, - ppp will look for an entry in - ppp.linkup according to the - following rules: First, try to match the same label - as we used in ppp.conf. If - that fails, look for an entry for the - IP address of our gateway. This - entry is a four-octet IP style - label. If we still have not found an entry, look - for the MYADDR entry. - - - - - Line 2: - - - This line tells ppp to add a - default route that points to - HISADDR. - HISADDR will be replaced with the - IP number of the gateway as - negotiated by the IPCP. - - - + point, the IP address will have been assigned + and it will now be possible to add the + routing table entries. The HISADDR line will be replaced with the + IP address of the default gateway as + negotiated using IPCP. Make sure that + provider matches the value + used in ppp.conf. - See the pmdemand entry in the files - /usr/share/examples/ppp/ppp.conf.sample - and - /usr/share/examples/ppp/ppp.linkup.sample - for a detailed example. + provider: + add default HISADDR @@ -543,44 +485,47 @@ receiving incoming calls - When configuring ppp to - receive incoming calls on a machine connected to a LAN, - decide if packets should be forwarded to the LAN. If so, - allocate the peer an IP address from - the LAN's subnet, and use enable - proxy in the + When configuring &man.ppp.8; to + receive incoming calls on a machine connected to a Local + Area Network (LAN), + decide if packets should be forwarded to the LAN. If so, + allocate the connecting system an IP address from + the LAN's subnet, and add the enable + proxy line to /etc/ppp/ppp.conf. - Alsom confirm that /etc/rc.conf + Also, confirm that /etc/rc.conf contains the following line: gateway_enable="YES" - - - - Which getty? - - provides a good description - on enabling dial-up services using &man.getty.8;. - - An alternative to getty is mgetty (from - comms/mgetty+sendfax - port), a smarter version of getty - designed with dial-up lines in mind. + + Refer to &man.ppp.8; and + /usr/share/examples/ppp/ppp.conf.sample + for more details. The following steps will also be required: + + + + Create an entry in /etc/passwd + (using the &man.vipw.8; program). + - The advantages of using mgetty is - that it actively talks to modems, - meaning if port is turned off in - /etc/ttys then the modem will not - answer the phone. + + Create a profile in this users home directory that + runs ppp -direct direct-server or + similar. + - Later versions of mgetty (from - 0.99beta onwards) also support the automatic detection of - PPP streams, allowing clients - scriptless access to the server. + + Create an entry in + /etc/ppp/ppp.conf. The + direct-server example should + suffice. + - Refer to for more - information on mgetty. + + Create an entry in + /etc/ppp/ppp.linkup. + + @@ -765,6 +710,28 @@ mary: LCP + provides a good description + on enabling dial-up services using &man.getty.8;. + + An alternative to getty is mgetty (from + comms/mgetty+sendfax + port), a smarter version of getty + designed with dial-up lines in mind. + + The advantages of using mgetty is + that it actively talks to modems, + meaning if port is turned off in + /etc/ttys then the modem will not + answer the phone. + + Later versions of mgetty (from + 0.99beta onwards) also support the automatic detection of + PPP streams, allowing clients + scriptless access to the server. + + Refer to for more + information on mgetty. By default the comms/mgetty+sendfax port @@ -1101,96 +1068,6 @@ ifconfig_tun0= &prompt.root; ppp -auto provider - - - Summary - - To recap, the following steps are necessary when setting - up ppp for the first time: - - Client side: - - - - Ensure that the tun device - is built into the kernel. - - - - Ensure that the tunN - device file is available in the /dev directory. - - - - Create an entry in - /etc/ppp/ppp.conf. The - pmdemand example should suffice - for most ISPs. - - - - When using a dynamic IP address, - create an entry in - /etc/ppp/ppp.linkup. - - - - Update your /etc/rc.conf - file. - - - - Create a start_if.tun0 script - if demand dialing is required. - - - - Server side: - - - - Ensure that the tun device - is built into the kernel. - - - - Ensure that the - tunN - device file is available in the /dev directory. - - - - Create an entry in /etc/passwd - (using the &man.vipw.8; program). - - - - Create a profile in this users home directory that - runs ppp -direct direct-server or - similar. - - - - Create an entry in - /etc/ppp/ppp.conf. The - direct-server example should - suffice. - - - - Create an entry in - /etc/ppp/ppp.linkup. - - - - Update /etc/rc.conf. - - -