svn commit: r43004 - head/en_US.ISO8859-1/books/handbook/ppp-and-slip
Dru Lavigne
dru at FreeBSD.org
Fri Oct 18 20:50:46 UTC 2013
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 @@
<title>Configuring <acronym>PPP</acronym></title>
<para>&os; provides built-in support for managing dial-up
- <acronym>PPP</acronym> connections using &man.ppp.8;. In order
+ <acronym>PPP</acronym> connections using &man.ppp.8;. The
+ default &os; kernel provides support for
+ <devicename>tun</devicename> 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, <command>ppp</command> is
+ used to start and manage connections.</para>
+
+ <para>In order
to use a <acronym>PPP</acronym> connection, the following items
are needed:</para>
@@ -198,7 +206,7 @@
</note>
<sect2 id="userppp-staticIP">
- <title>PPP With Static <acronym>IP</acronym> Addresses</title>
+ <title>PPP With a Static <acronym>IP</acronym> Address</title>
<indexterm>
<primary>PPP</primary>
@@ -431,8 +439,8 @@
</sect2>
<sect2 id="userppp-dynamicIP">
- <title><acronym>PPP</acronym> With Dynamic
- <acronym>IP</acronym> Addresses</title>
+ <title><acronym>PPP</acronym> With a Dynamic
+ <acronym>IP</acronym> Address</title>
<indexterm>
<primary><acronym>PPP</acronym></primary>
@@ -445,94 +453,28 @@
</indexterm>
<para>If the <acronym>IP</acronym> address changes whenever
- a connection is made, configure <command>ppp</command> to
- negotiate the local and remote addresses. This is done by
- <quote>guessing</quote> an <acronym>IP</acronym> address
- and allowing <command>ppp</command> to set it up correctly
- using the <acronym>IP</acronym> Configuration Protocol
- (IPCP) after connecting. The
- <filename>ppp.conf</filename> configuration is the same as
- that described in <xref linkend="userppp-staticIP"/>, with
- the following change:</para>
-
- <programlisting>17 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0</programlisting>
-
- <para>Again, do not include the line number, it is just for
- reference. Indentation of at least one space is
- required.</para>
+ a connection is made, change the <literal>set ifaddr</literal> line
+ in <filename>/etc/ppp/ppp.conf</filename> to the following value.
+ This tells &man.ppp.8; to use the
+ <acronym>IP</acronym> Configuration Protocol
+ (<acronym>IPCP</acronym>) to negotiate the <acronym>IP</acronym> address.</para>
- <variablelist>
- <varlistentry>
- <term>Line 17:</term>
-
- <listitem>
- <para>The number after the <literal>/</literal>
- character is the number of bits of the address that
- ppp will insist on. Other <acronym>IP</acronym>
- addresses can be used, but the above example will
- always work.</para>
-
- <para>The last argument (<literal>0.0.0.0</literal>)
- tells PPP to start negotiations using address
- <hostid role="ipaddr">0.0.0.0</hostid> rather than
- <hostid role="ipaddr">10.0.0.1</hostid> and is
- necessary for some <acronym>ISP</acronym>s. Do not
- use <literal>0.0.0.0</literal> as the first argument
- to <command>set ifaddr</command> as it prevents
- PPP from setting up an initial route in
- <option>-auto</option> mode.</para>
- </listitem>
- </varlistentry>
- </variablelist>
+ <programlisting>set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0</programlisting>
<para>When not running in <option>-auto</option> mode,
- create an entry in
- <filename>/etc/ppp/ppp.linkup</filename> as this file is
+ create
+ <filename>/etc/ppp/ppp.linkup</filename> with the following lines. This file is
used after a connection has been established. At this
- point, <command>ppp</command> will have assigned the
- interface addresses and it will now be possible to add the
- routing table entries:</para>
-
- <programlisting>1 provider:
-2 add default HISADDR</programlisting>
-
- <variablelist>
- <varlistentry>
- <term>Line 1:</term>
-
- <listitem>
- <para>On establishing a connection,
- <command>ppp</command> will look for an entry in
- <filename>ppp.linkup</filename> according to the
- following rules: First, try to match the same label
- as we used in <filename>ppp.conf</filename>. If
- that fails, look for an entry for the
- <acronym>IP</acronym> address of our gateway. This
- entry is a four-octet <acronym>IP</acronym> style
- label. If we still have not found an entry, look
- for the <literal>MYADDR</literal> entry.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Line 2:</term>
-
- <listitem>
- <para>This line tells <command>ppp</command> to add a
- default route that points to
- <literal>HISADDR</literal>.
- <literal>HISADDR</literal> will be replaced with the
- <acronym>IP</acronym> number of the gateway as
- negotiated by the IPCP.</para>
- </listitem>
- </varlistentry>
- </variablelist>
+ point, the <acronym>IP</acronym> address will have been assigned
+ and it will now be possible to add the
+ routing table entries. The <literal>HISADDR</literal> line will be replaced with the
+ <acronym>IP</acronym> address of the default gateway as
+ negotiated using <acronym>IPCP</acronym>. Make sure that
+ <replaceable>provider</replaceable> matches the value
+ used in <filename>ppp.conf</filename>.</para>
- <para>See the <literal>pmdemand</literal> entry in the files
- <filename>/usr/share/examples/ppp/ppp.conf.sample</filename>
- and
- <filename>/usr/share/examples/ppp/ppp.linkup.sample</filename>
- for a detailed example.</para>
+ <programlisting>provider:
+ add default HISADDR</programlisting>
</sect2>
<sect2>
@@ -543,44 +485,47 @@
<secondary>receiving incoming calls</secondary>
</indexterm>
- <para>When configuring <application>ppp</application> 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 <acronym>IP</acronym> address from
- the LAN's subnet, and use <command>enable
- proxy</command> in the
+ <para>When configuring &man.ppp.8; to
+ receive incoming calls on a machine connected to a Local
+ Area Network (<acronym>LAN</acronym>),
+ decide if packets should be forwarded to the <acronym>LAN</acronym>. If so,
+ allocate the connecting system an <acronym>IP</acronym> address from
+ the <acronym>LAN</acronym>'s subnet, and add the <command>enable
+ proxy</command> line to
<filename>/etc/ppp/ppp.conf</filename>.
- Alsom confirm that <filename>/etc/rc.conf</filename>
+ Also, confirm that <filename>/etc/rc.conf</filename>
contains the following line:</para>
<programlisting>gateway_enable="YES"</programlisting>
- </sect2>
-
- <sect2>
- <title>Which getty?</title>
-
- <para><xref linkend="dialup"/> provides a good description
- on enabling dial-up services using &man.getty.8;.</para>
-
- <para>An alternative to <command>getty</command> is <ulink
- url="http://mgetty.greenie.net/">mgetty</ulink> (from
- <filename role="package">comms/mgetty+sendfax</filename>
- port), a smarter version of <command>getty</command>
- designed with dial-up lines in mind.</para>
+
+ <para>Refer to &man.ppp.8; and
+ <filename>/usr/share/examples/ppp/ppp.conf.sample</filename>
+ for more details. The following steps will also be required:</para>
+
+ <procedure>
+ <step>
+ <para>Create an entry in <filename>/etc/passwd</filename>
+ (using the &man.vipw.8; program).</para>
+ </step>
- <para>The advantages of using <command>mgetty</command> is
- that it actively <emphasis>talks</emphasis> to modems,
- meaning if port is turned off in
- <filename>/etc/ttys</filename> then the modem will not
- answer the phone.</para>
+ <step>
+ <para>Create a profile in this users home directory that
+ runs <command>ppp -direct direct-server</command> or
+ similar.</para>
+ </step>
- <para>Later versions of <command>mgetty</command> (from
- 0.99beta onwards) also support the automatic detection of
- <acronym>PPP</acronym> streams, allowing clients
- scriptless access to the server.</para>
+ <step>
+ <para>Create an entry in
+ <filename>/etc/ppp/ppp.conf</filename>. The
+ <filename>direct-server</filename> example should
+ suffice.</para>
+ </step>
- <para>Refer to <xref linkend="userppp-mgetty"/> for more
- information on <command>mgetty</command>.</para>
+ <step>
+ <para>Create an entry in
+ <filename>/etc/ppp/ppp.linkup</filename>.</para>
+ </step>
+ </procedure>
</sect2>
<sect2>
@@ -765,6 +710,28 @@ mary:
<indexterm>
<primary>LCP</primary>
</indexterm>
+ <para><xref linkend="dialup"/> provides a good description
+ on enabling dial-up services using &man.getty.8;.</para>
+
+ <para>An alternative to <command>getty</command> is <ulink
+ url="http://mgetty.greenie.net/">mgetty</ulink> (from
+ <filename role="package">comms/mgetty+sendfax</filename>
+ port), a smarter version of <command>getty</command>
+ designed with dial-up lines in mind.</para>
+
+ <para>The advantages of using <command>mgetty</command> is
+ that it actively <emphasis>talks</emphasis> to modems,
+ meaning if port is turned off in
+ <filename>/etc/ttys</filename> then the modem will not
+ answer the phone.</para>
+
+ <para>Later versions of <command>mgetty</command> (from
+ 0.99beta onwards) also support the automatic detection of
+ <acronym>PPP</acronym> streams, allowing clients
+ scriptless access to the server.</para>
+
+ <para>Refer to <xref linkend="userppp-mgetty"/> for more
+ information on <command>mgetty</command>.</para>
<para>By default the <filename
role="package">comms/mgetty+sendfax</filename> port
@@ -1101,96 +1068,6 @@ ifconfig_tun0=</programlisting>
<screen>&prompt.root; <userinput>ppp -auto provider</userinput></screen>
</sect2>
-
- <sect2>
- <title>Summary</title>
-
- <para>To recap, the following steps are necessary when setting
- up ppp for the first time:</para>
-
- <para>Client side:</para>
-
- <procedure>
- <step>
- <para>Ensure that the <devicename>tun</devicename> device
- is built into the kernel.</para>
- </step>
-
- <step>
- <para>Ensure that the <filename
- class="devicefile">tun<replaceable>N</replaceable></filename>
- device file is available in the <filename
- class="directory">/dev</filename> directory.</para>
- </step>
-
- <step>
- <para>Create an entry in
- <filename>/etc/ppp/ppp.conf</filename>. The
- <filename>pmdemand</filename> example should suffice
- for most <acronym>ISP</acronym>s.</para>
- </step>
-
- <step>
- <para>When using a dynamic <acronym>IP</acronym> address,
- create an entry in
- <filename>/etc/ppp/ppp.linkup</filename>.</para>
- </step>
-
- <step>
- <para>Update your <filename>/etc/rc.conf</filename>
- file.</para>
- </step>
-
- <step>
- <para>Create a <filename>start_if.tun0</filename> script
- if demand dialing is required.</para>
- </step>
- </procedure>
-
- <para>Server side:</para>
-
- <procedure>
- <step>
- <para>Ensure that the <devicename>tun</devicename> device
- is built into the kernel.</para>
- </step>
-
- <step>
- <para>Ensure that the
- <filename
- class="devicefile">tun<replaceable>N</replaceable></filename>
- device file is available in the <filename
- class="directory">/dev</filename> directory.</para>
- </step>
-
- <step>
- <para>Create an entry in <filename>/etc/passwd</filename>
- (using the &man.vipw.8; program).</para>
- </step>
-
- <step>
- <para>Create a profile in this users home directory that
- runs <command>ppp -direct direct-server</command> or
- similar.</para>
- </step>
-
- <step>
- <para>Create an entry in
- <filename>/etc/ppp/ppp.conf</filename>. The
- <filename>direct-server</filename> example should
- suffice.</para>
- </step>
-
- <step>
- <para>Create an entry in
- <filename>/etc/ppp/ppp.linkup</filename>.</para>
- </step>
-
- <step>
- <para>Update <filename>/etc/rc.conf</filename>.</para>
- </step>
- </procedure>
- </sect2>
</sect1>
<sect1 id="ppp-troubleshoot">
More information about the svn-doc-all
mailing list