TCPIP on RHL 4.2 (Biltmore)

[Glenn Burkhardt]

Regarding agaskell at west.bidmc.harvard.edu 's attempts to get PPP
running, I don't know quite what to say, except re-check all the
configuration entries.

I just verified for RHL 4.2 (Biltmore) that the drill remains the same:

/etc/sysconfig/network-scripts/ifup-ppp:

line 75:
 connect "/usr/sbin/chat -v -f /etc/sysconfig/network-scripts/chat-$DEVICE"

/etc/syslog.conf:

daemon.debug                                            /var/log/messages

Use the standard Network Configuration GUI in the control panel to do
the rest of the PPP setup.

Here's what was put in the /var/log/messages file:

Sep 23 10:47:57 proteus ifup-ppp: pppd started for ppp0 on /dev/modem at 115200
Sep 23 10:47:57 proteus ifup-ppp: pppd started for ppp0 on /dev/modem at 115200
Sep 23 10:47:58 proteus kernel: CSLIP: code copyright 1989 Regents of the University of California
Sep 23 10:47:58 proteus kernel: PPP: version 2.2.0 (dynamic channel allocation)
Sep 23 10:47:58 proteus kernel: PPP Dynamic channel allocation code copyright 1995 Caldera, Inc.
Sep 23 10:47:58 proteus kernel: PPP line discipline registered.
Sep 23 10:47:58 proteus kernel: registered device ppp0
Sep 23 10:47:58 proteus pppd[573]: pppd 2.2.0 started by root, uid 0
Sep 23 10:47:58 proteus pppd[573]: pppd 2.2.0 started by root, uid 0
Sep 23 10:47:59 proteus chat[577]: abort on (BUSY) 
Sep 23 10:47:59 proteus chat[577]: abort on (ERROR) 
Sep 23 10:47:59 proteus chat[577]: abort on (NO CARRIER) 
Sep 23 10:47:59 proteus chat[577]: abort on (NO DIALTONE) 
Sep 23 10:47:59 proteus chat[577]: abort on (Invalid Login) 
Sep 23 10:47:59 proteus chat[577]: abort on (Login incorrect) 
Sep 23 10:47:59 proteus chat[577]: send (ATZ^M) 
Sep 23 10:47:59 proteus chat[577]: expect (OK) 
Sep 23 10:47:59 proteus chat[577]: ATZ^M^M 
Sep 23 10:47:59 proteus chat[577]: OK -- got it 
Sep 23 10:47:59 proteus chat[577]: send (ATDT453-2906^M) 
Sep 23 10:48:00 proteus chat[577]: expect (CONNECT) 
Sep 23 10:48:00 proteus chat[577]: ^M 
Sep 23 10:48:02 proteus chat[577]: ATDT453-2906^M^M 
Sep 23 10:48:02 proteus chat[577]: NO DIAL TONE^M 
Sep 23 10:48:45 proteus chat[577]: alarm
Sep 23 10:48:45 proteus pppd[573]: Connect script failed
Sep 23 10:48:45 proteus pppd[573]: Connect script failed
Sep 23 10:48:45 proteus pppd[573]: Exit.
Sep 23 10:48:45 proteus pppd[573]: Exit.
Sep 23 10:48:45 proteus chat[577]: Failed

I believe that you should at least see messages about the 'pppd'
starting.

What's in your chat script (/etc/sysconfig/network-scripts/chat-ppp0)?  
Normally, you would use the 'Edit PPP Interface' GUI to change this,
but, of course, emacs works too.  Read the 'chat' man page, and make
sure that the chat script makes sense.

If you like, you can correspond with me directly.  Send the chat-ppp0
and ifcfg-ppp0 scripts (with passwords marked out!).  We can post a
resolution note after it's working.  Please include your phone number.