LCP terminated by peer - PPP

This is a discussion on LCP terminated by peer - PPP ; Please help I can't run my dial-in server on Suse 8.2. I keep getting "LCP terminated by peer" and the ip-up script doesn't start at all. I'm dialing from WindowsNT and here is the log from /var/log/messages Jan 19 10:01:15 ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: LCP terminated by peer

  1. LCP terminated by peer

    Please help I can't run my dial-in server on Suse 8.2.
    I keep getting "LCP terminated by peer" and the ip-up script doesn't start
    at all.
    I'm dialing from WindowsNT and here is the log from /var/log/messages

    Jan 19 10:01:15 linux pppd[8399]: pppd 2.4.1 started by LOGIN, uid 0
    Jan 19 10:01:15 linux pppd[8399]: Perms of /dev/ttyS1 are ok, no 'mesg n'
    neccesary.
    Jan 19 10:01:15 linux pppd[8399]: using channel 7
    Jan 19 10:01:15 linux pppd[8399]: Using interface ppp0
    Jan 19 10:01:15 linux pppd[8399]: Connect: ppp0 <--> /dev/ttyS1
    Jan 19 10:01:15 linux pppd[8399]: sent [LCP ConfReq id=0x1
    ]
    Jan 19 10:01:15 linux pppd[8399]: rcvd [LCP ConfRej id=0x1 ]
    Jan 19 10:01:15 linux pppd[8399]: sent [LCP ConfReq id=0x2
    ]
    Jan 19 10:01:16 linux pppd[8399]: rcvd [LCP ConfAck id=0x2
    ]
    Jan 19 10:01:17 linux pppd[8399]: sent [LCP ConfReq id=0x2
    ]
    Jan 19 10:01:18 linux pppd[8399]: rcvd [LCP ConfAck id=0x2
    ]
    Jan 19 10:01:18 linux pppd[8399]: rcvd [LCP ConfReq id=0x2
    ]
    Jan 19 10:01:18 linux pppd[8399]: sent [LCP ConfAck id=0x2
    ]
    Jan 19 10:01:18 linux pppd[8399]: sent [LCP EchoReq id=0x0 magic=0x8a68104d]
    Jan 19 10:01:18 linux pppd[8399]: cbcp_lowerup
    Jan 19 10:01:18 linux pppd[8399]: want: 2
    Jan 19 10:01:18 linux pppd[8399]: rcvd [LCP EchoRep id=0x0 magic=0x29ed]
    Jan 19 10:01:19 linux pppd[8399]: rcvd [PAP AuthReq id=0x3 user="borut"
    password=]
    Jan 19 10:01:19 linux pppd[8399]: user borut logged in
    Jan 19 10:01:19 linux pppd[8399]: Script /etc/ppp/auth-up finished (pid
    8432), status = 0x0
    Jan 19 10:01:36 linux pppd[8399]: LCP terminated by peer
    Jan 19 10:01:36 linux pppd[8399]: Script /etc/ppp/auth-down finished (pid
    8435), status = 0x0
    Jan 19 10:01:37 linux pppd[8399]: Hangup (SIGHUP)
    Jan 19 10:01:37 linux pppd[8399]: Modem hangup
    Jan 19 10:01:37 linux pppd[8399]: Connection terminated.
    Jan 19 10:01:37 linux pppd[8399]: Connect time 0.4 minutes.
    Jan 19 10:01:37 linux pppd[8399]: Sent 0 bytes, received 0 bytes.
    Jan 19 10:01:37 linux pppd[8399]: Exit.


    I have this settings in my configuration files\:

    1)/etc/inittab

    mo:235:respawn:/usr/sbin/mgetty -x 9 -D -s 57600 ttyS1

    2)/etc/mgetty+sendfax/login.config

    /AutoPPP/ - a_ppp /usr/sbin/pppd file /etc/ppp/options.server

    3)/etc/mgetty+sendfax/mgetty.config
    port-owner uucp
    port-group uucp
    port-mode 0664

    4)/etc/ppp/options.server

    auth
    +pap
    -chap
    login
    lock
    modem
    crtscts
    debug
    proxyarp
    asyncmap 0
    defaultroute
    replacedefaultroute
    noipdefault
    noipx
    kdebug 4
    ms-dns 10.1.0.200
    ms-wins 10.1.0.200

    and the default settings:
    nodetach
    lcp-echo-interval 30
    lcp-echo-failure 4
    lcp-max-configure 60
    lcp-restart 2
    idle 600
    5)/etc/ppp/pap-secrets

    * * ""




  2. Re: LCP terminated by peer

    Please review the answers posted to your same question on the various linux
    newsgroups. One of those answers is mine.

    On Mon, 26 Jan 2004 15:07:28 +0100, "Borut" wrote:

    >Please help I can't run my dial-in server on Suse 8.2.
    >I keep getting "LCP terminated by peer" and the ip-up script doesn't start
    >at all.


    >I'm dialing from WindowsNT and here is the log from /var/log/messages
    >
    >Jan 19 10:01:15 linux pppd[8399]: pppd 2.4.1 started by LOGIN, uid 0
    >Jan 19 10:01:15 linux pppd[8399]: Perms of /dev/ttyS1 are ok, no 'mesg n'
    >neccesary.
    >Jan 19 10:01:15 linux pppd[8399]: using channel 7
    >Jan 19 10:01:15 linux pppd[8399]: Using interface ppp0
    >Jan 19 10:01:15 linux pppd[8399]: Connect: ppp0 <--> /dev/ttyS1
    >Jan 19 10:01:15 linux pppd[8399]: sent [LCP ConfReq id=0x1
    > ]

    [snip]
    >Jan 19 10:01:18 linux pppd[8399]: rcvd [LCP ConfAck id=0x2
    > ]


    Up to this point, everything looks normal.

    >Jan 19 10:01:18 linux pppd[8399]: rcvd [LCP ConfReq id=0x2
    > ]


    The WinNT box asks the Linux box if it is willing to participate in the
    "callback CBCP"

    >Jan 19 10:01:18 linux pppd[8399]: sent [LCP ConfAck id=0x2
    > ]


    The Linux box agrees to participate in the "callback CBCP"


    >Jan 19 10:01:18 linux pppd[8399]: sent [LCP EchoReq id=0x0 magic=0x8a68104d]
    >Jan 19 10:01:18 linux pppd[8399]: cbcp_lowerup
    >Jan 19 10:01:18 linux pppd[8399]: want: 2
    >Jan 19 10:01:18 linux pppd[8399]: rcvd [LCP EchoRep id=0x0 magic=0x29ed]
    >Jan 19 10:01:19 linux pppd[8399]: rcvd [PAP AuthReq id=0x3 user="borut"
    >password=]
    >Jan 19 10:01:19 linux pppd[8399]: user borut logged in
    >Jan 19 10:01:19 linux pppd[8399]: Script /etc/ppp/auth-up finished (pid
    >8432), status = 0x0


    The initial stage of the callback is performed. Linux now knows which user to
    call back.

    >Jan 19 10:01:36 linux pppd[8399]: LCP terminated by peer
    >Jan 19 10:01:36 linux pppd[8399]: Script /etc/ppp/auth-down finished (pid
    >8435), status = 0x0
    >Jan 19 10:01:37 linux pppd[8399]: Hangup (SIGHUP)
    >Jan 19 10:01:37 linux pppd[8399]: Modem hangup
    >Jan 19 10:01:37 linux pppd[8399]: Connection terminated.
    >Jan 19 10:01:37 linux pppd[8399]: Connect time 0.4 minutes.
    >Jan 19 10:01:37 linux pppd[8399]: Sent 0 bytes, received 0 bytes.
    >Jan 19 10:01:37 linux pppd[8399]: Exit.


    At this point, the WinNT box is waiting for Linux to honour the negotiated
    callback CBCP. Your linux pppd should have exited with a returncode indicating
    that a callback had been negotiated. So, go ahead and have the Linux box
    complete the negotiated callback.

    [snip]

    --
    Lew Pitcher
    IT Consultant, Enterprise Technology Solutions
    Toronto Dominion Bank Financial Group

    (Opinions expressed are my own, not my employers')

  3. Re: LCP terminated by peer

    Lew.Pitcher@td.com (Lew Pitcher) writes:
    > >Jan 19 10:01:18 linux pppd[8399]: sent [LCP ConfAck id=0x2
    > > ]

    >
    > The Linux box agrees to participate in the "callback CBCP"


    This is a vendor-broken version of pppd. There aren't any versions
    that support the server side of CBCP.

    Lose this hacked version of pppd and download the real one from
    samba.org.

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  4. Re: LCP terminated by peer

    James Carlson wrote:
    > Lew.Pitcher@td.com (Lew Pitcher) writes:
    >> >Jan 19 10:01:18 linux pppd[8399]: sent [LCP ConfAck id=0x2
    >> > ]

    >>
    >> The Linux box agrees to participate in the "callback CBCP"


    > This is a vendor-broken version of pppd. There aren't any versions
    > that support the server side of CBCP.


    > Lose this hacked version of pppd and download the real one from
    > samba.org.


    Yes, I told the OP the same thing (although a lot less succinctly) on the
    23rd when he posted about the same problem on COLN. Maybe now he will,
    with your credentials.

    Last time it was Red Hat 7.2 that had the broken server side CBCP...

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/

+ Reply to Thread