Running the asppp2pppd Conversion Script (Tasks)

The /usr/sbin/asppp2pppd script copies the PPP information in /etc/asppp.cf and PPP-related UUCP files to appropriate locations in the Solaris PPP 4.0 files.

Task Prerequisites

Before doing the next task, you should have done the following:

• Installed the Oracle Solaris release on the machine that also has the asppp and UUCP configuration files

• Become superuser on the machine with the PPP files, for example, the machine mojave

How to Convert From asppp to Solaris PPP 4.0

1. Start the conversion script.

   # /usr/sbin/asppp2pppd

   The conversion process starts and gives you the following screen output.

   This script provides only a suggested translation for your existing aspppd
   configuration.  You will need to evaluate for yourself whether the translation
   is appropriate for your operating environment.
   Continue [Yn]? 

2. Type “Y” to continue.

   You receive the following output.

   Chat cannot do echo checking; requests for this removed.
   Adding 'noauth' to /etc/ppp/options
   
   Preparing to write out translated configuration:
       1 chat file:
           1.  /etc/ppp/chat.Pgobi.hayes
       2 option files:
           2.  /etc/ppp/peers/Pgobi
           3.  /etc/ppp/options
       1 script file:
           4.  /etc/ppp/demand

   The new Solaris PPP 4.0 files have been generated.

How to View the Results of the Conversion

You can view the Solaris PPP 4.0 files that were created by the /usr/sbin/asppp2pppd conversion script at the end of the conversion process. The script displays the following list of options.

Enter option number:
        1 - view contents of file on standard output
        2 - view contents of file using /usr/bin/less
        3 - edit contents of file using /usr/bin/vi
        4 - delete/undelete file from list
        5 - rename file in list
        6 - show file list again
        7 - escape to shell (or "!")
        8 - abort without saving anything
        9 - save all files and exit (default)
Option:

1. Type 1 to view the contents of the files on the screen.

   The script requests the number of the file you want to view.

   File number (1 .. 4):

   The numbers refer to the translated files that are listed during the conversion process, as shown in the previous Step 2.

2. Type 1 to view the chat file /etc/ppp/chat.Pgobi.hayes.

   File number (1 .. 4):  1
   "" \d\dA\p\pTE1V1X1Q0S2=255S12=255\r\c
   OK\r ATDT\T\r\c
   CONNECT \c
   in:--in: mojave
   word: sand

   The chat script contains the modem “chat” information that appears on the hayes line in the sample /etc/uucp/Dialers file. /etc/ppp/chat.Pgobi.hayes also contains the login sequence for Pgobi that appears in the sample /etc/uucp/Systems file. The chat script is now in the /etc/ppp/chat.Pgobi.hayes file.

3. Type 2 to view the peers file, /etc/ppp/peers/Pgobi.

   File number (1 .. 4):  2
   /dev/cua/b
   38400
   demand
   idle 120
   connect "/usr/bin/chat -f /etc/ppp/chat.Pgobi.hayes -T '15551212'"
   user NeverAuthenticate
   mojave:gobi

   The serial port information (/dev/cua/b) is from the /etc/uucp/Devices file. The link speed, idle time, authentication information, and peer names are from the /etc/asppp.cf file. “demand” refers to the “demand” script, to be called when the dial-out machine tries to connect to peer Pgobi.

4. Type 3 to view the /etc/ppp/options file that are created for dial-out machine mojave.

   File number (1 .. 4):  3
   #lock
   noauth

   The information in /etc/ppp/options is from the /etc/asppp.cf file.

5. Type 4 to view the contents of the demand script.

   File number (1 .. 4):  4
   /usr/bin/pppd file /etc/ppp/peers/Pgobi

   This script, when invoked, runs the pppd command, which then reads the /etc/ppp/peers/Pgobi to initiate the link between mojave and Pgobi.

6. Type 9 to save the created files. Then exit the conversion script.