From volkerdi@mhd1.moorhead.msus.edu Fri Mar 25 16:38:42 1994
Received: from joker.cs.hut.fi by niksula.hut.fi id <49656-1>; Fri, 25 Mar 1994 18:38:52 +0200
Received: from mail.netcom.com ([192.100.81.107]) by niksula.hut.fi with SMTP id <51152-3>; Fri, 25 Mar 1994 16:28:19 +0200
Received: from localhost by mail.netcom.com (8.6.4/SMI-4.1/Netcom)
	id GAA08606; Fri, 25 Mar 1994 06:29:04 -0800
From: longyear@netcom.com (Alfred Longyear)
X-Mn-Key: PPP
X-Note1: Remember to put 'X-Mn-Key: PPP' to your mail body or header
Message-Id: <199403251429.GAA08606@mail.netcom.com>
Subject: ppp version 0.1 patches for Linux 1.0
Sender: owner-linux-activists@joker.cs.hut.fi
To: linux-activists@joker.cs.hut.fi
Date: Fri, 25 Mar 1994 16:28:35 +0200
Cc: callahan@maths.ox.ac.uk (Michael Callahan)
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 4322      


I was asked to make some patches to make the version 0.1 PPP code work
with the "1.0"+ kernels.

Here is a set of patches to do this. You probably have the first two in
place.

Please note, these are the ONLY patches which are needed to the
distributed code to make the process work under 1.0. If you start with a
"fresh" copy from your archives (or ftp.gang.umass.edu) and apply these
patches, it should work. There may be copious warning messages generated
during the compile of ppp.c. These are just that; warnings. (If you are
bothered by the warnings, then go through the ppp.c module and cast the
printk numerical values to (int).)

1. A small patch to enable the PPP code in the config.in file.

2. The "pl15" patch to ppp.c code.

3. A patch to the "main.c" module of pppd to allow the routing to work
with the new routing definitions. I chose to use the "old" routing calls
and tables as these are compatible with the existing code.

This patch to the pppd process should be performed if you are planning
to re-compile the code. If you use Michael's BINARY; as originally
delivered (if he did deliver a binary, that is) then it is ok. However,
to rebuild the process and have it work with the proper routing, you
must do this patch.

With these patches applied the ppp code should work. I have run it with
the 1.0.4 kernel and it functions as with the earlier kernel releases.

These patches will, do (I am using it now via telnet), work with the 1.0
kernel.

Please re-check your chat script if you use it. Make sure that you end
the script at the "last possible moment"; just before your peer ppp
process tries to send the lcp configure frame (the trash). For some
strange reason, it happen only to me, the ppp process used on netcom
sends "PPP session from (163.179.6.2) to 192.187.163.32 beginning...".
(Those are the remote and local IP numbers for my session; so please
don't tell me that. :)) At any rate, leaving this line to filter through
the pppd process caused it to become lost. What happened in pre-1.0 days
was that it would generate a bad fcs block for the first receive and the
timeouts would expire and allow the connection to be re-started. This
apparently did not work in my case. The pppd process was lost in a
quagmire of unknown frames. For all that I know, I could have been
confusing the ppp process on netcom! Besides, I did not like the "bad
fcs" messages on the console :) So, please trim the chat script to
remove the extra "informational messages" that you may receive. In my
case, the script looked for "beginning..." once it had sent the
password. It should work following that. (As always, It works for me. :))

-- 
Al Longyear           longyear@netcom.com