New user Process PPP based on iij-ppp0.94beta2.

   o Supporting SYNC SIO device (But need a device driver)
     - add "set speed sync"
   o Fixing bug for Predictor-1 function.
   o Add new parameter that re-sent interval for set timeout commands.
   o Improving RTT (Round Trip Time) and reducing processor time.
     - Previous Timer service was using polling, and now using
       SIGALRM ;-)
     - A 0.94beta2 will not work correctly....

   -- Follows are additinal feature not including 0.94beta2
   o Support Proxy ARP
     - add "enable/disable proxy" commands
   o Marging common routine in CHAP/PAP.
   o Enhancing LCP/IPCP log information.
   o Support local Authfication connection on port 300x and tty.
     - You can set up pair of your "hostname -s" and
       password in ppp.secret. if either ppp.secret file nor
       your hostname line don't exist, It will notify a message
       and working as same as previous version.(Backword compatibility)
     - If you did set up them, It's allow connection but nothing to do
       except help and passwd command.
     - add "passwd yourpasswd" commands
   o Support afilter - keep Alive filter that a packet can send/receiving
     according to ifilter/ofilter but doesn't count it as preventing idle
     timer expires.
     - Same syntax of other filters.
   o Fixing bugs reported by current user for previous one. Thanks !!

Reviewed by: Atsushi Murai (amurai@spec.co.jp)

1 files changed, 140 insertions, 88 deletions

diff --git a/usr.sbin/ppp/ppp.8.m4 b/usr.sbin/ppp/ppp.8.m4
index b46eed1..9cf384e 100644
--- a/usr.sbin/ppp/ppp.8.m4
+++ b/usr.sbin/ppp/ppp.8.m4
@@ -1,5 +1,5 @@
-.\" manual page [] for ppp 0.93
-.\" $Id:$
+.\" manual page [] for ppp 0.94 beta2 + alpha
+.\" $Id: ppp.8,v 1.1.1.1 1995/01/31 06:29:58 amurai Exp $
 .\" SH section heading
 .\" SS subsection heading
 .\" LP paragraph
@@ -17,37 +17,57 @@ ppp \- Point to Point Protocol (aka iijppp)
 ]
 .SH DESCRIPTION
 .LP
- This is user process \fIPPP\fR software package. Normally, \fIPPP\fR is implemented as a part of kernel and hard to debug and/or modify its behavior. However, in this implementation, \fIPPP\fR is implemented as a user process with the help of tunnel device driver.
+This is user process \fIPPP\fR software package. Normally, \fIPPP\fR
+is implemented as a part of kernel and hard to debug and/or modify its
+behavior. However, in this implementation, \fIPPP\fR is implemented as
+a user process with the help of tunnel device driver.
 .LP
 
 .SH Major Features
 
 .TP 2
-o
-Provide interactive user interface. Using its command mode, user can easily enter commands to establish the connection with the peer, check the status of connection, and close the connection.                         
-                                                                                
+o Provide interactive user interface. Using its command mode, user can
+easily enter commands to establish the connection with the peer, check
+the status of connection, and close the connection.  And now, all
+functions has password protected if describe your hostname/password in
+secret file or exist secret file itself.
+
 .TP 2
-o
-Supports both of manual and automatic dialing. Interactive mode has ``term'' command which enables you to talk to your modem directory. When your modem is connected to the peer, and it starts to speak \fIPPP\fR, \fIPPP\fR software detects it and turns into packet mode automatically. Once you have convinced how to connect with the peer, you can write chat script to define necessary dialing and login procedure for later convenience.                                                                
+o Supports both of manual and automatic dialing. Interactive mode has
+``term'' command which enables you to talk to your modem
+directory. When your modem is connected to the peer, and it starts to
+speak \fIPPP\fR, \fIPPP\fR software detects it and turns into packet
+mode automatically. Once you have convinced how to connect with the
+peer, you can write chat script to define necessary dialing and login
+procedure for later convenience.
+
 .TP 2
-o
-Supports on-demand dialup capability. By using auto mode, \fIPPP\fR program will act as a daemon and wait for the packet send to the peer. Once packet is found, daemon automatically dials and establish the connection. 
+o Supports on-demand dialup capability. By using auto mode, \fIPPP\fR
+program will act as a daemon and wait for the packet send to the peer. 
+Once packet is found, daemon automatically dials and establish the
+connection.
 
 .TP 2
 o
-Can act as server which accept incoming \fIPPP\fR connection.                     
-
+Can act as server which accept incoming \fIPPP\fR connection. 
+                 
 .TP 2
 o
 Supports PAP and CHAP authentification.                                     
 
 .TP 2
