Changeset 782820d

Timestamp:

03/12/2008 11:52:02 AM (16 years ago)

Author:

Alexander E. Patrakov <alexander@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

0fb3692

Parents:

a90bc8c

Message:

Added dialup and GPRS/EDGE configuration instructions to the PPP page.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@7258 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:

• connect/dialup/ppp.xml (modified) (7 diffs)
• introduction/welcome/changelog.xml (modified) (1 diff)

connect/dialup/ppp.xml

@@ -60 +60 @@
 
     <bridgehead renderas="sect4">Optional</bridgehead>
-    <para role="optional"><xref linkend="libpcap"/> (needed to do PPP filtering)
+    <para role="optional"><xref linkend="libpcap"/> (needed to do PPP filtering),
+    <xref linkend="linux-pam"/> (to authenticate incoming calls using PAM),
     and <ulink url="http://linux-atm.sourceforge.net/">Linux ATM</ulink> (to
     build the pppoatm.so plugin)</para>
@@ -73 +74 @@
 
     <note id="ppp-kernel">
-      <para><application>PPP</application> support must be
-      compiled into the kernel or available as a kernel module.</para>
+      <para><application>PPP</application> support (CONFIG_PPP),
+      the asynchronous line discipline (CONFIG_PPP_ASYNC), and the
+      driver for your serial port device must be
+      compiled into the kernel or loaded as a kernel module.
+      Udev doesn't load the ppp_generic module automatically, it must be
+      mentioned in the <filename>/etc/sysconfig/modules</filename> file.</para>
     </note>
 
@@ -91 +96 @@
     <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
 
-<screen role='root'><userinput>make install &amp;&amp;
-make install-etcppp</userinput></screen>
+<screen role='root'><userinput>groupadd -g 52 pppusers &amp;&amp;
+make install &amp;&amp;
+<!-- FIXME: is "make install-etcppp" needed for KPPP/WvDial?
+The example configuration below overwrites two of three files, and
+already includes the "lock" option in each peer file
+-->make install-etcppp &amp;&amp;
+install -m755 scripts/{pon,poff,plog} /usr/bin &amp;&amp;
+instal -m644 scripts/pon.1 /usr/share/man/man1</userinput></screen>
 
   </sect2>
@@ -101 +112 @@
     <para><command>make install-etcppp</command>: This command puts example
     configuration files in <filename class="directory">/etc/ppp</filename>.</para>
+
+<!-- FIXME: the three options below are taken from pppd/Makefile.linux file.
+     They have not been tested. There are other options, such as USE_SRP=y,
+     that cannot work (in this case, because libsrp is not available from
+     anywhere) - Alexander E. Patrakov -->
+
+    <para><parameter>USE_PAM=y</parameter>: Add this argument to the
+    <command>make</command> command to compile in support for PAM, usually
+    needed for authenticating inbound calls against a central database.</para>
+
+    <para><parameter>HAVE_INET6=y</parameter>: Add this argument to the
+    <command>make</command> command to compile in support for IPv6.</para>
+
+    <para><parameter>CBCP=y</parameter>: Add this argument to the
+    <command>make</command> command to compile in support for
+    Microsoft proprietary Callback Control Protocol.</para>
 
   </sect2>
@@ -121 +148 @@
       <title>Configuration Information</title>
 
-      <para>The <application>PPP</application> daemon requires very little
-      configuration. The main trick is scripting the connection. This can be done
+      <para>The <application>PPP</application> daemon requires some
+      configuration. The main trick is scripting the connection.
+      For dialup and GPRS connections, this can be done
       either using the <command>chat</command> program which comes with
