pppd 2.2.0 and kernel 1.2.13

pppd 2.2.0 and kernel 1.2.13

Post by Matthew Dawso » Wed, 30 Oct 1996 04:00:00



Very big newbie warning...

I've managed to install pppd 2.2.0e, I have a chat script written, and I
have managed to successfully run pppd.  I run it in debugging mode and
am told that I've connected and my ID and password have been accepted.
My big question is how do I know that the login process is completely
(and correctly) finished?  Should I get a message saying something to
the effect of "Your IP address is ...", (Boston University uses dynamic
addresses), or is this one of those occasions where Linux goes on its
merry way after successfully completing something without bothering to
inform the ever-so-humble system administrator?

And one more minor question...  How do I kill the damn process?  I've
tried to find the right .pid, but I can't seem to exit the session.

Thanks in advance...

Matt Dawson

 
 
 

pppd 2.2.0 and kernel 1.2.13

Post by Matthew Dawso » Wed, 30 Oct 1996 04:00:00


Well, forget my post.  I just got it working.  

-Matt

 
 
 

pppd 2.2.0 and kernel 1.2.13

Post by Al Longye » Fri, 01 Nov 1996 04:00:00



>I've managed to install pppd 2.2.0e, I have a chat script written, and I
>have managed to successfully run pppd.  I run it in debugging mode and
>am told that I've connected and my ID and password have been accepted.
>My big question is how do I know that the login process is completely
>(and correctly) finished?  Should I get a message saying something to
>the effect of "Your IP address is ...", (Boston University uses dynamic
>addresses), or is this one of those occasions where Linux goes on its
>merry way after successfully completing something without bothering to
>inform the ever-so-humble system administrator?

It depends upon the terminal server which BU uses. Some will write a
text message. Some don't. The message, if you get one, is totally junk
to the PPP link and will be discarded.

A common response to any PPP protocol starting would be to wait for
the flag sequence. In the case of PPP over an Asynch link, the flag is
simply a 0x7E (the ~ character) when it is not preceeded by a 0x7D.
So, if you really want to wait for some confirmation message, then just
wait for the ~ character.

I would not bother if I was you. Just find the proper sequence for sending
the password and the protocol to start the PPP link and let it go at that.

Quote:>And one more minor question...  How do I kill the damn process?

See the script in the PPP-FAQ document on sunsite.unc.edu.

--

 
 
 

1. pppd, kernel 1.2.13, and dial-up ISDN

my ISP provides me with a 128K connection via a 3com Impact ISDN TA
which of course is attached via /dev/cua1.  Authentication is handled
via PAP.  I have tried both +ua pap.inf and adding the ppp-secrets files
at different times both ending up in failure.  I know the device is
initializing and connecting to the Ascend router on the ISP's side but I
cannot seem to get pppd to negotiate IP, etc.
Any suggestions?

Tim Schuh

2. interupt level 4

3. Problems with pppd and kernel > 1.2.13

4. SMPT connections sticky?????

5. strange problems 1.2.13 --> 2.0.0 --> 1.2.13

6. Cannot mount new SCSI disk!!

7. 1.2.13 kernel is slower than 1.2.1 kernel

8. Euro and AIX

9. IP alias - Kernel crash - 1.2.13 kernel, 3com 3c590 module

10. pppd-2.2.0d and 1.2.13

11. Red Hat Picasso Linux (Kernel 1.2.13) - Want to make a.out in GCC

12. Compiling 1.2.13 kernel with RedHat 3.0.3/gcc 2.7.2

13. Quota's on 1.2.13 kernel?