ppp daemon has died (exit code=10) - PPP

This is a discussion on ppp daemon has died (exit code=10) - PPP ; Hello, I use an Olitec 56K winmodem fully compatible with Mandrake 9.1 and Wvdial to get online...I installed the kdenetwork_kppp package from the CD. I also installed Wvdial and set up the wvdial.conf with my ISP details to get it ...

+ Reply to Thread
Results 1 to 20 of 20

Thread: ppp daemon has died (exit code=10)

  1. ppp daemon has died (exit code=10)

    Hello,

    I use an Olitec 56K winmodem fully compatible with Mandrake 9.1 and
    Wvdial to get online...I installed the kdenetwork_kppp package from
    the CD. I also installed Wvdial and set up the wvdial.conf with my ISP
    details to get it working. But I never get connected, when I launch
    wvdial here is what happens:
    --> WvDial: Internet dialer version 1.53
    --> Initializing modem.
    --> Sending: ATZ
    ATZ
    OK
    --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
    OK
    --> Modem initialized.
    --> Sending: ATDT08089996356
    --> Waiting for carrier.
    ATDT08089996356
    NO CARRIER
    --> No Carrier! Trying again.
    --> Sending: ATDT08089996356
    --> Waiting for carrier.
    ATDT08089996356
    CONNECT 115200
    ~[7f]}#@!}!x} +}!}$}&@}%}&}6};Jk}"}&} } } } }1}$}&@}7}$} l}
    }"}#}$@#}3})}#}(} }#}*/v4e~
    --> Carrier detected. Waiting for prompt.
    ~[7f]}#@!}!y} +}!}$}&@}%}&}6};Jk}"}&} } } } }1}$}&@}7}$} l}
    }"}#}$@#}3})}#}(} }#}*/v[18]G~
    --> PPP negotiation detected.
    --> Starting pppd at Tue Feb 10 19:17:27 2004
    --> pid of pppd: 2112
    --> Disconnecting at Tue Feb 10 19:17:49 2004
    --> The PPP daemon has died: PPP negotiation failed (exit code = 10)
    --> man pppd explains pppd error codes in more detail.
    --> I guess that's it for now, exiting
    --> The PPP daemon has died. (exit code = 10)

    Then I TAKE A LOOK AT LOG FILES:
    tail /var/log/messages;
    Feb 5 19:13:42 localhost pppd[2215]: pppd 2.4.1 started by root, uid
    0
    Feb 5 19:13:42 localhost pppd[2215]: Using interface ppp0
    Feb 5 19:13:42 localhost pppd[2215]: Connect: ppp0 <--> /dev/ttySHSF0
    Feb 5 19:13:43 localhost /etc/hotplug/net.agent: assuming ppp0 is
    already up
    Feb 5 19:14:00 localhost pppd[2215]: LCP terminated by peer
    Feb 5 19:14:03 localhost pppd[2215]: Connection terminated.
    Feb 5 19:14:03 localhost pppd[2215]: Exit.
    Feb 5 19:14:03 localhost /etc/hotplug/net.agent: NET unregister event
    not supported

    tail /var/log/syslog;
    LCP terminated by peer
    connection terminated are the 2 main lines...

    I do not know what is wrong because I constantly followed the man
    pages to install and set up wvdial. I consulted several websites about
    wvdial config. Maybe it has not to do with wvdial? maybe it is ppp, I
    just installed the rpm file and did nothing else to configure ppp as
    discribed. Could you help me to find out?
    I have no other clue but these log files. Please post me suggestions.
    I'd be grateful for any help!

  2. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:
    > --> The PPP daemon has died: PPP negotiation failed (exit code = 10)
    > --> man pppd explains pppd error codes in more detail.


    Exit code 10 means that no network layer protocols were able to run.

    > Feb 5 19:13:42 localhost pppd[2215]: Connect: ppp0 <--> /dev/ttySHSF0
    > Feb 5 19:13:43 localhost /etc/hotplug/net.agent: assuming ppp0 is
    > already up
    > Feb 5 19:14:00 localhost pppd[2215]: LCP terminated by peer


    Set up the pppd configuration to include the "debug" option. There's
    not much information available otherwise.

    At a guess, something is going amiss in the IPCP negotiation, perhaps
    due to a bug at the peer's end. Such things aren't terribly uncommon.

    --
    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

  3. Re: ppp daemon has died (exit code=10)

    Thank you for your answers...

    James Carlson wrote in message news:...
    > lap1974_sen@yahoo.co.uk (lolo) writes:
    > > --> The PPP daemon has died: PPP negotiation failed (exit code = 10)
    > > --> man pppd explains pppd error codes in more detail.

    >
    > Exit code 10 means that no network layer protocols were able to run.
    >

    does it mean that something is wrong in kppp? I just double clicked on
    the rpm package to install it...

    > > Feb 5 19:13:42 localhost pppd[2215]: Connect: ppp0 <--> /dev/ttySHSF0
    > > Feb 5 19:13:43 localhost /etc/hotplug/net.agent: assuming ppp0 is
    > > already up
    > > Feb 5 19:14:00 localhost pppd[2215]: LCP terminated by peer

    >
    > Set up the pppd configuration to include the "debug" option. There's
    > not much information available otherwise.


    I ll try this but I have no clue how to set it up at the moment. I ll
    post the log when I have found this option to have more details.
    >
    > At a guess, something is going amiss in the IPCP negotiation, perhaps
    > due to a bug at the peer's end. Such things aren't terribly uncommon.


    what do you mean? a pb at my ISP side?

  4. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:
    > > Exit code 10 means that no network layer protocols were able to run.
    > >

    > does it mean that something is wrong in kppp? I just double clicked on
    > the rpm package to install it...


    No. kppp is just an obscuring wrapper atop of pppd. As long as PPP
    is running, it's mostly unlikely that kppp did anything wrong.

    > > Set up the pppd configuration to include the "debug" option. There's
    > > not much information available otherwise.

    >
    > I ll try this but I have no clue how to set it up at the moment. I ll
    > post the log when I have found this option to have more details.


    I don't know or use kppp, but the following (assuming Linux) should do
    the job:

    # touch /etc/ppp/options
    # echo debug >> /etc/ppp/options
    # echo daemon.debug /var/log/debug >> /etc/syslog.conf
    # touch /var/log/debug
    # killall -HUP syslogd

    Then try logging in again, and look at the end of the /var/log/debug
    file. Post *all* messages from 'pppd'.

    > > At a guess, something is going amiss in the IPCP negotiation, perhaps
    > > due to a bug at the peer's end. Such things aren't terribly uncommon.

    >
    > what do you mean? a pb at my ISP side?


    Yes. But there are work-arounds for some known ISP bugs. You need to
    find out what the problem is first, though.

    --
    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

  5. Re: ppp daemon has died (exit code=10)

    Many thanks, James, for your advice.
    This is my /var/log/debug file (it doesn't tell me anything!!)and I am
    afraid it is a long file , the beginning seems to be as important as
    the end so I posted it all...

    Feb 12 20:07:57 localhost pppd[1856]: pppd 2.4.1 started by root, uid
    0
    Feb 12 20:07:57 localhost pppd[1856]: using channel 1
    Feb 12 20:07:58 localhost pppd[1856]: Using interface ppp0
    Feb 12 20:07:58 localhost pppd[1856]: Connect: ppp0 <--> /dev/ttySHSF0
    Feb 12 20:07:58 localhost pppd[1856]: sent [LCP ConfReq id=0x1
    ]
    Feb 12 20:07:58 localhost pppd[1856]: rcvd [LCP ConfAck id=0x1
    ]
    Feb 12 20:08:00 localhost pppd[1856]: rcvd [LCP ConfReq id=0xfe 1600> < 17 04 02 fe> <
    00 02> ]
    Feb 12 20:08:00 localhost pppd[1856]: sent [LCP ConfRej id=0xfe 1600> < 17 04 02 fe> < 00 02> ]
    Feb 12 20:08:00 localhost pppd[1856]: rcvd [LCP ConfReq id=0xff 1600> [MAC:08:00:03:0a:2f:f6]>]
    Feb 12 20:08:00 localhost pppd[1856]: sent [LCP ConfAck id=0xff 1600> [MAC:08:00:03:0a:2f:f6]>]
    Feb 12 20:08:00 localhost pppd[1856]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 12 20:08:00 localhost pppd[1856]: sent [CCP ConfReq id=0x1
    ]
    Feb 12 20:08:00 localhost pppd[1856]: rcvd [proto=0xc029] 01 00 00 06
    01 02
    Feb 12 20:08:00 localhost pppd[1856]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 12 20:08:00 localhost pppd[1856]: sent [LCP ProtRej id=0x2 c0 29
    01 00 00 06 01 02]
    Feb 12 20:08:03 localhost pppd[1856]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 12 20:08:03 localhost pppd[1856]: rcvd [proto=0xc029] 01 01 00 06
    01 02
    Feb 12 20:08:03 localhost pppd[1856]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 12 20:08:03 localhost pppd[1856]: sent [LCP ProtRej id=0x3 c0 29
    01 01 00 06 01 02]
    Feb 12 20:08:03 localhost pppd[1856]: sent [CCP ConfReq id=0x1
    ]
    Feb 12 20:08:06 localhost pppd[1856]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 12 20:08:06 localhost pppd[1856]: rcvd [proto=0xc029] 01 02 00 06
    01 02
    Feb 12 20:08:06 localhost pppd[1856]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 12 20:08:06 localhost pppd[1856]: sent [LCP ProtRej id=0x4 c0 29
    01 02 00 06 01 02]
    Feb 12 20:08:06 localhost pppd[1856]: sent [CCP ConfReq id=0x1
    ]
    Feb 12 20:08:09 localhost pppd[1856]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 12 20:08:09 localhost pppd[1856]: rcvd [proto=0xc029] 01 03 00 06
    01 02
    Feb 12 20:08:09 localhost pppd[1856]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 12 20:08:09 localhost pppd[1856]: sent [LCP ProtRej id=0x5 c0 29
    01 03 00 06 01 02]
    Feb 12 20:08:09 localhost pppd[1856]: sent [CCP ConfReq id=0x1
    ]
    Feb 12 20:08:12 localhost pppd[1856]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 12 20:08:12 localhost pppd[1856]: rcvd [proto=0xc029] 01 04 00 06
    01 02
    Feb 12 20:08:12 localhost pppd[1856]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 12 20:08:12 localhost pppd[1856]: sent [LCP ProtRej id=0x6 c0 29
    01 04 00 06 01 02]
    Feb 12 20:08:12 localhost pppd[1856]: sent [CCP ConfReq id=0x1
    ]
    Feb 12 20:08:15 localhost pppd[1856]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 12 20:08:15 localhost pppd[1856]: rcvd [LCP TermReq id=0x9b]
    Feb 12 20:08:15 localhost pppd[1856]: LCP terminated by peer
    Feb 12 20:08:15 localhost pppd[1856]: sent [LCP TermAck id=0x9b]
    Feb 12 20:08:15 localhost pppd[1856]: rcvd [LCP ConfReq id=0x0 1600> < 17 04 02 fe> <
    00 02> ]
    Feb 12 20:08:15 localhost pppd[1856]: rcvd [LCP TermReq id=0x9c]
    Feb 12 20:08:15 localhost pppd[1856]: sent [LCP TermAck id=0x9c]
    Feb 12 20:08:18 localhost pppd[1856]: Connection terminated.
    Feb 12 20:08:18 localhost pppd[1856]: Exit.

    I hope you can understand something from it.

    >
    > Yes. But there are work-arounds for some known ISP bugs. You need to
    > find out what the problem is first, though.


    I am gonna ask them for PAP or CHAP just in case...
    Thanks a lot for your help!

  6. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:
    > Many thanks, James, for your advice.
    > This is my /var/log/debug file (it doesn't tell me anything!!)and I am
    > afraid it is a long file , the beginning seems to be as important as
    > the end so I posted it all...


    Thanks; that's exactly how to handle it.

    > Feb 12 20:08:00 localhost pppd[1856]: rcvd [LCP ConfReq id=0xfe > 1600> < 17 04 02 fe> <
    > 00 02> ]
    > Feb 12 20:08:00 localhost pppd[1856]: sent [LCP ConfRej id=0xfe > 1600> < 17 04 02 fe> < 00 02> ]


    The peer is requesting that you identify yourself using PAP. You
    refuse to identify yourself by *any* means.

    Your /etc/ppp/{pap,chap}-secrets file are probably misconfigured.

    > Feb 12 20:08:00 localhost pppd[1856]: rcvd [proto=0xc029] 01 00 00 06
    > 01 02
    > Feb 12 20:08:00 localhost pppd[1856]: Unsupported protocol 'CallBack
    > Control Protocol (CBCP)' (0xc029) received


    That's strange. You didn't negotiate callback at the LCP level, but
    the peer is trying to use CBCP. That's not right.

    Perhaps it's because you refused authentication.

    > Feb 12 20:08:15 localhost pppd[1856]: rcvd [LCP TermReq id=0x9c]
    > Feb 12 20:08:15 localhost pppd[1856]: sent [LCP TermAck id=0x9c]


    The peer gives up on you.

    You need to have something like this in the pppd configuration:

    user your-user-name

    and this in /etc/ppp/pap-secrets:

    your-user-name * "your password" *

    --
    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

  7. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:

    ]Hello,

    ]I use an Olitec 56K winmodem fully compatible with Mandrake 9.1 and
    ]Wvdial to get online...I installed the kdenetwork_kppp package from
    ]the CD. I also installed Wvdial and set up the wvdial.conf with my ISP
    ]details to get it working. But I never get connected, when I launch
    ]wvdial here is what happens:

    Try following www.theory.physics.ubc.ca/ppp-linux.html. wvdial can
    sometimes be very stupid and if it does not work out of the box, vary
    difficult to debug.


  8. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:

    ]Many thanks, James, for your advice.
    ]This is my /var/log/debug file (it doesn't tell me anything!!)and I am
    ]afraid it is a long file , the beginning seems to be as important as
    ]the end so I posted it all...
    The other end wants Callback, you cannot supply. End of game, set and
    match. Find out why they want callback or find a new ISP.


    ]Feb 12 20:08:00 localhost pppd[1856]: sent [LCP ConfRej id=0xfe ]1600> < 17 04 02 fe> < 00 02> ]

    SEt up /etc/ppp/pap-secrets properly and use the user username option.



    ]I hope you can understand something from it.

    I think when you rejected pap, they went to callback. You cannot do it.


    ]>
    ]> Yes. But there are work-arounds for some known ISP bugs. You need to
    ]> find out what the problem is first, though.

    ]I am gonna ask them for PAP or CHAP just in case...

    Uh, they ask you for pap, you reject it.

    ]Thanks a lot for your help!


  9. Re: ppp daemon has died (exit code=10)

    Thanks very much , James, It becomes clearer! actually I need to
    configure ppp to get on line though.

    > You need to have something like this in the pppd configuration:
    >
    > user your-user-name
    >


    OK but in which file?...I ll see the relevant ones and let you know.

    > and this in /etc/ppp/pap-secrets:
    >
    > your-user-name * "your password" *


    I am going to check 'pap-secrets' out and to amend it. I keep you
    posted!

  10. Re: ppp daemon has died (exit code=10)

    Thanks for that.

    > SEt up /etc/ppp/pap-secrets properly and use the user username option.


    I will amend this file, but what's that, 'The user username option' ?
    ....I will take a look at it though.

  11. Re: ppp daemon has died (exit code=10)

    > Try following www.theory.physics.ubc.ca/ppp-linux.html. wvdial can
    > sometimes be very stupid and if it does not work out of the box, vary
    > difficult to debug.


    This doc is very helpful indeed. Many thanks for the tip!!
    I will do changes and let you know about.

  12. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:
    > Thanks very much , James, It becomes clearer! actually I need to
    > configure ppp to get on line though.
    >
    > > You need to have something like this in the pppd configuration:
    > >
    > > user your-user-name
    > >

    >
    > OK but in which file?...I ll see the relevant ones and let you know.


    Any place that takes pppd options will do. /etc/ppp/options is sort
    of brute-force, but will likely suffice in this case. A better place
    would be in /etc/ppp/peers/your-isp-name (if you use the "call"
    option) or on the pppd command line itself.

    See the pppd man page for details ...

    --
    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

  13. Re: ppp daemon has died (exit code=10)

    James, help help help!! I am puzzled.

    I did all that you stipulated and it seemed to work fine on saturday.
    Then I installed flashplayer and realplayer on my distribution on
    sunday to complete the package...But it's not connecting anymore then
    and have no clue why. I think it has nothing to do with pppd but that
    is strange. I guess from the debug file that there is again an
    protocol exchange pb between my ISP and I which ends in callback. I
    enclosed my debug file to show ppp behaviour.
    NB: my access to the net is permitted now ,PAP exchange succeeding.
    I hope that can help to suggest anything. Thanks again for your time.

    Feb 15 18:43:45 localhost pppd[1910]: pppd 2.4.1 started by root, uid
    0
    Feb 15 18:43:45 localhost pppd[1910]: using channel 1
    Feb 15 18:43:46 localhost pppd[1910]: Using interface ppp0
    Feb 15 18:43:46 localhost pppd[1910]: Connect: ppp0 <--> /dev/ttySHSF0
    Feb 15 18:43:46 localhost pppd[1910]: sent [LCP ConfReq id=0x1
    ]
    Feb 15 18:43:46 localhost pppd[1910]: rcvd [LCP ConfAck id=0x1
    ]
    Feb 15 18:43:46 localhost pppd[1910]: rcvd [LCP ConfReq id=0xf9 1600> < 17 04 01 4d> <
    00 02> ]
    Feb 15 18:43:46 localhost pppd[1910]: sent [LCP ConfRej id=0xf9 1600> < 17 04 01 4d> < 00 02>]
    Feb 15 18:43:47 localhost pppd[1910]: rcvd [LCP ConfReq id=0xfa 1600> [MAC:08:00:03:0a:2f:f6]>]
    Feb 15 18:43:47 localhost pppd[1910]: sent [LCP ConfAck id=0xfa 1600> [MAC:08:00:03:0a:2f:f6]>]
    Feb 15 18:43:47 localhost pppd[1910]: sent [PAP AuthReq id=0x1
    user="lsen@fa.net" password=]
    Feb 15 18:43:50 localhost pppd[1910]: sent [PAP AuthReq id=0x2
    user="lsen@fa.net" password=]
    Feb 15 18:43:50 localhost pppd[1910]: rcvd [PAP AuthAck id=0x2 "Access
    permitted for user \"lsen@fa.net\"\r\n"]
    Feb 15 18:43:50 localhost pppd[1910]: Remote message: Access permitted
    for user "lsen@fa.net"^M^J
    Feb 15 18:43:50 localhost pppd[1910]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 15 18:43:51 localhost pppd[1910]: sent [CCP ConfReq id=0x1
    ]
    Feb 15 18:43:51 localhost pppd[1910]: rcvd [proto=0xc029] 01 00 00 06
    01 02
    Feb 15 18:43:51 localhost pppd[1910]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 15 18:43:51 localhost pppd[1910]: sent [LCP ProtRej id=0x2 c0 29
    01 00 00 06 01 02]
    Feb 15 18:43:53 localhost pppd[1910]: rcvd [proto=0xc029] 01 01 00 06
    01 02
    Feb 15 18:43:53 localhost pppd[1910]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 15 18:43:53 localhost pppd[1910]: sent [LCP ProtRej id=0x3 c0 29
    01 01 00 06 01 02]
    Feb 15 18:43:53 localhost pppd[1910]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 15 18:43:54 localhost pppd[1910]: sent [CCP ConfReq id=0x1
    ]
    Feb 15 18:43:56 localhost pppd[1910]: rcvd [proto=0xc029] 01 02 00 06
    01 02
    Feb 15 18:43:56 localhost pppd[1910]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 15 18:43:56 localhost pppd[1910]: sent [LCP ProtRej id=0x4 c0 29
    01 02 00 06 01 02]
    Feb 15 18:43:56 localhost pppd[1910]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 15 18:43:57 localhost pppd[1910]: sent [CCP ConfReq id=0x1
    ]
    Feb 15 18:43:59 localhost pppd[1910]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 15 18:43:59 localhost pppd[1910]: rcvd [proto=0xc029] 01 03 00 06
    01 02
    Feb 15 18:43:59 localhost pppd[1910]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 15 18:43:59 localhost pppd[1910]: sent [LCP ProtRej id=0x5 c0 29
    01 03 00 06 01 02]
    Feb 15 18:44:00 localhost pppd[1910]: sent [CCP ConfReq id=0x1
    ]
    Feb 15 18:44:02 localhost pppd[1910]: rcvd [proto=0xc029] 01 04 00 06
    01 02
    Feb 15 18:44:02 localhost pppd[1910]: Unsupported protocol 'CallBack
    Control Protocol (CBCP)' (0xc029) received
    Feb 15 18:44:02 localhost pppd[1910]: sent [LCP ProtRej id=0x6 c0 29
    01 04 00 06 01 02]
    Feb 15 18:44:02 localhost pppd[1910]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 15 18:44:03 localhost pppd[1910]: sent [CCP ConfReq id=0x1
    ]
    Feb 15 18:44:05 localhost pppd[1910]: sent [IPCP ConfReq id=0x1 0.0.0.0> ]
    Feb 15 18:44:05 localhost pppd[1910]: rcvd [LCP TermReq id=0xa8]
    Feb 15 18:44:05 localhost pppd[1910]: LCP terminated by peer
    Feb 15 18:44:05 localhost pppd[1910]: sent [LCP TermAck id=0xa8]
    Feb 15 18:44:05 localhost pppd[1910]: rcvd [LCP ConfReq id=0xfb 1600> < 17 04 01 4d> <
    00 02> ]
    Feb 15 18:44:05 localhost pppd[1910]: rcvd [LCP TermReq id=0xa9]
    Feb 15 18:44:05 localhost pppd[1910]: sent [LCP TermAck id=0xa9]
    Feb 15 18:44:08 localhost pppd[1910]: Hangup (SIGHUP)
    Feb 15 18:44:08 localhost pppd[1910]: Modem hangup
    Feb 15 18:44:08 localhost pppd[1910]: Connection terminated.
    Feb 15 18:44:08 localhost pppd[1910]: Exit.

  14. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:

    ]James, help help help!! I am puzzled.

    ]I did all that you stipulated and it seemed to work fine on saturday.
    ]Then I installed flashplayer and realplayer on my distribution on
    ]sunday to complete the package...But it's not connecting anymore then
    ]and have no clue why. I think it has nothing to do with pppd but that
    ]is strange. I guess from the debug file that there is again an
    ]protocol exchange pb between my ISP and I which ends in callback. I
    ]enclosed my debug file to show ppp behaviour.

    They want callback. You do not. That is the end of it. In case of
    irreconcilable disagreement, no connection. Phone them and
    ask why they are asking for callback.

    ]Feb 15 18:43:51 localhost pppd[1910]: rcvd [proto=0xc029] 01 00 00 06
    ]01 02
    ]Feb 15 18:43:51 localhost pppd[1910]: Unsupported protocol 'CallBack
    ]Control Protocol (CBCP)' (0xc029) received
    ]Feb 15 18:43:51 localhost pppd[1910]: sent [LCP ProtRej id=0x2 c0 29
    ]01 00 00 06 01 02]
    ]Feb 15 18:43:53 localhost pppd[1910]: rcvd [proto=0xc029] 01 01 00 06
    ]01 02
    ]Feb 15 18:43:53 localhost pppd[1910]: Unsupported protocol 'CallBack
    ]Control Protocol (CBCP)' (0xc029) received
    ]Feb 15 18:43:53 localhost pppd[1910]: sent [LCP ProtRej id=0x3 c0 29
    ]01 01 00 06 01 02]

  15. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:
    > I did all that you stipulated and it seemed to work fine on saturday.
    > Then I installed flashplayer and realplayer on my distribution on
    > sunday to complete the package...But it's not connecting anymore then


    I don't think those have anything to do with the problem.

    > Feb 15 18:43:46 localhost pppd[1910]: sent [LCP ConfReq id=0x1
    > ]
    > Feb 15 18:43:46 localhost pppd[1910]: rcvd [LCP ConfAck id=0x1
    > ]
    > Feb 15 18:43:47 localhost pppd[1910]: rcvd [LCP ConfReq id=0xfa > 1600> > [MAC:08:00:03:0a:2f:f6]>]
    > Feb 15 18:43:47 localhost pppd[1910]: sent [LCP ConfAck id=0xfa > 1600> > [MAC:08:00:03:0a:2f:f6]>]


    LCP is brought up -- note that no callback was requested here.

    > Feb 15 18:43:51 localhost pppd[1910]: rcvd [proto=0xc029] 01 00 00 06
    > 01 02
    > Feb 15 18:43:51 localhost pppd[1910]: Unsupported protocol 'CallBack
    > Control Protocol (CBCP)' (0xc029) received


    Your peer starts asking for Microsoft's proprietary callback
    mechanism, even though it never negotiated the use of that during LCP.
    The peer is obviously quite broken. I don't think there's much you
    can do about this from your end.

    Most likely, this ISP has a large number of access servers, with some
    sort of call-distribution mechanism in front of them. On the days
    when you dial in and hit one of the "good" ones, all is well. When
    you hit a "bad" one, it doesn't work.

    Given the unlikelihood of being able to interest anyone at the ISP in
    fixing the problem, my advice would be to find an ISP that doesn't use
    broken equipment.

    --
    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

  16. Re: ppp daemon has died (exit code=10)

    unruh@string.physics.ubc.ca (Bill Unruh) wrote in message news:...
    > lap1974_sen@yahoo.co.uk (lolo) writes:
    >
    > ]James, help help help!! I am puzzled.
    >
    > ]I did all that you stipulated and it seemed to work fine on saturday.
    > ]Then I installed flashplayer and realplayer on my distribution on
    > ]sunday to complete the package...But it's not connecting anymore then
    > ]and have no clue why. I think it has nothing to do with pppd but that
    > ]is strange. I guess from the debug file that there is again an
    > ]protocol exchange pb between my ISP and I which ends in callback. I
    > ]enclosed my debug file to show ppp behaviour.
    >
    > They want callback. You do not. That is the end of it. In case of
    > irreconcilable disagreement, no connection. Phone them and
    > ask why they are asking for callback.
    >
    > ]Feb 15 18:43:51 localhost pppd[1910]: rcvd [proto=0xc029] 01 00 00 06
    > ]01 02
    > ]Feb 15 18:43:51 localhost pppd[1910]: Unsupported protocol 'CallBack
    > ]Control Protocol (CBCP)' (0xc029) received


    Thanks. I will.

  17. Re: ppp daemon has died (exit code=10)

    James Carlson wrote:

    > Most likely, this ISP has a large number of access servers, with some
    > sort of call-distribution mechanism in front of them. On the days
    > when you dial in and hit one of the "good" ones, all is well. When
    > you hit a "bad" one, it doesn't work.


    Good point. It also would be interesting to know whether the CBCP
    message appears in any successful connection...

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

  18. Re: ppp daemon has died (exit code=10)

    Clifford, thanks for your time.
    I will go through my debug file to see whether that Callback appeared
    when I had managed to get surfing from it. I will tell you.

  19. Re: ppp daemon has died (exit code=10)

    Thanks for your time.

    > Your peer starts asking for Microsoft's proprietary callback
    > mechanism, even though it never negotiated the use of that during LCP.
    > The peer is obviously quite broken. I don't think there's much you
    > can do about this from your end.
    >

    Maybe that Callback line isn't important and that it is not
    responsible for terminating the negotiation!! Maybe we should look
    elsewhere?

    > Most likely, this ISP has a large number of access servers, with some
    > sort of call-distribution mechanism in front of them. On the days
    > when you dial in and hit one of the "good" ones, all is well. When
    > you hit a "bad" one, it doesn't work.
    >


    but why would it be working fine from windows then?

    > Given the unlikelihood of being able to interest anyone at the ISP in
    > fixing the problem, my advice would be to find an ISP that doesn't use
    > broken equipment.


    Oh yes, I think so...Before that I am going to configure kppp alone
    without going through wvdial. Just to check whether they are good. If
    it is still wrong, I will change.

  20. Re: ppp daemon has died (exit code=10)

    lap1974_sen@yahoo.co.uk (lolo) writes:
    > > Your peer starts asking for Microsoft's proprietary callback
    > > mechanism, even though it never negotiated the use of that during LCP.
    > > The peer is obviously quite broken. I don't think there's much you
    > > can do about this from your end.
    > >

    > Maybe that Callback line isn't important and that it is not
    > responsible for terminating the negotiation!! Maybe we should look
    > elsewhere?


    In the failure cases, the only thing the peer tries to negotiate is MS
    Callback (CBCP), and it eventually terminates the connection after
    you've (rightly) refused that bogus attempt a number of times. I'd
    call that a very strong case to say that the peer is just plain
    confused.

    I don't know what else to say about it. Horrid implementations are
    all too common, and there's really not much that can be done about the
    situation.

    > > Most likely, this ISP has a large number of access servers, with some
    > > sort of call-distribution mechanism in front of them. On the days
    > > when you dial in and hit one of the "good" ones, all is well. When
    > > you hit a "bad" one, it doesn't work.
    > >

    >
    > but why would it be working fine from windows then?


    You're free to draw your own conclusions ...

    > > Given the unlikelihood of being able to interest anyone at the ISP in
    > > fixing the problem, my advice would be to find an ISP that doesn't use
    > > broken equipment.

    >
    > Oh yes, I think so...Before that I am going to configure kppp alone
    > without going through wvdial. Just to check whether they are good. If
    > it is still wrong, I will change.


    Both of those things (kppp, wvdial) are just wrappers that take care
    of dialing the modem and the like. They have nothing to do with the
    way in which pppd negotiates with the peer.

    Those are just the deck chairs on the sinking ship. ;-}

    --
    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

+ Reply to Thread