1This directory contains a set of scripts which have been used on Linux 2as well as Solaris 2.x systems to initiate or maintain a connection 3with PPP. The files in this directory were contributed by Al Longyear 4(longyear@netcom.com) and Adi Masputra (adi.masputra@sun.com) 5 6------------------------------------------------------------------------ 7 81. README 9 10This file. You are reading it. It is just documentation. 11 12------------------------------------------------------------------------ 13 142. ppp-on 15 16This script will initiate a connection to the PPP system. It will run 17the chat program with the connection script as a parameter. This is a 18possible security hole. However, it is simple. It is meant to replace 19the previous version of ppp-on which was not very functional. 20 21The ppp-on script has entries for the account name, password, IP 22addresses, and telephone numbers. The parameters are passed to the 23pppd process and, then in turn, to the second part of the connect 24script, as a set of environment variables. 25 26Please make sure that you put the full path name to the ppp-on-dialer 27script in the reference to it in ppp-on. 28 29------------------------------------------------------------------------ 30 313. ppp-on-dialer 32 33This is the second part to the simple calling script, ppp-on. It 34executes the chat program to connect the user with a standard UNIX 35style getty/login connection sequence. 36 37------------------------------------------------------------------------ 38 394. callback 40 41This script may be used in lieu of the ppp-on-dialer to permit the 42common modem callback sequence. You may need to make changes to the 43expected prompt string for the modem. 44 45The script works by disabling the system's detection of the DCD 46condition and working on the modem status message "NO CARRIER" which 47is generated when the modem disconnects. 48 49It is crude. It does work for my modem connection. Use as you see fit. 50 51------------------------------------------------------------------------ 52 535. redialer 54 55The redialer script is a replacement for the ppp-on-dialer script. It 56will do 'attack dialing' or 'demon dialing' of one or more telephone 57numbers. The first number which responds will be used for a 58connection. 59 60There is a limit of ten attempts and a 15 second delay between dialing 61attempts. Both values are set in the script. 62 63------------------------------------------------------------------------ 64 656. ppp-off 66 67This is a script which will terminate the active ppp connection. Use 68as either "ppp-off" to terminate ppp0, or "ppp-off <device>" to 69terminate the connection on <device>. For example, "ppp-off ppp2" will 70terminate the ppp2 connection. 71 72------------------------------------------------------------------------ 73 747. secure-card 75 76This script was written by Jim Isaacson <jcisaac@crl.com>. It is a script 77for the 'expect' programming language used with Tcl. You need to have 78expect and Tcl installed before this script may be used. 79 80This script will operate with a device marketed under the name "SecureCARD". 81This little device is mated with its controller. On the credit card size 82device, there is a sequence number which changes on a random basis. In order 83for you to connect you need to enter a fixed portion of your account name 84and the number which is displayed on this card device. The number must match 85the value at the controller in order for the account name to be used. 86 87The problem is that chat uses fixed response strings. In addition, the 88timing for running the script may prevent the use of a script that reads the 89value before it starts the dial sequence. What was needed was a script which 90asked the user at the user's console at the time that it is needed. 91 92This led to the use of expect. 93 94------------------------------------------------------------------------ 95 968. ppp-on-rsh 97 98This script will initiate a PPP connection to a remote machine using rsh. 99This is implemented by creating a master/slave pseudo-tty with the slave 100pointing to rsh, specifically with the 'pty' and 'notty' options of pppd. 101It is assumed that the remote machine contains some sort of trust 102mechanisms (such as ~/.rhosts, et al) to allow the local machine to 103connect via rsh as root. 104 105------------------------------------------------------------------------ 106 1079. ppp-on-ssh 108 109This script will initiate a PPP connection to a remote machine using the 110secure shell, or ssh. I've only tested this on ssh 1.x, so those of you 111who are running ssh 2.x mahy need to modify the ssh options slightly. 112This is implemented by creating a master/slave pseudo-ttyt with the slave 113pointing to ssh, specifically with the 'pty' and 'notty' options of pppd. 114It is assumed that the remote machine can accept the ssh connection from 115the local host, in the sense that all ssh authentication mechanisms have 116been properly configured, so that a remote root user can open a ssh 117connection. 118 119------------------------------------------------------------------------ 120 12110. options-rsh-loc & options-rsh-rem 122 123These options files accompany the ppp-on-rsh script mentioned above. In 124theory, you'd want to copy the options-rsh-rem to the remote machine where 125in.rshd is running. The only extra option required on the remote machine 126options file is the 'notty' option. In addition, all ASCII control characters 127[0x00 to 0x1f], plus 0xff, are escaped. This may need to be modified 128depending on the rsh (or pseudo-tty) implementation which may differ across 129platforms, for further optimizations. 130 131------------------------------------------------------------------------ 132 13311. options-ssh-loc & options-ssh-rem 134 135These options files accompany the ppp-on-ssh script mentioned above. I've 136only tested this on ssh 1.x, so those of you who are running ssh 2.x need 137to modify the ssh options slightly. In theory, you'd want to copy the 138options-ssh-rem to the remote machine where sshd daemon is running. The only 139extra options required on the remote machine options file is the 'notty' 140option. In addition, all ASCII control characters [0x00 to 0x1f], plus 0xff, 141are escaped. This may need to be modified depending on the ssh (or 142pseudo-tty) implementation which may differ across platforms, for further 143optimizations. 144