-      this package or by using <xref linkend="wvdial"/>.</para>
-
+      this package, or by using external tools such as <xref linkend="wvdial"/>
+      or <application>KPPP</application> from
+      <xref linkend="kdenetwork"/>. The text below explains how to set up
+      <!-- PPPoE, --> dialup and GPRS connections using only tools provided with
+      the <application>PPP</application> package. All configuration steps
+      in this section are executed as
+      <systemitem class="username">root</systemitem> user.</para>
+
+    <sect4>
+      <title>Setting the passwords</title>
+
+      <para>Passwords are stored in <filename>/etc/ppp/pap-secrets</filename>
+      and <filename>/etc/ppp/chap-secrets</filename> files, depending on the
+      authentication method used by the ISP. If in doubt, place the password
+      into both files. E.g., if the username given by the ISP is
+      <quote>jdoe</quote>, the password is <quote>guessit</quote>, the
+      ISP uses PAP and the user wants to name this account
+      <quote>dialup</quote> in order to distinguish it from other PPP accounts,
+      the following file has to be created:</para>
+<screen role="root"><userinput>touch /etc/ppp/pap-secrets
+chmod 600 /etc/ppp/pap-secrets
+cat &gt;&gt;/etc/ppp/pap-secrets &lt;&lt;"EOF"</userinput>
+<literal># username      remotename    password        IP for the peer
+jdoe            dialup        guessit         *</literal>
+<userinput>EOF</userinput></screen>
+    </sect4>
+
+    <sect4>
+      <title>DNS Server Configuration</title>
+
+      <para>If you don't run your own caching DNS server, create a simple
+      <command>ip-up</command> script (to be called by <command>pppd</command>
+      automatically once the connection is brought up) that populates the
+      <filename>/etc/resolv.conf</filename> file with nameservers specified
+      by the ISP.</para>
+<screen role="root"><userinput>cat &gt;/etc/ppp/ip-up &lt;&lt;"EOF"</userinput>
+<literal>#!/bin/sh
+if [ "$USEPEERDNS" = "1" ] &amp;&amp; [ -s /etc/ppp/resolv.conf ]
+then
+        install -m 644 /etc/ppp/resolv.conf /etc/resolv.conf
+fi</literal>
+<userinput>EOF
+chmod 755 /etc/ppp/ip-up</userinput></screen>
+      <para>If you use a caching DNS server such as <xref linkend="bind"/>
+      or <ulink url="http://www.phys.uu.nl/~rombouts/pdnsd.html">Pdnsd</ulink>,
+      the script above is wrong for you. In such case, write your
+      own script that tells your caching nameserver to forward queries to
+      upstream DNS servers specified in the $DNS1 and $DNS2 environment
+      variables.</para>
+      <!-- FIXME: write the replacement script that works with Bind -->
+    </sect4>
+
+    <sect4>
+      <title>Dialup Modem Connection</title>
+<!-- This section has been tested with various ISPs in Yekaterinburg,
+     Russia using Lucent WinModem. I cannot test it anymore, because
+     there is no free PCI slot for the modem in my new computer. However,
+     it is similar enough to GPRS for me to be sure that it still works,
+     and nobody complained about non-working dialup on the LFS LiveCD.
+     - Alexander E. Patrakov -->
+
+      <para>Dialup connections are established with the help of a modem
+      connected to a computer and the telephone line. The modem dials a
+      telephone number of the ISP's modem, and they exchange data using
+      the signal frequencies 300-4000 Hz. Typical data transfer
+      rate is 40-50 kilobits per second, and the gateway ping time
+      (latency) is up to 300-400 ms. In order to configure the
+      dialup connection, it is required to know the telephone number of
+      the ISP's modem pool, the username and the password.</para>
+
+      <para>In order to configure a dialup connection, two files have to
+      be created: a chat script that automates the connection procedure
+      (common for all dialup accounts), and a peer file that provides
+      configuration information about a specific connection to
+      <command>pppd</command>:</para>
+<screen role="root"><userinput>cat $gt;/etc/ppp/dialup.chat &lt;&lt;"EOF"</userinput>
+<literal>ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE'
+ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
+ABORT ERROR ABORT BLACKLISTED
+
+TIMEOUT 5
+'' AT
+# \T is the phone number, passed from /etc/ppp/peers/<replaceable>dialup</replaceable>
+OK-+++\dATH0-OK ATD\T
+TIMEOUT 75
+CONNECT \d\c</literal>
+<userinput>EOF
+
+cat &gt;/etc/ppp/peers/<replaceable>dialup</replaceable> &lt;&lt;"EOF"</userinput>
+<literal># Your username at the ISP
+user "<replaceable>jdoe</replaceable>"
+# What should be in the second column in /etc/ppp/*-secrets
+remotename "<replaceable>dialup</replaceable>"
+# Replace <replaceable>TTTTTTT</replaceable> with the ISP phone number
+connect "/usr/sbin/chat -T <replaceable>TTTTTTT</replaceable> -f /etc/ppp/dialup.chat"
+
+# Specify your modem serial port and speed below
+<replaceable>/dev/ttyS0</replaceable>
+<replaceable>115200</replaceable>
+
+# The settings below usually don't need to be changed
+updetach
+noauth
+hide-password
+debug
+lock
+defaultroute
+noipdefault
+usepeerdns</literal>
+<userinput>EOF</userinput></screen>
+
+      <para>The first three lines of the
+      <filename>/etc/ppp/dialup.chat</filename> file abort the script when
+      it receives an indication of an error from the modem. Then the timeout
+      is set to 5 seconds and the script checks that the modem responds to
+      the dummy AT command at all. If not, measures are taken to dewedge it
+      (by interrupting the data transfer and going on hook). Then the
+      telephone number is dialed, and the script waits for the answer for
+      75 seconds. The serial connection is considered established when the
+      modem sends the string CONNECT.</para>
+
+    </sect4>
+
+    <sect4>
+      <title>GPRS and EDGE Connections</title>
+<!-- This section has been tested with GPRS service from MOTIV in
+     Yekaterinburg, Russia. According to forum messages, the procedure
+     also works with EDGE, but my cellular phone (Motorola C350) does not
+     support EDGE. - Alexander E. Patrakov -->
+
+      <para>GPRS and EDGE connections are established with the help of a
+      cellular phone connected to a computer via serial or USB cable, or
+      using Bluetooth.
+      The phone exchanges data packets with the nearest base station,
+      which can be up to 35 kilometers away.
+
+      <!-- FIXME: watch for new standards! SkyLink is already offering
+           3.1 megabits per second with CDMA mobile phones, and
+           the configuration below doesn't work. It is reported that
+           a regular dialup setup with the telephone number "#777",
+           username "mobile" and password "internet" works with SkyLink. -->
+
+      The maximum possible data transfer rate is 170 kilobits per second
+      for GPRS and 474 kilobits per second for EDGE, but many cellular
+      operators impose lower limits, such as 64 kilobits per second. The
+      gateway ping time is 900 ms for GPRS, which makes playing many online
+      games impossible and causes connection to ICQ to be unreliable.
+      In order to configure a GPRS or EDGE connection,
+      it is required to know the access point name (APN) and, rarely, the
+      username and the password.
+      In most cases, billing is based on the telephone number, and the
+      username/password pair is not needed, as assumed in the example
+      below.</para>
+
+      <para>In order to configure a GPRS connection, two files have to
+      be created: a chat script that automates the connection procedure
+      (common for all GPRS accounts), and a peer file that provides
+      configuration information about a specific connection to
+      <command>pppd</command>:</para>
+<screen role="root"><userinput>cat &gt;/etc/ppp/gprs.chat &lt;&lt;"EOF"</userinput>
+<literal>ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE'
+ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
+ABORT ERROR ABORT BLACKLISTED
+
+TIMEOUT 5
+'' AT
+OK-+++\dATH0-OK ATZ
+# \T is the APN, passed from /etc/ppp/peers/<replaceable>gprs</replaceable>
+# This example stores the APN as profile #1 in the phone.
+# The telephone number, *99***&lt;profile_number&gt;#, is always the same
+# If you want to store this as profile #2, change 1 to 2 in the
+# following two lines.
+OK AT+CGDCONT=<replaceable>1</replaceable>,"IP","\T"
+OK "ATD*99***<replaceable>1</replaceable>#"
+CONNECT \d\c</literal>
+<userinput>EOF
+
+cat &gt;/etc/ppp/peers/<replaceable>gprs</replaceable> &lt;&lt;"EOF"</userinput>
+<literal># Replace <replaceable>inet.example.com</replaceable> with the proper APN for your provider
+connect "/usr/sbin/chat -T <replaceable>inet.example.com</replaceable> -f /etc/ppp/gprs.chat"
+
+# Specify your cellphone serial port and speed below
+# Note: you must manually send some vendor-specific AT commands
+# to certain old cellular phones (such as Sony-Ericsson T200)
+# in order to achieve connection speed more than 9600 bits ber second.
+<replaceable>/dev/ttyS1</replaceable>
+<replaceable>115200</replaceable>
+
+# The settings below usually don't need to be changed
+noccp
+noauth
+updetach
+debug
+lock
+defaultroute
+noipdefault
+usepeerdns</literal>
+<userinput>EOF</userinput></screen>
+    </sect4>
+
+    <sect4>
+      <title>Establishing the connection</title>
+
+      <para>In order to establish a PPP connection described by the
+      <filename>/etc/ppp/peers/<replaceable>peername</replaceable></filename>
+      file, run, as root or as a member of the
+      <systemitem class="groupname">pppusers</systemitem> group:</para>
+<screen><userinput>pon <replaceable>peername</replaceable></userinput></screen>
+
+      <para>In order to tear the connection down, run:</para>
+<screen><userinput>poff <replaceable>peername</replaceable></userinput></screen>
+
+    </sect4>
     </sect3>
 
