Unexpected LCP config Nak - PPP

This is a discussion on Unexpected LCP config Nak - PPP ; Hi, When i try to create an internet connection in ppc2003(using connection manager api), i am getting the following LCP packets. ==> 7E FF 7D 23 C0 21 7D 21 7D 20 7D 20 7D 2E 7D 22 7D 26 ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Unexpected LCP config Nak

  1. Unexpected LCP config Nak

    Hi,


    When i try to create an internet connection in ppc2003(using
    connection manager api), i am getting the following LCP packets.

    ==> 7E FF 7D 23 C0 21 7D 21 7D 20 7D 20 7D 2E 7D 22 7D 26 7D 20 7D 20
    7D 20 7D 20 7D 27 7D 22 7D 28 7D 22 DD 31 7E

    <== config reject ....

    ==> config req ....

    <== 7E C0 21 7D 22 7D 21 7D 20 7D 2A 7D 22 7D 26 7D 20 7D 20 7D 20 7D
    20 4F E1 7E



    <== 7E C0 21 7D 21 7D 21 7D 20 7D 2E 7D 22 7D 26 7D 20 7D 20 7D 20 7D
    20 7D 21 7D 24 7D 26 40 88 BF 7E

    ==> 7E FF 7D 23 C0 21 7D 23 7D 21 7D 20 7D 28 7D 27 7D 22 7D 28 7D 22
    F6 D8 7E


    The config NAK sent from the pocket pc 2003 ppp (the last packet) is
    not the expected one. Can any one tell me why this happens and how can
    i solve this problem ?Whether it depends on some entries in the phone
    book?

    TIA,

    Gomas

  2. Re: Unexpected LCP config Nak

    gomas_vincy@yahoo.com (gomas) writes:
    > When i try to create an internet connection in ppc2003(using
    > connection manager api), i am getting the following LCP packets.
    >
    > ==> 7E FF 7D 23 C0 21 7D 21 7D 20 7D 20 7D 2E 7D 22 7D 26 7D 20 7D 20
    > 7D 20 7D 20 7D 27 7D 22 7D 28 7D 22 DD 31 7E


    That decodes as:

    FF 03 - Address/Control
    C0 21 - LCP
    01 - Configure-Request
    00 - ID 0
    00 0E - Length 14
    02 06 00 00 00 00
    - ACCM 0
    07 02 - PFC
    08 02 - ACFC
    DD 31 - FCS

    > <== config reject ....
    >
    > ==> config req ....
    >
    > <== 7E C0 21 7D 22 7D 21 7D 20 7D 2A 7D 22 7D 26 7D 20 7D 20 7D 20 7D
    > 20 4F E1 7E


    That looks mangled to me. The sender must use the RFC 1661 defaults
    until LCP has reached Opened state. It's omitted the Address and
    Control fields, and thus it's broken. Complain to the vendor.

    An attempted decode:

    C0 21 - LCP
    02 - Configure-Ack
    01 - ID 1 ???
    00 0A - Length 10
    02 06 00 00 00 00
    - ACCM 0
    4F E1

    I don't know what that's about; I didn't see a Configure-Request that
    corresponds to this message. Are you showing the *entire* log?

    > <== 7E C0 21 7D 21 7D 21 7D 20 7D 2E 7D 22 7D 26 7D 20 7D 20 7D 20 7D
    > 20 7D 21 7D 24 7D 26 40 88 BF 7E


    LCP Configure-Request ID 1, Length 14, ACCM 0, MRU 1600.

    I'm not sure what that's about. It seems unrelated to the above
    messages.

    > ==> 7E FF 7D 23 C0 21 7D 23 7D 21 7D 20 7D 28 7D 27 7D 22 7D 28 7D 22
    > F6 D8 7E


    LCP Configure-Nak, ID 1, Length 8, PFC, ACFC.

    > The config NAK sent from the pocket pc 2003 ppp (the last packet) is
    > not the expected one. Can any one tell me why this happens and how can
    > i solve this problem ?


    These are called "unsolicited Naks." The sender is requesting that
    the peer use Protocol Field Compression and Address and Control Field
    Compression (options 7 and 8 from RFC 1661). They're only a hint.

    If the peer doesn't comply, the sender has to either fall back on the
    defaults or (if it's a lousy implementation) give up and fail the
    connection.

    > Whether it depends on some entries in the phone
    > book?


    That sounds like an implementation-related question. I've never used
    the implementation you're using. You might want to try a group
    related to "pocket pc."

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