$Id: ppp.8,v 1.31 1997/05/04 02:39:04 ache Exp $
.Dd 20 September 1995 .Os FreeBSD .Dt PPP 8 .Sh NAME .Nm ppp .Nd Point to Point Protocol (aka iijppp) .Sh SYNOPSIS .Nm .Op Fl auto | background | ddial | direct | dedicated .Op Fl alias .Op Ar system .Sh DESCRIPTION This is a user process .Em PPP software package. Normally, .Em PPP is implemented as a part of the kernel (e.g. as managed by pppd) and it's thus somewhat hard to debug and/or modify its behavior. However, in this implementation .Em PPP is done as a user process with the help of the tunnel device driver (tun). .Sh Major Features l -diag t Provides interactive user interface. Using its command mode, the user can easily enter commands to establish the connection with the remote end, check the status of connection and close the connection. All functions can also be optionally password protected for security. t Supports both manual and automatic dialing. Interactive mode has a .Dq term command which enables you to talk to your modem directly. When your modem is connected to the remote peer and it starts to talk .Em PPP , the .Em PPP software detects it and switches to packet mode automatically. Once you have determined the proper sequence for connecting with the remote host, you can write a chat script to define the necessary dialing and login procedure for later convenience. t Supports on-demand dialup capability. By using auto mode, .Nm will act as a daemon and wait for a packet to be sent over the .Em PPP link. When this happens, the daemon automatically dials and establishes the connection. In almost the same manner ddial mode (dedicated or demon dialing) also automatically dials and establishes the connection. However, it differs in that it will dial the remote site any time it detects the link is down, even if there are no packets to be sent. This mode is useful for full-time connections who worry less about line charges and more about being connected full time. t Supports packet aliasing. Packet aliasing, more commonly known as masquerading, allows computers on a private, unregistered network to access the internet. The .Em PPP host acts as a masquerading gateway. IP addresses as well as TCP and UDP port numbers are aliased for outgoing packets and de-aliased for returning packets. t Supports background PPP connections. In background mode, if .Nm successfully establishes the connection, it will become a daemon. Otherwise, it will exit with an error. t Supports server-side PPP connections. Can act as server which accepts incoming .Em PPP connections. t Supports PAP and CHAP authentication. t Supports Proxy Arp. When .Em PPP is set up as server, you can also configure it to do proxy arp for your connection. t Supports packet filtering. User can define four kinds of filters: .Em ifilter for incoming packets, .Em ofilter for outgoing packets, .Em dfilter to define a dialing trigger packet and .Em afilter for keeping a connection alive with the trigger packet. t Tunnel driver supports bpf. The user can use .Xr tcpdump 1 to check the packet flow over the .Em PPP link. t Supports PPP over TCP capability. t Supports IETF draft Predictor-1 compression. .Nm supports not only VJ-compression but also Predictor-1 compression. Normally, a modem has built-in compression (e.g. v42.bis) and the system may receive higher data rates from it as a result of such compression. While this is generally a good thing in most other situations, this higher speed data imposes a penalty on the system by increasing the number of serial interrupts the system has to process in talking to the modem and also increases latency. Unlike VJ-compression, Predictor-1 compression pre-compresses .Em all data flowing through the link, thus reducing overhead to a minimum. t Supports Microsofts IPCP extentions. Name Server Addresses and NetBIOS Name Server Addresses can be negotiated with clients using the Microsoft .Em PPP stack (ie. Win95, WinNT) t Runs under BSDI-1.1 and FreeBSD. .El Patches for NeXTSTEP 3.2 are also available on the net. .Sh GETTING STARTED When you first run .Nm you may need to deal with some initial configuration details. First, your kernel should include a tunnel device (the default in FreeBSD 2.0.5 and later). If it doesn't, you'll need to rebuild your kernel with the following line in your kernel configuration file: .Dl pseudo-device tun 1 You should set the numeric field to the maximum number of .Em PPP connections you wish to support. Second, check your
a /dev directory for the tunnel device entry
a /dev/tun0. If it doesn't exist, you can create it by running "MAKEDEV tun0" .Sh MANUAL DIALING % .Nm User Process PPP written by Toshiharu OHNO. * If you set your hostname and password in
a /etc/ppp/ppp.secret , you can't do anything except run the quit and help commands * ppp on "your hostname"> help passwd : Password for security quit : Quit the PPP program help : Display this message ppp on tama> pass <password> * "on" will change to "ON" if you specify the correct password. * ppp ON tama> * You can now specify the device name, speed and parity for your modem, and whether CTS/RTS signalling should be used (CTS/RTS is used by default). If your hardware does not provide CTS/RTS lines (as may happen when you are connected directly to certain ppp-capable terminal servers), .Nm will never send any output through the port; it waits for a signal which never comes. Thus, if you have a direct line and can't seem to make a connection, try turning ctsrts off: * ppp ON tama> set line /dev/cuaa0 ppp ON tama> set speed 38400 ppp ON tama> set parity even ppp ON tama> set ctsrts on ppp ON tama> show modem * Modem related parameters are shown in here * ppp ON tama> * Use term command to talk with your modem * ppp ON tama> term at OK atdt123456 CONNECT login: ppp Password: * PPP started in remote side. When the peer start to talk PPP, the program will detect it automatically and return to command mode. * ppp ON tama> .Nm PPP ON tama> * NOW, you are connected! Note that .Sq PPP in the prompt has changed to capital letters to indicate this. * PPP ON tama> show lcp * You'll see LCP status * PPP ON tama> show ipcp * You'll see IPCP status. At this point, your machine has a host route to the peer. If you want to add a default route entry, then enter the following command. * PPP ON tama> add 0 0 HISADDR * The string .Sq HISADDR represents the IP address of connected peer. * PPP ON tama> * Use network applications (i.e. ping, telnet, ftp) in other windows * PPP ON tama> show log * Gives you some logging messages * PPP ON tama> close * The connection is closed and modem will be disconnected. * ppp ON tama> quit % .Sh AUTOMATIC DIALING To use automatic dialing, you must prepare some Dial and Login chat scripts. See the example definitions in
a /etc/ppp/ppp.conf.sample (the format of ppp.conf is pretty simple). l -bullet -compact t Each line contains one command, label or comment. t A line starting with a .Sq # character is treated as a comment line. t A label name has to start in the first column and should be followed by a colon (:). t A command line must contain a space or tab in the first column. .El Once ppp.conf is ready, specify the destination label name when you invoke .Nm ppp . Commands associated with the destination label are then executed. Note that the commands associated with the .Dq default label are ALWAYS executed. Once the connection is made, you'll find that the .Nm ppp portion of the prompt has changed to .Nm PPP . % ppp pm2 ... ppp ON tama> dial dial OK! login OK! PPP ON tama> If the
a /etc/ppp/ppp.linkup file is available, its contents are executed when the .Em PPP connection is established. See the provided example which adds a default route. The string HISADDR represents the IP address of the remote peer. .Sh BACKGROUND DIALING If you want to establish a connection using .Nm ppp non-interactively (such as from a .Xr crontab(5) entry or an .Xr at(1) script) you should use the .Fl background option. You must also specify the destination label in
a /etc/ppp/ppp.conf to use. When .Fl background is specified, .Nm attempts to establish the connection. If this attempt fails, .Nm ppp exits immediately with a non-zero exit code. If it succeeds, then .Nm ppp becomes a daemon, and returns an exit status of zero to its caller. The daemon exits automatically if the connection is dropped by the remote system, or it receives a TERM signal. The file
a /var/run/ppp.tun0.pid contains the process id number of the .Nm ppp program that is using the tunnel device tun0. .Sh DIAL ON DEMAND To play with demand dialing, you must use the .Fl auto or .Fl ddial option. You must also specify the destination label in
a /etc/ppp/ppp.conf to use. It should contain the .Dq ifaddr command to define the remote peer's IP address. (refer to
a /etc/ppp/ppp.conf.sample ) % ppp -auto pm2demand ... % When .Fl auto or .Fl ddial is specified, .Nm runs as a daemon but you can still configure or examine its configuration by using the diagnostic port as follows: % telnet localhost 3000 Trying 127.0.0.1... Connected to localhost.spec.co.jp. Escape character is '^]'. User Process PPP. Written by Toshiharu OHNO. Working as auto mode. PPP on tama> show ipcp what ? PPP on tama> pass xxxx PPP ON tama> show ipcp IPCP [OPEND] his side: xxxx ....
p Each .Nm daemon has an associated port number which is computed as "3000 + tunnel_device_number". If 3000 is not good base number, edit defs.h in the ppp sources (
a /usr/src/usr.sbin/ppp ) and recompile it. When an outgoing packet is detected, .Nm will perform the dialing action (chat script) and try to connect with the peer. If the connect fails, the default behavior is to wait 30 seconds and then attempt to connect when another outgoing packet is detected. This behavior can be changed with d -literal -offset indent set redial seconds|random[.nseconds|random] [dial_attempts] .Ed
p .Sq Seconds is the number of seconds to wait before attempting to connect again. If the argument is .Sq random , the delay period is a random value between 0 and 30 seconds. .Sq Nseconds is the number of seconds to wait before attempting to dial the next number in a list of numbers (see the .Dq set phone command). The default is 3 seconds. Again, if the argument is .Sq random , the delay period is a random value between 0 and 30 seconds. .Sq dial_attempts is the number of times to try to connect for each outgoing packet that is received. The previous value is unchanged if this parameter is omitted. If a value of zero is specified for .Sq dial_attempts , .Nm ppp will keep trying until a connection is made. d -literal -offset indent set redial 10.3 4 .Ed
p will attempt to connect 4 times for each outgoing packet that is detected with a 3 second delay between each number and a 10 second delay after all numbers have been tried. If multiple phone numbers are specified, the total number of attempts is still 4 (it does not attempt each number 4 times). Modifying the dial delay is very useful when running .Nm in demand dial mode on both ends of the link. If each end has the same timeout, both ends wind up calling each other at the same time if the link drops and both ends have packets queued. At some locations, the serial link may not be reliable, and carrier may be lost at inappropriate times. It is possible to have .Nm redial should carrier be unexpectedly lost during a session. d -literal -offset indent set reconnect timeout ntries .Ed This command tells ppp to re-establish the connection .Ar ntries times on loss of carrier with a pause of .Ar timeout seconds before each try. For example, d -literal -offset indent set reconnect 3 5 .Ed tells .Nm that on an unexpected loss of carrier, it should wait .Ar 3 seconds before attempting to reconnect. This may happen up to .Ar 5 times before .Nm gives up. The default value of ntries is zero (no redial). Care should be taken with this option. If the local timeout is slightly longer than the remote timeout, the reconnect feature will always be triggered (up to the given number of times) after the remote side times out and hangs up. If the .Fl background flag is specified, all phone numbers are dialed at most once until a connection is made. The next number redial period specified with the .Dq set redial command is honoured, as is the reconnect tries value. To terminate the program, type PPP ON tama> close ppp ON tama> quit all
p A simple .Dq quit command will terminate the telnet connection but not the program itself. You must use .Dq quit all to terminate the program as well. .Sh PACKET ALIASING The .Fl alias command line option enables packet aliasing. This allows the ppp host to act as a masquerading gateway for other computers over a local area network. Outgoing IP packets are are aliased so that they appear to come from the ppp host, and incoming packets are de-aliased so that they are routed to the correct machine on the local area network. Packet aliasing allows computers on private, unregistered subnets to have internet access, although they are invisible from the outside world. In general, correct ppp operation should first be verified with packet aliasing disabled. Then, the .Fl alias option should be switched on, and network applications (web browser, telnet, ftp, ping, traceroute) should be checked on the ppp host. Finally, the same or similar applications should be checked on other computers in the LAN. If network applications work correctly on the ppp host, but not on other machines in the LAN, then the masquerading software is working properly, but the host is either not forwarding or possibly receiving IP packets. Check that IP forwarding is enabled in /etc/sysconfig and that other machines have designated the ppp host as the gateway for the LAN. .Sh PACKET FILTERING This implementation supports packet filtering. There are three kinds of filters: ifilter, ofilter and dfilter. Here are the basics: l -bullet -compact t A filter definition has the following syntax: set filter-name rule-no action [src_addr/src_width] [dst_addr/dst_width] [proto [src [lt|eq|gt] port ]] [dst [lt|eq|gt] port] [estab] l -enum t .Sq filter-name should be one of ifilter, ofilter, or dfilter. t There are two actions: .Sq permit and .Sq deny . If a given packet matches the rule, the associated action is taken immediately. t .Sq src_width and .Sq dst_width work like a netmask to represent an address range. t .Sq proto must be one of icmp, udp or tcp. t .Sq port number can be specified by number and service name from
a /etc/services . .El t Each filter can hold up to 20 rules, starting from rule 0. The entire rule set is not effective until rule 0 is defined. t If no rule is matched to a packet, that packet will be discarded (blocked). t Use .Dq set filter-name -1 to flush all rules. .El See
a /etc/ppp/ppp.conf.filter.example . .Sh RECEIVING INCOMING PPP CONNECTIONS (Method 1) To handle an incoming .Em PPP connection request, follow these steps: l -enum t Make sure the modem and (optionally)
a /etc/rc.serial is configured correctly. l -bullet -compact t Use Hardware Handshake (CTS/RTS) for flow control. t Modem should be set to NO echo back (ATE0) and NO results string (ATQ1). .El t Edit
a /etc/ttys to enable a getty on the port where the modem is attached. For example: .Dl ttyd1 "/usr/libexec/getty std.38400" dialup on secure Don't forget to send a HUP signal to the init process to start the getty. .Dl # kill -HUP 1 t Prepare an account for the incoming user. d -literal ppp:xxxx:66:66:PPP Login User:/home/ppp:/usr/local/bin/ppplogin .Ed t Create a
a /usr/local/bin/ppplogin file with the following contents: d -literal -offset indent #!/bin/sh -p exec /usr/sbin/ppp -direct .Ed (You can specify a label name for further control.)
p Direct mode ( .Fl direct ) lets .Nm work with stdin and stdout. You can also telnet to port 3000 to get command mode control in the same manner as client-side .Nm. t Optional support for Microsoft's IPCP Name Server and NetBIOS Name Server negotiation can be enabled use .Dq enable msext and .Dq set ns pri-addr [sec-addr] along with .Dq set nbns pri-addr [sec-addr] in your ppp.conf file .El .Sh RECEIVING INCOMING PPP CONNECTIONS (Method 2) This method differs in that it recommends the use of .Em mgetty+sendfax to handle the modem connections. The latest version 0.99 can be compiled with the .Dq AUTO_PPP option to allow detection of clients speaking PPP to the login prompt. Follow these steps: l -enum t Get, configure, and install mgetty+sendfax v0.99 or later (beta) making sure you have used the AUTO_PPP option. t Edit
a /etc/ttys to enable a mgetty on the port where the modem is attached. For example: .Dl cuaa1 "/usr/local/sbin/mgetty -s 57600" dialup on t Prepare an account for the incoming user. d -literal Pfred:xxxx:66:66:Fred's PPP:/home/ppp:/etc/ppp/ppp-dialup .Ed t Examine the files
a /etc/ppp/sample.ppp-pap-dialup and
a /etc/ppp/ppp.conf.sample for ideas. ppp-pap-dialup is supposed to be called from
a /usr/local/etc/mgetty+sendfax/login.conf from a line like .Dl /AutoPPP/ - - /etc/ppp/ppp-pap-dialup .El .Sh SETTING IDLE, LINE QUALITY REQUEST, RETRY TIMER To check/set idletimer, use the .Dq show timeout and .Dq set timeout [lqrtimer [retrytimer]] commands. Ex: .Dl ppp ON tama> set timeout 600 The timeout period is measured in seconds, the default values for which are timeout = 180 or 3 min, lqrtimer = 30sec and retrytimer = 3sec. To disable the idle timer function, use the command .Dq set timeout 0 . In .Fl auto mode, an idle timeout causes the .Em PPP session to be closed, though the .Nm program itself remains running. Another trigger packet will cause it to attempt to reestablish the link. .Sh Predictor-1 compression This version supports CCP and Predictor type 1 compression based on the current IETF-draft specs. As a default behavior, .Nm will attempt to use (or be willing to accept) this capability when the peer agrees (or requests it). To disable CCP/predictor functionality completely, use the .Dq disable pred1 and .Dq deny pred1 commands. .Sh Controlling IP address .Nm uses IPCP to negotiate IP addresses. Each side of the connection specifies the IP address that it's willing to use, and if the requested IP address is acceptable then .Nm returns ACK to the requester. Otherwise, .Nm returns NAK to suggest that the peer use a different IP address. When both sides of the connection agree to accept the received request (and send ACK), IPCP is set to the open state and a network level connection is established. To control this IPCP behavior, this implementation has the .Dq set ifaddr command for defining the local and remote IP address: .Nm set ifaddr .Op src_addr Op dst_addr Op netmask Op trg_addr Where, .Sq src_addr is the IP address that the local side is willing to use and .Sq dst_addr is the IP address which the remote side should use. .Sq netmask is interface netmask. .Sq trg_addr is the IP address which used in address negotiation. Ex: .Dl set ifaddr 192.244.177.38 192.244.177.2 255.255.255.0 The above specification means: l -bullet -compact t I strongly want to use 192.244.177.38 as my IP address, and I'll disagree if the peer suggests that I use another address. t I strongly insist that peer use 192.244.177.2 as own side address and don't permit it to use any IP address but 192.244.177.2. When peer request another IP address, I always suggest that it use 192.244.177.2. t My interface netmask will be 255.255.255.0. t This is all fine when each side has a pre-determined IP address, however it is often the case that one side is acting as a server which controls all IP addresses and the other side should obey the direction from it. .El In order to allow more flexible behavior, `ifaddr' variable allows the user to specify IP address more loosely: .Dl set ifaddr 192.244.177.38/24 192.244.177.2/20 A number followed by a slash (/) represent the number of bits significant in the IP address. The above example signifies that: l -bullet -compact t I'd like to use 192.244.177.38 as my address if it is possible, but I'll also accept any IP address between 192.244.177.0 and 192.244.177.255. t I'd like to make him use 192.244.177.2 as his own address, but I'll also permit him to use any IP address between 192.244.176.0 and 192.244.191.255. t As you may have already noticed, 192.244.177.2 is equivalent to saying 192.244.177.2/32. t As an exception, 0 is equivalent to 0.0.0.0/0, meaning that I have no preferred IP address and will obey the remote peer's selection. t 192.244.177.2/0 means that I'll accept/permit any IP address but I'll try to insist that 192.244.177.2 be used first. .El .Sh Connecting with your service provider The following steps should be taken when connecting to your ISP: l -enum t Describe your provider's phone number(s) in the dial script using the .Dq set phone command. This command allows you to set multiple phone numbers for dialing and redialing separated by a colon (:). For example: d -literal -offset indent set phone "1234567:2345678" .Ed
p Here, the first number is attempted. If the connection fails, the second number is attempted after the next number redial period. If the second number also fails, the first is tried again after the redial period has expired. The selected phone number is substituted for the \\T string in the .Dq set dial command (see below). t Set up your redial requirements using .Dq set redial . For example, if you have a bad telephone line or your provider is usually engaged (not so common these days), you may want to specify the following: d -literal -offset indent set redial 10 4 .Ed
p This says that up to 4 phone calls should be attempted with a pause of 10 seconds before dialing the first number again. t Describe your login procedure using the .Dq set dial and .Dq set login commands. The .Dq set dial command is used to talk to your modem and establish a link with your ISP, for example: d -literal -offset indent set dial "ABORT BUSY ABORT NO\\\\sCARRIER TIMEOUT 4 \\"\\" ATZ OK-ATZ-OK ATDT\\\\T TIMEOUT 60 CONNECT" .Ed
p This modem "chat" string means: l -bullet t Abort if the string "BUSY" or "NO CARRIER" are received. t Set the timeout to 4. t Expect nothing. t Send ATZ. t Expect OK. If that's not received, send ATZ and expect OK. t Send ATDTxxxxxxx where xxxxxxx is the next number in the phone list from above. t Set the timeout to 60. t Wait for the CONNECT string. .El Once the connection is established, the login script is executed. This script is written in the same style as the dial script: d -literal -offset indent set login "TIMEOUT 15 login:-\\\\r-login: awfulhak word: xxx ocol: PPP HELLO" .Ed
p This login "chat" string means: l -bullet t Set the timeout to 15 seconds. t Expect "login:". If it's not received, send a carriage return and expect "login:" again. t Send "awfulhak" t Expect "word:" (the tail end of a "Password:" prompt). t Send "xxx". t Expect "ocol:" (the tail end of a "Protocol:" prompt). t Send "PPP". t Expect "HELLO". .El
p Login scripts vary greatly between ISPs. t Use .Dq set line and .Dq set sp to specify your serial line and speed, for example: d -literal -offset indent set line /dev/cuaa0 set sp 115200 .Ed
p Cuaa0 is the first serial port on FreeBSD. Cuaa1 is the second etc. A speed of 115200 should be specified if you have a modem capable of bit rates of 28800 or more. In general, the serial speed should be about four times the modem speed. t Use .Dq set ifaddr command to define the IP address. l -bullet t If you know what IP address your provider uses, then use it as the remote address, otherwise choose something like 10.0.0.2/0 (see below). t If your provider has assigned a particular IP address to you, then use it as your address. t If your provider assigns your address dynamically, choose a suitably unobtrusive and unspecific IP number as your address. 10.0.0.1/0 would be appropriate. The bit after the / specifies how many bits of the address you consider to be important, so if you wanted to insist on something in the class C network 1.2.3.0, you could specify 1.2.3.0/24. .El
p An example for a connection where you don't know your IP number or your ISPs IP number would be: d -literal -offset indent set ifaddr 10.0.0.1/0 10.0.0.2/0 .Ed t In most cases, your ISP will also be your default router. If this is the case, add the lines d -literal -offset indent delete ALL add 0 0 HISADDR .Ed
p to
a ppp.conf .
p This tells .Nm ppp to delete all routing entries already made by .Nm ppp , then to add a default route to HISADDR. HISADDR is a macro meaning the "other side"s IP number.
p If you're using dynamic IP numbers, you must also put these two lines in the
a ppp.linkup file. Then, once the link has been established and .Nm ppp knows the actual IP numbers in use, all previous (and probably incorrect) entries are deleted and a default to the correct IP number is added. Use the same label as the one used in
a ppp.conf .
p If commands are being typed interactively, the only requirement is to type d -literal -offset indent add 0 0 HISADDR .Ed
p after a successful dial. t If your provider requests that you use PAP/CHAP authentication methods, add the next lines to your
a ppp.conf file: d -literal -offset indent enable pap (or enable chap) disable chap (or disable pap) set authname MyName set authkey MyPassword .Ed t It is also worth adding the following line: d -literal -offset indent set openmode active .Ed
p This tells .Nm ppp to initiate LCP. Without this line, there's a possibility of both sides of the connection just sitting there and looking at eachother rather than communicating. .El Please refer to
a /etc/ppp/ppp.conf.sample and
a /etc/ppp/ppp.linkup.sample for some real examples. The pmdemand label should be appropriate for most ISPs. .Sh Logging facility .Nm is able to generate the following log info into
a /var/log/ppp.tun0.log : l -column SMMMMMM -offset indent -compat t Li Phase Phase transition log output t Li Chat Generate Chat script trace log t Li Connect Generate complete Chat log t Li Carrier Log Chat lines with 'CARRIER' t Li LQM Generate LQR report t Li LCP Generate LCP/IPCP packet trace t Li Link Log address assignments and link up/down events t Li TCP/IP Dump TCP/IP packet t Li HDLC Dump HDLC packet in hex t Li Async Dump async level packet in hex .El The .Dq set debug command allows you to set logging output level, of which multiple levels can be specified. The default is equivalent to .Dq set debug carrier link phase . If a HUP signal is received, the log file is closed and re-opened to facilitate log file rotation. .Sh MORE DETAILS l -bullet -compact t Please read the Japanese doc for complete explanation. It may not be useful for non-japanese readers, but examples in the document may help you to guess. t Please read example configuration files. t Use .Dq help , .Dq show ? , .Dq set ? and .Dq set ? <var> commands. t NetBSD and BSDI-1.0 were supported in previous releases but are no longer supported in this release. Please contact the author if you need old driver code. .El .Sh FILES .Nm refers to three files: ppp.conf, ppp.linkup and ppp.secret. These files are placed in
a /etc/ppp , but the user can create his own files under his $HOME directory as
a .ppp.conf ,
a .ppp.linkup and
a .ppp.secret. .Nm will always try to consult the user's personal setup first. l -tag -width flag
a $HOME/ppp/.ppp.[conf|linkup|secret] User dependent configuration files.
a /etc/ppp/ppp.conf System default configuration file.
a /etc/ppp/ppp.secret An authorization file for each system.
a /etc/ppp/ppp.linkup A file to check when .Nm establishes a network level connection.
a /var/log/ppp.tun0.log Logging and debugging information file.
a /var/spool/lock/Lck..* tty port locking file.
a /var/run/PPP.system Holds the pid for ppp -auto system.
a /var/run/ppp.tun0.pid The process id (pid) of the ppp program connected to the ppp0 device.
a /etc/services Get port number if port number is using service name. .El .Sh SEE ALSO .Xr chat 8 , .Xr pppd 8 .Sh HISTORY This program was submitted in FreeBSD-2.0.5 Atsushi Murai (amurai@spec.co.jp). .Sh AUTHORS Toshiharu OHNO (tony-o@iij.ad.jp)