SuSE GmbH

SuSE Support Database

Title: ISDN: syncPPP can't be established

----------

Mainpage o Searchform o History o Versions o Categories o Contents
Deutsch

----------

ISDN: syncPPP can't be established

Symptom:

The ISDN card is detected, the ISDN configuration seems to be OK, the provider is called, but no connection is established.

Cause:

The PPP negociation doesn't work. There can be several reasons for this, e.g.:

Solution:

Start the ipppd with the debug option; more outputs are created by the PPP handshake in /var/log/messages, which help to narrow down the problem.

Enter in /etc/ppp/options (or the one you use) a line:

debug
Hint:When the connection works, undo these changes again, because only many unnecessary outputs are created.

If you have discovered and solved a problem that is not described here, please send me a short report, so it can be described here.

Possible causes:

  • No synchronous PPP is used on the opposite side.

    In /var/log/messages (with debug outputs), there is something like the following:

    Jan 19 15:56:33 ninja kernel: ippp0: dialing 0 1234...
    Jan 19 15:56:33 ninja isdnlog: Jan 19 15:56:33 * tei 94 calling 07721/1234, Villingen-Schwenning with HDLC  RING (Data) 
    Jan 19 15:56:37 ninja isdnlog: Jan 19 15:56:37 tei 94 calling 07721/1234, Villingen-Schwenning with HDLC  Time:Sun Jan 19 15:49:00 1997 
    Jan 19 15:56:37 ninja isdnlog: Jan 19 15:56:37 tei 94 calling 07721/1234, Villingen-Schwenning with HDLC  CONNECT (Data) 
    Jan 19 15:56:37 ninja kernel: isdn_net: ippp0 connected
    Jan 19 15:56:37 ninja pppd[90]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 0, linkunit: 0, fd: 5
    Jan 19 15:56:37 ninja pppd[90]: sent [0][LCP ConfReq id=0x1  ]
    Jan 19 15:57:04 ninja last message repeated 9 times
    Jan 19 15:57:07 ninja pppd[90]: LCP: timeout sending Config-Requests
    Jan 19 15:57:07 ninja pppd[90]: Connection terminated.
    Jan 19 15:57:07 ninja pppd[90]: taking down PHASE_DEAD link 0, linkunit: 0
    Jan 19 15:57:07 ninja pppd[90]: link 0 closed , linkunit: 0
    Jan 19 15:57:07 ninja pppd[90]: reinit_unit: 0 
    Jan 19 15:57:07 ninja pppd[90]: Connect[0]: /dev/ippp0, fd: 5
    Jan 19 15:57:07 ninja kernel: isdn_net: local hangup ippp0
    Jan 19 15:57:07 ninja kernel: ippp0: Chargesum is 0
    

    Solution: Use asynchronous PPP, see below.

  • The remote station is a Netblazer

    The remote station doesn't answer a CCP-request, after a timeout the connection is being cut.

    The protocol looks like the following :

    May 22 00:57:09 loki pppd[93]: local  IP address 194.25.217.89
    May 22 00:57:09 loki pppd[93]: remote IP address 194.25.217.97
    May 22 00:57:12 loki pppd[93]: sent [0][CCP ConfReq id=0x1]
    [..]
    May 22 00:57:36 loki pppd[93]: sent [0][CCP ConfReq id=0x1]
    May 22 00:57:36 loki pppd[93]: rcvd [0][CCP ConfNak id=0x1 < 05 05 00 01 03>]
    May 22 00:57:39 loki pppd[93]: CCP: timeout sending Config-Requests
    May 22 00:57:39 loki pppd[93]: rcvd [0][CCP ConfReq id=0xb]
    May 22 00:57:39 loki pppd[93]: sent [0][CCP ConfReq id=0x2]
    May 22 00:57:39 loki pppd[93]: sent [0][CCP ConfAck id=0xb]
    May 22 00:57:39 loki pppd[93]: rcvd [0][CCP ConfAck id=0x2]
    May 22 00:58:24 loki kernel: isdn_net: local hangup ippp0
    May 22 00:58:24 loki kernel: ippp0: Chargesum is 0
    
    Solution : Set the option noccp in /etc/ppp/options.ippp0

    ----------

    See also:

    ----------

    Keywords: ISDN, PPP, SYNCPPP, IPPPD, TROUBLE

    ----------

    Categories: Configuration , PPP

    ----------

    Feedback welcome: Send Mail to kfr@suse.de (Please give the following subject: SDB-ipppd)

    ----------

    Mainpage o Searchform o History o Versions o Categories o Contents
    Deutsch

    ----------

    SDB-ipppd, Copyright SuSE GmbH, Nuremberg, Germany - Version: 10. Mar 1998
    SuSE GmbH - Last generated: 07. Oct 1999 16:41:43 by maddin with sdb_gen 1.00.0