PPPD says: "LCP: timeout sending Config-Requests"

PPPD says: "LCP: timeout sending Config-Requests"

Post by T » Fri, 20 Jun 1997 04:00:00



Hello,
        I have setup ppp on my system and cannot get it to work.  The modem
connects to my ISP and the chat script runs correctly.  From
/var/log/messages:

Jun 18 19:10:20 louise chat[1372]: expect (ACS)
Jun 18 19:10:20 louise chat[1372]:  ^M
Jun 18 19:10:20 louise chat[1372]: osu-ts12-ACS -- got it
Jun 18 19:10:20 louise chat[1372]: send (PPP^M)
Jun 18 19:10:20 louise pppd[1370]: Serial connection established.
Jun 18 19:10:22 louise kernel: PPP: version 2.2.0 (dynamic channel
allocation)
Jun 18 19:10:22 louise kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc.
Jun 18 19:10:22 louise kernel: PPP line discipline registered.
Jun 18 19:10:22 louise kernel: registered device ppp0
Jun 18 19:10:22 louise pppd[1370]: Using interface ppp0
Jun 18 19:10:22 louise pppd[1370]: Connect: ppp0 <--> /dev/ttyS1
Jun 18 19:11:57 louise pppd[1370]: LCP: timeout sending Config-Requests
 /* message repeats 11 times */
Jun 18 19:31:51 louise pppd[1370]: LCP: timeout sending Config-Requests
Jun 18 19:32:38 louise pppd[1370]: Terminating on signal 15.   /* I killed
pppd */
Jun 18 19:32:38 louise pppd[1370]: Connection terminated.
Jun 18 19:33:24 louise pppd[1370]: disconnect script failed     /* I do not
have 'ppp-off' yet */
Jun 18 19:33:24 louise pppd[1370]: Exit.
Jun 18 19:33:44 louise kernel: PPP: ppp line discipline successfully
unregistered

As far as I can tell (from manually logging in with minicom), ppp does in
fact startup on the remote.

Anyone have any ideas?

My ppp-on, ppp-on-dialer, and options are included below.

ppp-on:
  #!/bin/sh
  #
  # Script to initiate a PPP connection. This is the first part of the
  # pair of scripts. This is not a secure pair of scripts as the codes
  # are visible with the 'ps' command.  However, it is simple.
  #
  # These are the parameters. Change as needed.
  TELEPHONE=xxxxxxx      # The telephone number for the connection
  ACCOUNT=xxxxxx          # The account name for logon (as in 'George
Burns')
  PASSWORD=xxxxxx         # The password for this account (and 'Gracie
Allen')
  LOCAL_IP=0.0.0.0        # Local IP address if known. Dynamic = 0.0.0.0
  REMOTE_IP=0.0.0.0       # Remote IP address if desired. Normally 0.0.0.0
  #NETMASK=255.255.255.0   # The proper netmask if needed
  #
  # Export them so that they will be available to 'ppp-on-dialer'
  export TELEPHONE ACCOUNT PASSWORD
  #
  # This is the location of the script which dials the phone and logs
  # in.  Please use the absolute file name as the $PATH variable is not
  # used on the connect option.  (To do so on a 'root' account would be
  # a security hole so don't ask.)
  #
  DIALER_SCRIPT=/etc/ppp/scripts/ppp-on-dialer
  #
  # Initiate the connection
  #
  #
  #setserial /dev/cua1 spd_normal
  exec /usr/sbin/pppd -d /dev/ttyS1 38400 \
          connect $DIALER_SCRIPT

ppp-on-dialer:
  #!/bin/sh
  #
  # This is part 2 of the ppp-on script. It will perform the connection
  # protocol for the desired connection.
  #
  chat -v                                                 \
          TIMEOUT         3                               \
          ABORT           '\nBUSY\r'                      \
          ABORT           '\nNO ANSWER\r'                 \
          ABORT           '\nRINGING\r\n\r\nRINGING\r'    \
          ''              \rAT                            \
          'OK-+++\c-OK'   ATH0                            \
          TIMEOUT         30                              \
          OK              ATDT$TELEPHONE                  \
          CONNECT         ''                              \
          name:--name:    $ACCOUNT                        \
          assword:        $PASSWORD                       \
          ACS--ACS        PPP

options:

/*all lines relevant to options I am not using removed*/

# /etc/ppp/options -*- sh -*- general options for pppd
# created 13-Jul-1995 jmk
# autodate: 01-Aug-1995
# autotime: 19:45

# Use the executable or shell command specified to set up the serial
# line.  This script would typically use the "chat" program to dial the
# modem and start the remote ppp session.
connect "/usr/sbin/chat -f /etc/ppp/homenet.chat"

# Run the executable or shell command specified after pppd has
# terminated the link.  This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
disconnect "/usr/sbin/chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it.  0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0x00

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Add a default route to the system routing tables, using the peer as
# the gateway, when IPCP negotiation is successfully completed.  This
# entry is removed when the PPP connection is broken.
defaultroute

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.  pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.  The default MRU value is 1500.  A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
mru 552

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
noipdefault

# Enables the "passive" option in the LCP.  With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
passive

# Increase debugging level (same as -d).  If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form.  The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)).  (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
debug

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
mtu 552

# Set the name of the local system for authentication purposes to <n>.
name apeden

# Set the user name to use for authenticating this machine with the peer
# using PAP to <u>.
user apeden

# If this option is given, pppd will send an LCP echo-request frame to
# the peer every n seconds. Under Linux, the echo-request is sent when
# no packets have been received from the peer for n seconds. Normally
# the peer should respond to the echo-request by sending an echo-reply.
# This option can be used with the lcp-echo-failure option to detect
# that the peer is no longer connected.
lcp-echo-interval 5

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 5

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
lcp-max-configure 30

 
 
 

1. "LCP: timeout sending Config-Requests" w/ pppd 2.1 p2

I just replaced my Slackware 2.2/kernel 1.2.1/a.out partition
with a RedHat 3.0.3/kernel 1.2.13/ELF partition and am unable
to use my old ppp configuration.

In the log, I get a message "LCP: timeout sending Config-Requests"
followed by "Connection terminated.".  I used some of the pppd options
to wait for the peer to send LCP but they only caused pppd to wait
forever.

My pppd version is 2.1 patch level 2 (Linux 1.0.1).  I don't recall
the level of pppd on my old setup, but I'm sure it is older.

I'm not getting any errors about "not 8-bit clean" like a recent
poster did.

Any common errors that might lead to timeout sending Config-Requests?

Thanks in advance,

Jeff
--

2. What is Sync. Polarity?

3. PPPD Dial-In, FreeBSD 4.3, "LCP: timeout sending Config-Requests".

4. System Reset !! Help !!

5. pppd dial ins and , "LCP: timeout sending Config-Requests"

6. QUESTION

7. pppd: "LCP: timeout sending Config-Requests"

8. NFS problems on redhat 7.3

9. Rehat 4.0 ppp: "LCP: timeout sending Config-Requests"

10. "LCP: timeout sending Config-Requests" --- whose fault?

11. ppp fails "LCP: timeout sending Config-Requests"

12. "LCP: timeout sending Config-Requests" Problem????

13. pppd fails with: LCP: timeout sending Config-Requests