[418] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: PPP problems

daemon@ATHENA.MIT.EDU (Al Longyear)
Mon Jun 5 15:13:40 1995

Date: Mon, 5 Jun 1995 09:33:44 -0700
To: dean@franklin.com, linux-net@vger.rutgers.edu
From: Al Longyear <longyear@sii.com>

At 09:22 AM 6/5/95 -0400, Dean G A Johnson wrote:
>
>This weekend I had some problems with my PPP connection to my internet access
>provider.  I am having trouble determining which 'side' the problem is on.
>I don't know if my Linux box is messing up or my internet service provider is 
>messing up.

Without the log trace it is impossible to tell. Send the log to
longyear@netcom.com when you get home.

>First a little background.  I am running linux on a 486dx33 with 12 mb RAM.
>I am using pppd and have been using it without a problem from several months.
>About a week ago my internet service provider switched my account from static
>IP to dynamic IP.  I made the necessary changes to my /etc/ppp/options file 
>and it was working beautifully for about a week.

Please do one thing at a time. Run the old kernel with the changes for a
dynamic IP address and then upgrade the kernel. Doing both things (changing
the options for dynamic IP addresses and upgrading the kernel) will confuse
the issue.

>I have recently updated to
>the latest kernel at sunsite.unc.edu but this problem seems independent of
>that.

The 1.2.8 version of the kernel contained a patch to the ppp.c driver to fix
several problems. One problem was that the driver was not using one of the
options which it should have been. It turns out that the 'lack' of using the
option really hid a bug in the daemon process as the daemon was not sending
the proper data to the driver. The 2.1.2d version of the daemon corrected
this flaw. The daemon was using the wrong variable to define what the peer
(remote) system wanted for a compression option.

>The Problem.
>
>This weekend I tried to establish a ppp connection and I experienced the
>following failure mode:
>
>(I am at work and I don't have the log here with me so I will paraphrase)
>
>-the chat script connected correctly and started the ppp negoiations.
>
>-after a little thrashing I get something like this:
>
>pppd [234]: Hangup (SIGHUP)

That mearly means that the remote system has disconnected the link. It is
pppd logging the fact that it received a SIGHUP from the tty drivers.

Please make sure that you are using the 2.1.2d version of pppd. It was
uploaded to sunsite about one week ago. I sent a notice to the
linux-ppp@vger.rutgers.edu list and to the c.o.l.announce usenet group.
(There is still a propigation problem with c.o.l.a. if the article was
approved as it has not shown up in netcom's spool.)

There is no 'magic' trick to using dynamic IP addressses. You need only
leave out your IP address or use 0.0.0.0 for the value. If you are going to
use dynamic IP then a good option to add is "noipdefault", but it is not
manditory.

>
>
>Can anyone out there figure out from this if the problem is on my side
>or on the other side of the link?
>
>If not, then how do I troubleshoot this to find out?  What reference materials
>are there on the subject that I could use to fix this problem?
>
>Thanks in advance
>--------
>-dgaj
>
>
-- 
Al Longyear               longyear@netcom.com            longyear@sii.com
The public pgp 2.6 key is available by fingering longyear@netcom.com.


home help back first fref pref prev next nref lref last post