CHANGES FROM THE PREVIOUS VERSION
FUTURE PLANS
INSTALLATION
+ PROBLEMS WHICH MAY OCCUR WHILE BUILDING THE KERNEL
+ A REFERENCE TO UNDEFINED _mod_use_count_
+ BLOCK ON FREELIST AT nnnnnn ISN'T FREE
GENERAL NETWORK CONFIGURATION
CONNECTING TO A PPP SERVER
IF IT WORKS
INTRODUCTION
This file is substantially derived from the previous version for
-the pppd process 2.1.2. Michael Callahan wrote that version. This
+the pppd process 2.2.0. Michael Callahan wrote that version. This
particular version was written, modified, hacked, changed, whatever,
by Al Longyear. If you find errors in this document, they are probably
mine and not Michael's.
The PPP protocol consists of two parts. One is a scheme for framing
and encoding packets, the other is a series of protocols called LCP,
-IPCP, UPAP and CHAP, for negotiating link options and for
+IPCP, PAP and CHAP, for negotiating link options and for
authentication. This package similarly consists of two parts: a
kernel module which handles PPP's low-level framing protocol, and a
user-level program called pppd which implements PPP's negotiation
Chris Torek.
Jim Freeman added the code to support a ppp module and to dynamically
-extend the number of ppp devices. The Space.c module should not have
-any devices defined for this logic to work.
+extend the number of ppp devices. All ppp devices listed in the Space.c
+will be unlinked when the kernel is loaded. This feature makes the use
+of '16 channel' support obsolete.
+
CHANGES FROM THE PREVIOUS VERSION
- There is no limit to the number of ppp devices which you may use. Jim Freeman
has added code to create them upon demand and to re-use the ones which have
been closed. There is no code, nor plans to write code, to remove (delete)
- the un-used devices. So, if your system goes to a spurt and uses 3000 ppp
+ the un-used devices. So, if your system goes to a spurt and uses 256 ppp
devices, it will remain at that level until you next reload the kernel.
+ If you are using modules then you may use the additional setting of
+
+ max_dev=#
+
+ where # is the maximum number. The default is set by the define PPP_MAX_DEV
+ and this define may be altered if you are not using modules.
+
+ The BSD compressor may only be loaded as a module. Previous beta versions
+ permitted the compressor to be included into the kernel. This was removed
+ for several reasons, some technical, some less technical and more
+ political (legal).
+
FUTURE PLANS
-The IPX support is still minimal. There is code which will only work with
-the 1.3 version of the networking software. The pppd process will still
-require changes to support the IPXCP and a change to the driver to properly
-enable/disable the IPX frames. Jim Freeman is reportily working on the IPX
-support.
+The next version of pppd, 2.3, is designed to contain a demand dial
+function directly.
+
INSTALLATION
subscribe linux-ppp
contained in the body to majordomo@vger.rutgers.edu
+ You may use
+
+ subscribe linux-ppp myname@mail.address
+
+ if you wish the linux-ppp information sent to a different mail
+ address.
+
To leave the mail list, send 'unsubscribe linux-ppp' to the same
mail address.
You can send to the list by mailing to
linux-ppp@vger.rutgers.edu. This is a majordomo mailing list and
is unlike the earlier version on hut.fi. There is no magic header
- required for this list. In addition, it is mirrored to the usenet
- group linux.act.ppp. You may choose to read the few messages posted
+ required for this list. In addition, it is gated to the usenet
+ group linux.dev.ppp. You may choose to read the few messages posted
there.
Usenet News Groups
'ppp' on usenet may cause it to be ignored by the people who
actually work on the networking code.
-kernel driver installation:
+Installation procedure:
+
+The installation procedure has been totally revised for this
+version. Due to feedback from other users, it was felt that a more
+automated installation procedure be performed.
+
+Use the following procedure for all kernel versions. There are six steps
+numbered one through six. Please do them in order and not skip one.
+
+
+1. Issue the command:
+
+./configure
+
+from the top level directory of pppd. This is the directory which
+contains this README.linux file. The result of this will be to build a
+set of symbolic links to the makefiles. They should link 'Makefile' to
+'Makefile.linux' in each of the directories.
+
+
+2. Issue the command:
- This depends on the kernel version you're using.
+make kernel
- Version 1.0.*
- These versions are not supported.
+from the top level directory. This will install the various include
+files and source files into the proper directory for the linux
+kernel. If you don't have the kernel installed in the /usr/src/kernel
+directory then it will not work. Instead it will print a message to
+the effect that you need to specify the kernel location on the
+kinstall command.
- Version 1.1.0 through 1.1.14
- These versions are not supported.
+The actual message will say:
- Version 1.1.15 to 1.2.99
- - Use the source to the ppp.c driver from the 'linux' directory and
- replace the driver in the /usr/src/linux/drivers/net.
- - Delete the file /usr/src/linux/drivers/net/ppp.h
- - Add the following files to /usr/include/net:
- if_ppp.h
- if_pppvar.h
- ppp_comp.h
- ppp_defs.h
+There appears to be no kernel source distribution in /usr/src/linux.
+Give the top-level kernel source directory as the argument to
+this script.
+usage: kinstall.sh [linux-source-directory]
- - IF AND ONLY IF you are missing the following files then use the
- copy provided in the 'linux' directory to supplement the files.
+If, and only if, you receive this message, do the following:
- DO **NOT** REPLACE THE FILE IF IT CURRENTLY EXISTS.
+ a. Change to the 'linux' directory with the command:
- if_arp.h
- if_route.h
+cd linux
- Version 1.3.0 and later
- The files have been properly updated.
+ b. Issue the command:
- Reboot with the new kernel. At startup, you should see
- something line this:
+./kinstall.sh /usr/src/linux
- PPP: version 2.2.0 (dynamic channel allocation)
- TCP compression code copyright 1989 Regents of the University of California
- Dynamic channel allocation code copyright 1995 Caldera, Inc.
- PPP line discipline registered.
+or use the proper location for the kernel rather than
+/usr/src/linux. For example, if you have the kernel installed in
+/usr1/kernel then the command would be:
-pppd installation:
+./kinstall.sh /usr1/kernel
- First update /usr/include/net as described in the previous section.
+The script will validate that the kernel is properly installed into
+that directory and check the level of the kernel. The installation
+will not be accepted if your kernel is too early.
- Then, in this directory, issue the command:
+The installation procedure will copy only the files which are
+needed. It will not replace any file which should not be
+replaced. Please don't second-guess the installation script and
+attempt to do the procedure on your own. There are some very subtle
+dependencies and if you are not careful, the installation will not
+work.
- ./configure
+You are free to run the installation script as many times as you
+wish. The additional executions will only change the files which have
+not been changed.
- Go to the 'pppd' directory and issue the commands:
- make depend
- make
+3. Build the kernel.
- This should build the program. If you have any errors then ensure
- that you have the proper include files and haven't missed one.
+You must rebuild the kernel with this package. The driver is totally
+new and will not work with the older daemon and the newer daemon will
+not work with the older kernel driver. If you don't know how to build
+a kernel, then you should read the README file in the kernel source
+directory.
- If you are using shadow passwords *AND* have it installed, then you
- should use the command:
+If you wish module support then you need to have the 'modules-1.1.87'
+package installed as the minimum version. Earlier versions of the module
+support will not work properly.
- make shadow
+As of this time, the current version for the modules package is
+1.2.0. Even 1.1.87 is old. However, if you only have 1.1.87 then it
+will do as it permits the symbol table references. Please consider
+upgrading the module package however.
- rather than the non-shadow command listed earlier.
+Instructions on building the kernel with modules are given in the
+README.modules in the kernel source directory.
- (Shadow library support will require the addition of some modules
- to the shadow library. These were overlooked by the package author
- and I will, or have already, notified him.)
-
- This code has been built with the 4.5 and 4.6 subroutine libraries
- and include files. If your include files are too old then you should
- upgrade them.
- To install the package, issue the command:
+4. Install the kernel
- make install
+If you are using the Yggdrasil distribution then you need to 'install'
+the kernel at this point. Refer to their documentation on the procedures
+to install the kernel.
- This will install the binary in /usr/sbin and the man page into
- /usr/man/man8.
+Distributions other than the Yggdrasil will normally install the
+kernel when you build it.
- pppd needs to be run as root. You can either make it setuid
- root or just use it when you are root. 'make install' will try
- to install it setuid root. Making pppd setuid root is
- convenient for a single-user machine, but has security
- implications which you should investigate carefully before
- making it available on a multiuser machine.
- The pppd process must have the following directories to work:
+5. Build the programs.
- /var/run
- /etc/ppp
+The programs are built next. The command to build the programs is fairly
+simple. Just issue the command:
- In addition, for the program to run, there must be a 'options' file
- in the /etc/ppp directory. So, the following commands will accomplish
- the required operations. They may have errors if the entries currently
- exist.
+make
- Perform these commands as the 'root' user.
+from the top level directory where this README.linux file is located.
- mkdir /var /etc
- mkdir /var/run /etc/ppp
- touch /etc/ppp/options
-chat installation:
+6. Install the programs.
- If you have not already done so, run `./configure' in this directory.
+You may use the command
- To compile the chat program, go to the 'chat' directory and issue
- the command:
+make install
- make
+to install the various programs. They will be installed into the
+/usr/lib/ppp directory. You may not like this directory for the
+executables. The directory name is called BINDIR and is set in the
+file 'linux/Makefile.linux'.
- To install the package, issue the command:
- make install
+7. Reboot to the new kernel.
- This will install the binary in /usr/sbin and the man page into
- /usr/man/man8.
+After building the new kernel, you will need to actually use it. Reboot
+the Linux system and you may then use the new pppd program.
-pppstats installation:
- If you have not already done so, run `./configure' in this directory.
+8. Load optional modules.
- To compile the pppstats program, go to the 'pppstats' directory
- and issue the command:
+If you are using loadable modules for the ppp then you must load them
+after the kernel has been started. The following relative order must
+be maintained.
- make
+Sequence Module Description
+ 1 slhc.o VJ header compression
+ 2 ppp.o PPP driver
+ 3 bsd_comp.o BSD compression for PPP's compression protocol.
- To install the package, issue the command:
+If you only have the bsd comprssor as a module then you may load it without
+regard to any order.
- make install
+You may elect not to load the BSD compression module if you desire. There
+is a controversy regarding a Motorola software patent and while it is
+believed that this code does not infringe upon the patent, it is however
+an optional component.
+
+In addition, if memory is a premium, do not run the BSD compression. It
+may take large amounts of memory (up to 2.6 meg) for high compression
+lengths to hold the compression dictionaries.
+
+Without the BSD compression module, the PPP driver will not accept PPP's
+compression control protocol for BSD compression.
+
+
+PROBLEMS WHICH MAY OCCUR WHILE BUILDING THE KERNEL
+
+A REFERENCE TO UNDEFINED _mod_use_count_
+
+If you experience an error message that the variable "mod_use_count_" is
+undefined then apply the patches in the linux/Other.Patches directory. There
+is a version for the 1.2.13 kernel and a differnt one for the early 1.3
+kernels.
+
+The current 1.3 series kernels should not experience this problem as the
+patch has already been incorporated.
+
+
+BLOCK ON FREELIST AT nnnnnn ISN'T FREE
+(where nnnnnn are a sequence of hexadecimal digits.)
+
+While this is not really an error when the kernel is built, it is an error
+which may occur when you actually run the system. The solution is a patch
+in the linux/Other.Patches directory. (That is why I mention it here.)
+
+The problem is in the VJ header compression module. It allocated a block
+of memory and then used the wrong variable to determine the amount of memory
+which should be reset. The patch is present in the 1.3.46 kernel and later
+ones. However, versions prior to that may POSSIBLY have the problem depending
+upon the number of slots which are allocated for the header compression logic.
- This will install the binary in /usr/sbin and the man page into
- /usr/man/man8.
GENERAL NETWORK CONFIGURATION
whoever's providing your PPP link.
+
CONNECTING TO A PPP SERVER
To use PPP, you invoke the pppd program with appropriate options.
this option would actually be redundant.
pppd will write error messages and debugging logs to the syslogd
-daemon using the facility name "local2". (Verbose output from chat is
-the same.) These messages may already be logged to the console or to
-a file like /usr/adm/messages; consult your /etc/syslog.conf file to
-see. If you want to make all pppd and chat messages go to the
-console, add the line
+daemon using the facility name "daemon". These messages may already be
+logged to the console or to a file like /usr/adm/messages; consult
+your /etc/syslog.conf file to see. If you want to make all pppd
+messages go to the console, add the line
- local2.* /dev/console
+ daemon.* /dev/console
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is one or more tabs. Do not use spaces.
'debug' option, and put the following two lines in your
/etc/syslog.conf file:
- local2.* /dev/console
- local2.* /usr/adm/ppplog
+ daemon.* /dev/console
+ daemon.* /usr/adm/ppplog
This will cause pppd's messages to be written to the current virtual
console and to the file /usr/adm/ppplog. Note that the left-hand
the remote PPP server. To do this, alter your syslog.conf lines to
look like this
- local2.*,kern.* /dev/console
- local2.*,kern.* /usr/adm/ppplog
+ daemon.*,kern.* /dev/console
+ daemon.*,kern.* /usr/adm/ppplog
and HUP the syslog daemon as before. Then, run pppd with the option
"kdebug 25". Whatever characters arrive over the PPP terminal line
- the version number of Linux PPP you are using
- the exact command you use to start the PPP session
- log output from a session run with the 'debug' option, captured
- using local2.*,kern.* in your syslog.conf file
+ using daemon.*,kern.* in your syslog.conf file
- the type of PPP peer that you are connecting to (eg, Xyzzy Corp
terminal server, Morningstar PPP software, etc)
- the kind of connection you use (modem, hardwired, etc...)
/etc/hosts appropriately.
+
SETTING UP A MACHINE FOR INCOMING PPP CONNECTIONS
Suppose you want to permit another machine to call yours up and start
connected to the Ethernet.
+
SETTING UP A MACHINE FOR INCOMING PPP CONNECTIONS WITH DYNAMIC IP
The use of dynamic IP assignments is not much different from that
(which should be root) and the group only. All other users would be denied
all access to the files and executables.
+d) Prevent the motd file from being sent to the ppp user.
+touch ~ppp/.hushlogin
+chown root ~ppp/.hushlogin
+chmod 444 ~ppp/.hushlogin
+
ADDITIONAL INFORMATION
projects / ppp.git / blobdiff