[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9801.0. "what else changed?" by NNTPD::"[email protected]" (Farrell Woods) Tue May 13 1997 11:29

Somehing else probably changed...

That trace says to me that ppp never entered the network phase.  That is,
no IPCP config-requests were exchanged.  Also, your side appears to be asking
for authentication from the peer.  It hasn't been my experience that ISP's
will do two-way authentication.  Your peer may not have a secret that will
allow the ISP to authenticate itself to you.  pppd might be exiting because
of this (but if that's the case then it should have said something to that
effect.  The ppp code that I'm putting into Steel is better about this.)

What does your /etc/ppp/options file look like?

        -- Farrell


[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
9801.1DECWET::MARTINTue May 13 1997 16:191
Copied this note to 9781.2
9801.2/etc/ppp/options got me!CSC32::A_LICAUSETue May 13 1997 18:0114
    Thanks Farrell...don't know how .0 got deleted, but I'm assuming this
    was in response to my problem with pppd not syncing with the ISP.
    
    It turns out when I was tyring to produce a customer problem, that I
    put all of the PPP options in /etc/ppp/options and forgot to comment
    them out.  also misinterpretted what pppd would do with this file if
    the file keyword was not used specifically.
    
    Once I commented all options from this file, it all began to work.
    
    I'd still like to know a good source for documentation on how to 
    interpret pppd messages for future reference?
    
    Al
9801.3debug messagesNNTPD::"[email protected]"Farrell WoodsMon May 19 1997 12:1624
Hi,

A lot of the debug messages that pppd puts out are useful if you have
some knowledge of the relevent rfc's.  Probably the best place to start
is rfc1661, which describes the point-to-point protocol.  Skip down to
section 3.2 to get an overview of the PPP state machine.  The diagram
will give you an idea of what has to happen to establish a connection.
The paragraphs below that describe the states and what they mean, without
getting too bogged down in the jargon of technical "legalese".

Once you understand how that flows, then you may want to know more about
the details of each phase.  This is where things like the asyncmap, mru,
etc. (for LCP) get negotiated.  The negotiation of parameters for other
related protocols (CCP for compression, negotiation of a common authentication
protocol, and negotiation of a network protocol) follow this model.


The kinds of things that the "kdebug" options will tell you are
meaningful only if you're maintaining the code.


	-- Farrell

[Posted by WWW Notes gateway]