1,2c1,2
< .\" 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 $
20c20,23
< 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.
26,28c29,34
< 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.
>
30,31c36,43
< 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.
>
33,34c45,48
< 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.
38,39c52,53
< Can act as server which accept incoming \fIPPP\fR connection.
<
---
> Can act as server which accept incoming \fIPPP\fR connection.
>
45,46c59,60
< 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.
49,50c63,66
< 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.
52a69,72
> o Tunnel driver supports bpf. That is, user can use tcpdump to check
> packet flow over the \fIPPP\fR link.
>
> .TP 2
61,62c81,82
< 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.
65d84
< .LP
68a88,92
> -- 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>
70,73c94,97
< 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
75c99
< ppp>
---
> ppp ON tama>
77c101
< ppp> term
---
> ppp ON tama> term
89c113
< ppp>
---
> ppp on tama>
94c118
< PPP> show lcp
---
> PPP ON tama> show lcp
98c122
< PPP> show ipcp
---
> PPP ON tama> show ipcp
104c128
< PPP> add 0 0 HISADDR
---
> PPP ON tama> add 0 0 HISADDR
108c132
< PPP>
---
> PPP ON tama>
111c135
< PPP> show log
---
> PPP ON tama> show log
115c139
< PPP> close
---
> PPP ON tama> close
119c143
< ppp> quit
---
> ppp ON tama> quit
121a146
>
125,126c150,152
< 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.)
145c171,174
< 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.
153c182
< ppp> dial
---
> ppp ON tama> dial
156c185
< PPP>
---
> PPP ON tama>
158,159c187,189
< 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
---
> 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.
160a191
>
164,165c195,198
< 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)
166a200
>
172,173c206,207
< 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.
174a209
>
177c212
< PPP> show ipcp
---
> PPP on tama> show ipcp
181,182c216,222
< 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.
183a224
>
186c227
< PPP> close
---
> PPP on tama> close
294,295c335,341
< \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.
296a343
>
298,299c345,346
< 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.
300a348
>
305c353,354
< 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.
314,315c363,364
< 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.
318,319c367,369
< 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.
323,326c373,376
< 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.
327a378
>
331c382,383
< 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
334,335c386,388
< 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.
338,339c391,393
< 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.
344,345c398,399
< 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.
348,349c402,403
< 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.
352,353c406,407
< 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.
391c445
< Please refer /etc/ppp/example/ppp.conf.iij for some real examples.
---
> Please refer /etc/ppp/ppp.conf.iij for some real examples.
397,398c451,452
< \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
399a454
>
416c471
< HDLC
---
> .B HDLC
423,425c478,480
< ``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''.
452,455c507,509
< 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.
458c512
< .B $HOME/ppp/.ppp.[linkup|secret]
---
> .B $HOME/ppp/.ppp.[conf|linkup|secret]
484,485d537
< A Proxy arp is not support, yet.
< The TTS is little bit longer than pppd2.1, it's under improving ;-)
488,489c540,541
< 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).
< .\" 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 $
20c20,23
< 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.
26,28c29,34
< 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.
>
30,31c36,43
< 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.
>
33,34c45,48
< 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.
38,39c52,53
< Can act as server which accept incoming \fIPPP\fR connection.
<
---
> Can act as server which accept incoming \fIPPP\fR connection.
>
45,46c59,60
< 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.
49,50c63,66
< 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.
52a69,72
> o Tunnel driver supports bpf. That is, user can use tcpdump to check
> packet flow over the \fIPPP\fR link.
>
> .TP 2
61,62c81,82
< 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.
65d84
< .LP
68a88,92
> -- 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>
70,73c94,97
< 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
75c99
< ppp>
---
> ppp ON tama>
77c101
< ppp> term
---
> ppp ON tama> term
89c113
< ppp>
---
> ppp on tama>
94c118
< PPP> show lcp
---
> PPP ON tama> show lcp
98c122
< PPP> show ipcp
---
> PPP ON tama> show ipcp
104c128
< PPP> add 0 0 HISADDR
---
> PPP ON tama> add 0 0 HISADDR
108c132
< PPP>
---
> PPP ON tama>
111c135
< PPP> show log
---
> PPP ON tama> show log
115c139
< PPP> close
---
> PPP ON tama> close
119c143
< ppp> quit
---
> ppp ON tama> quit
121a146
>
125,126c150,152
< 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.)
145c171,174
< 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.
153c182
< ppp> dial
---
> ppp ON tama> dial
156c185
< PPP>
---
> PPP ON tama>
158,159c187,189
< 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
---
> 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.
160a191
>
164,165c195,198
< 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)
166a200
>
172,173c206,207
< 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.
174a209
>
177c212
< PPP> show ipcp
---
> PPP on tama> show ipcp
181,182c216,222
< 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.
183a224
>
186c227
< PPP> close
---
> PPP on tama> close
294,295c335,341
< \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.
296a343
>
298,299c345,346
< 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.
300a348
>
305c353,354
< 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.
314,315c363,364
< 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.
318,319c367,369
< 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.
323,326c373,376
< 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.
327a378
>
331c382,383
< 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
334,335c386,388
< 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.
338,339c391,393
< 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.
344,345c398,399
< 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.
348,349c402,403
< 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.
352,353c406,407
< 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.
391c445
< Please refer /etc/ppp/example/ppp.conf.iij for some real examples.
---
> Please refer /etc/ppp/ppp.conf.iij for some real examples.
397,398c451,452
< \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
399a454
>
416c471
< HDLC
---
> .B HDLC
423,425c478,480
< ``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''.
452,455c507,509
< 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.
458c512
< .B $HOME/ppp/.ppp.[linkup|secret]
---
> .B $HOME/ppp/.ppp.[conf|linkup|secret]
484,485d537
< A Proxy arp is not support, yet.
< The TTS is little bit longer than pppd2.1, it's under improving ;-)
488,489c540,541
< 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).