This manual page describes the pon, plog and poff scripts, which allow users to control PPP connections.
pon, invoked without arguments, runs the /etc/ppp/ppp_on_boot file, if it exists and is executable. Otherwise, a PPP connection will be started using configuration from /etc/ppp/peers/provider. This is the default behaviour unless an isp-name argument is given.
For instance, to use ISP configuration
pon will then use the options file /etc/ppp/peers/myisp. You can pass additional options after the ISP name, too. pon can be used to run multiple, simultaneous PPP connections.
poff closes a PPP connection. If more than one PPP connection exists, the one named in the argument to poff will be killed, e.g.
will terminate the connection to myprovider2, and leave the PPP connections to e.g.
poff takes the following command line options:
causes the connection to be redialed after it is dropped.
toggles the state of pppd's debug option.
causes pppd(8) to renegotiate compression.
stops all running ppp connections. If the argument isp-name is given it will be ignored.
displays help information.
prints the version and exits.
If no argument is given, poff will stop or signal pppd if and only if there is exactly one running. If more than one connection is active, it will exit with an error code of 1.
plog shows you the last few lines of /var/log/ppp.log. If that file doesn't exist, it shows you the last few lines of your /var/log/syslog file, but excluding the lines not generated by pppd. This script makes use of the tail(1) command, so arguments that can be passed to tail(1) can also be passed to plog.
Note: the plog script can only be used by root or another system administrator in group __/etc/syslog.conf'' file:
PPPd system options file.
System PAP passwords file.
System CHAP passwords file.
Directory holding the peer options files. The default file is called provider.
The chat script invoked from the default /etc/ppp/peers/provider.