-o 
-Supports packet filtering. User can define three kinds of filters; ifilter for incoming packet, ofilter for outgoing packet and dfilter to define dialing trigger packet.
+o
+Supports Proxy Arp.
 
 .TP 2
-o
-Tunnel driver supports bpf. That is, user can use tcpdump to check packet flow over the \fIPPP\fR link.
+o Supports packet filtering. User can define four kinds of filters;
+ifilter for incoming packet, ofilter for outgoing packet, dfilter to
+define dialing trigger packet and afilter to keep alive a connection
+by trigger packet.
+
+.TP 2
+o Tunnel driver supports bpf. That is, user can use tcpdump to check
+packet flow over the \fIPPP\fR link.
 
 .TP 2
 o
@@ -58,23 +78,27 @@ o
 Supports IETF draft Predictor-1 compression.
 
 .TP 2
-o
-Runs under BSDI-1.1 and FreeBSD-1.1. Patch for NeXTSTEP 3.2 is also available on the net. 
+o Runs under BSDI-1.1 and FreeBSD-1.1. Patch for NeXTSTEP 3.2 is also
+available on the net.
 
 .SH MANUAL DIALING
-.LP
 
    % ppp
    User Process PPP written by Toshiharu OHNO.
+   -- If you write your hostname and password in ppp.secret,
+      you can't do anything even quit command --
+   ppp on tama> quit
+   what ?
+   ppp on tama> pass <password>
    -- You can specify modem and device name using following commands.
-   ppp> set line /dev/cua01
-   ppp> set speed 38400
-   ppp> set parity even
-   ppp> show modem
+   ppp ON tama> set line /dev/cua01
+   ppp ON tama> set speed 38400
+   ppp ON tama> set parity even
+   ppp ON tama> show modem
    -- Modem related parameters are shown in here
-   ppp>
+   ppp ON tama>
    -- Use term command to talk with your modem
-   ppp> term
+   ppp ON tama> term
    at
    OK
    atdt123456
@@ -86,44 +110,46 @@ Runs under BSDI-1.1 and FreeBSD-1.1. Patch for NeXTSTEP 3.2 is also available on
 
    -- When peer start to speak PPP, the program will detect it
    -- automatically and back to command mode.
-   ppp>
+   ppp on tama>
    \fBPPP\fR>
 
    -- NOW, you are get connected !! Note that prompt has changed to
    -- capital letters
-   PPP> show lcp
+   PPP ON tama> show lcp
 
    -- You'll see LCP status --
 
-   PPP> show ipcp
+   PPP ON tama> show ipcp
 
    -- You'll see IPCP status --
    -- At this point, your machine has host route to the peer.
    -- If your want to add default route entry, then enter
 