@@ -139 +378 @@
 
       <seglistitem>
-        <seg>chat, pppd, pppdump, pppoe-discovery and pppstats</seg>
+        <seg>chat, pon, poff, plog, pppd, pppdump, pppoe-discovery and pppstats</seg>
         <seg>Several plugin modules installed in
-        <filename class='directory'>/usr/lib/pppd/2.4.3</filename></seg>
+        <filename class='directory'>/usr/lib/pppd/&ppp-version;</filename></seg>
         <seg>/etc/ppp, /usr/include/pppd and /usr/lib/pppd</seg>
       </seglistitem>
@@ -164 +403 @@
       </varlistentry>
 
+      <varlistentry id="pon">
+        <term><command>pon</command></term>
+        <listitem>
+          <para>is the script that establishes a PPP connection</para>
+          <indexterm zone="ppp pon">
+            <primary sortas="b-pon">pon</primary>
+          </indexterm>
+        </listitem>
+      </varlistentry>
+
+     <varlistentry id="poff">
+        <term><command>poff</command></term>
+        <listitem>
+          <para>is the script that tears a PPP connection down.</para>
+          <indexterm zone="ppp poff">
+            <primary sortas="b-poff">poff</primary>
+          </indexterm>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry id="plog">
+        <term><command>plog</command></term>
+        <listitem>
+          <para>is a script that prints the tail of the PPP log.</para>
+          <indexterm zone="ppp plog">
+            <primary sortas="b-plog">plog</primary>
+          </indexterm>
+        </listitem>
+      </varlistentry>
+
+
       <varlistentry id="pppd">
         <term><command>pppd</command></term>

introduction/welcome/changelog.xml

@@ -44 +44 @@
       <para>March 12th, 2008</para>
       <itemizedlist>
+        <listitem>
+          <para>[alexander] - Added dialup and GPRS configuration instructions
+          to the PPP page.</para>
+        </listitem>
         <listitem>
           <para>[dj] - Updated to OpenLDAP-2.3.39.</para>