-   PPP> add 0 0 HISADDR
+   PPP ON tama> add 0 0 HISADDR
 
    -- Here string `HISADDR' represents IP address of connected peer.
 
-   PPP>
+   PPP ON tama>
    -- Use applications (i.e. ping, telnet, ftp) in other windows
 
-   PPP> show log
+   PPP ON tama> show log
 
    -- Gives you some logging messages
 
-   PPP> close
+   PPP ON tama> close
 
    -- Connection is closed, and modem will be hanged.
 
-   ppp> quit
+   ppp ON tama> quit
    %
 .LP
+
 .SH AUTOMATIC DIALING
 
 .LP
-To use automatic dialing, you must prepare Dial and Login chat script.See example definition found in ppp.conf.sample(Format of ppp.conf is pretty simple.)
-.LP
+To use automatic dialing, you must prepare Dial and Login chat script.
+See example definition found in ppp.conf.sample (Format of ppp.conf is
+pretty simple.)
 
 .TP 2
 o
@@ -142,7 +168,10 @@ o
 Command line must contains space or tab at first column.
 
 .LP
-If ppp.conf is ready, specify destination label name when you invoke ppp. Commands associated with destination label is executed when ppp command is invoked. Note that commands associated with ``default'' label is ALWAYS executed.
+If ppp.conf is ready, specify destination label name when you invoke
+ppp. Commands associated with destination label is executed when ppp
+command is invoked. Note that commands associated with ``default''
+label is ALWAYS executed.
 
 Once connection is made, you'll find that prompt is changed to
 
@@ -150,40 +179,52 @@ Once connection is made, you'll find that prompt is changed to
 
    % ppp pm2
    ...
-   ppp> dial
+   ppp ON tama> dial
    dial OK!
    login OK!
-   PPP>
+   PPP ON tama>
+
+If ppp.linkup file is available, its contents are executed when
+\fIPPP\fR link is connected.  See example which add default route.
+The string HISADDR matches with IP address of connected peer.
 
-If ppp.linkup file is available, its contents are executed when \fIPPP\fR link is connected.  See example which add default route.  The string HISADDR matches with IP address of connected peer.
-.LP
 
 .SH DAIL ON DEMAND
 
 .LP
- To play with demand dialing, you must use -auto option. Also, you must specify destination label with proper setup in ppp.conf. It must contain ``ifaddr'' command to define peer's IP address. (refer /etc/ppp/ppp.conf.sample)
-.LP
+ To play with demand dialing, you must use -auto option. Also, you
+must specify destination label with proper setup in ppp.conf. It must
+contain ``ifaddr'' command to define peer's IP address. (refer
+/etc/ppp/ppp.conf.sample)
+
 
    % ppp -auto pm2demand
    ...
    %
 
 .LP
-When -auto is specified, \fIPPP\fR program works as a daemon.  But, you are still able to use command features to check its behavior.
-.LP
+When -auto is specified, \fIPPP\fR program works as a daemon.  But,
+you are still able to use command features to check its behavior.
+
 
   % telnet localhost 3000
   ...
-  PPP> show ipcp
+  PPP on tama> show ipcp
   ....
 
 .LP
- Each ppp has associated port number, which is computed as "3000 + tunnel_device_number". If 3000 is not good base number, edit defs.h.  When packet toward to remote network is detected, \fIPPP\fR will take dialing action and try to connect with the peer. If dialing is failed, program will wait for 30 seconds. Once this hold time expired, another trigger packet cause dialing action. Note that automatic re-dialing is NOT implemented.
-.LP
+ Each ppp has associated port number, which is computed as "3000 +
+tunnel_device_number". If 3000 is not good base number, edit defs.h.
+When packet toward to remote network is detected, \fIPPP\fR will take
+dialing action and try to connect with the peer. If dialing is failed,
+program will wait for 30 seconds. Once this hold time expired, another
+trigger packet cause dialing action. Note that automatic re-dialing is
+NOT implemented.
+
 
  To terminate program, use
 
-  PPP> close
+  PPP on tama> close
   \fBppp\fR> quit all
 
 .LP
@@ -291,18 +332,26 @@ ppp:*:21:0:PPP Login User:/home/ppp:/usr/local/bin/ppplogin
 .SH Controlling IP address
 
 .LP
- \fIPPP\fR uses IPCP to negotiate IP addresses. Each side of node informs IP address that willing to use to the peer, and if requested IP address is acceptable, \fIPPP\fR returns ACK to requester. Otherwise, \fIPPP\fR returns NAK to suggest the peer to use different IP address. When both side of nodes agrees to accept the received request (and send ACK), IPCP is reached to open state and network level connection is established.
-.LP
+ \fIPPP\fR uses IPCP to negotiate IP addresses. Each side of node
+informs IP address that willing to use to the peer, and if requested
+IP address is acceptable, \fIPPP\fR returns ACK to
+requester. Otherwise, \fIPPP\fR returns NAK to suggest the peer to use
+different IP address. When both side of nodes agrees to accept the
+received request (and send ACK), IPCP is reached to open state and
+network level connection is established.
+
 
 .LP
- To control, this IPCP behavior, this implementation has ``set ifaddr'' to define MY and HIS IP address.
-.LP
+ To control, this IPCP behavior, this implementation has ``set
+ifaddr'' to define MY and HIS IP address.
+
 
 .TP3
 ifaddr src_addr dst_addr
 
 .LP
- Where, src_addr is the IP address that my side is willing to use, and dst_addr is the IP address which his side should use.
+Where, src_addr is the IP address that my side is willing to use, and
+dst_addr is the IP address which his side should use.
 .LP
 
 .TP3
@@ -311,46 +360,51 @@ ifaddr 192.244.177.38 192.244.177.2
 For example, above specification means
 
 .TP
-o
-I strongly want to use 192.244.177.38 as my side. I'll disagree when peer suggest me to use other addresses.
+o I strongly want to use 192.244.177.38 as my side. I'll disagree when
+peer suggest me to use other addresses.
 
 .TP 2
-o
-I strongly insists peer to use 192.244.177.2 as his side address.  I don't permit him to use any IP address but 192.244.177.2.  When peer request other IP address, I always suggest him to use 192.244.177.2.
+o I strongly insists peer to use 192.244.177.2 as his side address.  I
+don't permit him to use any IP address but 192.244.177.2.  When peer
+request other IP address, I always suggest him to use 192.244.177.2.
 
 .LP
  This is all right, when each side has pre-determined IP address.
-However, it is often the case one side is acting as a server which 
-controls IP address and the other side should obey the direction from him.
-In order to allow more flexible behavior, `ifaddr' command allows user to specify IP address more loosely.
-.LP
+However, it is often the case one side is acting as a server which
+controls IP address and the other side should obey the direction from
+him.  In order to allow more flexible behavior, `ifaddr' command
+allows user to specify IP address more loosely.
+
 
 .TP 2
 ifaddr 192.244.177.38/24 192.244.177.2/20
 
- Number followed by slash (/) represents number of bits significant in IP address. That is, this example means
+ Number followed by slash (/) represents number of bits significant in
+IP address. That is, this example means
 
 .TP 2
-o
-I'd like to use 192.244.177.38 as my side address, if it is possible.  But I also accept any IP address between 192.244.177.0 and 192.244.177.255.
+o I'd like to use 192.244.177.38 as my side address, if it is
+possible.  But I also accept any IP address between 192.244.177.0 and
+192.244.177.255.
  
 .TP 2
-o
-I'd like to make him to use 192.244.177.2 as his side address.  But I also permit him to use any IP address between 192.244.176.0 and 192.244.191.255.
+o I'd like to make him to use 192.244.177.2 as his side address.  But
+I also permit him to use any IP address between 192.244.176.0 and
+192.244.191.255.
 
  Notes:
 
 .TP 2
-o
-As you may have already noticed, 192.244.177.2 is equivalent to say 192.244.177.2/32.
+o As you may have already noticed, 192.244.177.2 is equivalent to say
+192.244.177.2/32.
 
 .TP 2
-o
-As an exception, 0 is equivalent to 0.0.0.0/0. Means, I have no idea about IP address and obey what he says.
+o As an exception, 0 is equivalent to 0.0.0.0/0. Means, I have no idea
+about IP address and obey what he says.
 
 .TP 2
-o
-192.244.177.2/0 means that I'll accept/permit any IP address but I'll try to insist to use 192.244.177.2 at first.
+o 192.244.177.2/0 means that I'll accept/permit any IP address but
+I'll try to insist to use 192.244.177.2 at first.
 
 .SH Connecting with service provider
 
@@ -388,14 +442,15 @@ add next lines into your ppp.conf.
 .TP 3
 
 .LP
-Please refer /etc/ppp/example/ppp.conf.iij for some real examples.
+Please refer /etc/ppp/ppp.conf.iij for some real examples.
 .LP
 
 .SH Logging facility
 
 .LP
- \fI\fIPPP\fR\fR is able to generate following level log info as /var/log/ppp.log
-.LP
+ \fI\fIPPP\fR\fR is able to generate following level log info as
+/var/log/ppp.log
+
 
 .TP
 .B Phase
@@ -413,16 +468,16 @@ Generate LCP/IPCP packet trace
 .B TCP/IP
 Dump TCP/IP packet
 .TP 
-HDLC
+.B HDLC
 Dump HDLC packet in hex
 .TP 
 .B Async
 Dump async level packet in hex
 
 .LP
- ``set debug'' command allows you to set logging output level,
-and multiple levels can be specified.
-Default is equivalent to ``set debug phase lcp''.
+``set debug'' command allows you to set logging output level, and
+multiple levels can be specified.  Default is equivalent to ``set
+debug phase lcp''.
 
 .SH For more details
 
@@ -449,13 +504,12 @@ Please contact to author if you need old driver code.
 .SH FILES
 .LP
 \fIPPP\fR may refers three files, ppp.conf, ppp.linkup and ppp.secret.
-These files are placed in /etc/ppp,
-but user can create his own files under HOME directory as .ppp.conf,
-.ppp.linkup and .ppp.secret.
-the ppp always try to consult to user's personal setup first.
+These files are placed in /etc/ppp, but user can create his own files
+under HOME directory as .ppp.conf,.ppp.linkup and .ppp.secret.the ppp
+always try to consult to user's personal setup first.
 
 .TP
-.B $HOME/ppp/.ppp.[linkup|secret]
+.B $HOME/ppp/.ppp.[conf|linkup|secret]
 User depend configuration files.
 
 .TP
@@ -481,12 +535,10 @@ Logging and debug information file.
 tty port locking file.
 
 .SH BUGS
-A Proxy arp is not support, yet.
-The TTS is little bit longer than pppd2.1, it's under improving ;-)
 
 .SH HISTORY
-This programm has deliverd into core since FreeBSD-2.1 
-by Atsushi Murai (amurai@spec.co.jp).
+This programm has deliverd into core since FreeBSD-2.1 by Atsushi
+Murai (amurai@spec.co.jp).
 
 .SH AUTHORS
 Toshiharu OHNO (tony-o@iij.ad.jp)