Re: authentication retry - PPP

This is a discussion on Re: authentication retry - PPP ; Darren Simons wrote: > PPP: got packet on i/f:5 protocol:0xc021 > PPP: incoming packet contents: (length = 32) > FF 03 C0 21 01 03 00 1C 01 04 05 DC 02 06 00 0A ...!............ > 00 00 03 ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: authentication retry

  1. Re: authentication retry

    Darren Simons wrote:

    > PPP: got packet on i/f:5 protocol:0xc021
    > PPP: incoming packet contents: (length = 32)
    > FF 03 C0 21 01 03 00 1C 01 04 05 DC 02 06 00 0A ...!............
    > 00 00 03 04 C0 23 05 06 E0 15 E2 7C 07 02 08 02 .....#.....|....


    The peer requests an ACCM of a0000 (02 06 00 0A 00 00 above).

    > PPP: got LCP packet code=0x01 id=3 i/f 5
    > PPP: link i/f 5 is down
    > PPPLINK: bringing up serial PPP interface 5
    > PPPLINK: baud rate 38400: setting divisor to 14
    > PPPLINK: Opened PPP serial on iface 5 at 38400 baud
    > PPP: sending LCP config i/f 5
    > PPPLINK: send CTL (sans CRC) packet contents: (length = 28)
    > FF 03 C0 21 01 01 00 18 01 04 05 DC 02 06 00 00 ...!............
    > 00 00 05 06 F0 5B 06 10 07 02 08 02 .....[......


    You request an ACCM of 0 (02 06 00 00 00 00 above).

    > PPP: LCP config request i/f 5
    > PPP: sending LCP ACK i/f 5
    > PPPLINK: send CTL (sans CRC) packet contents: (length = 32)
    > FF 03 C0 21 02 03 00 1C 01 04 05 DC 02 06 00 0A ...!............
    > 00 00 03 04 C0 23 05 06 E0 15 E2 7C 07 02 08 02 .....#.....|....


    You ACK the peer's request.

    > PPP: got packet on i/f:5 protocol:0xc021
    > PPP: incoming packet contents: (length = 28)
    > FF 03 C0 21 02 01 00 18 01 04 05 DC 02 06 00 00 ...!............
    > 00 00 05 06 F0 5B 06 10 07 02 08 02 .....[......
    > PPP: got LCP packet code=0x02 id=1 i/f 5
    > PPP: received LCP ACK i/f 5. local_acked = 1


    The peer ACKs your request.

    > PPP: sending PAP auth i/f 5


    >>>>>>>>>>>>>>>>> pap packet should be here <<<<<<<<<<<<<<<<<<<<


    Was it *not* there, or did you just remove it because it contained
    your name and password?

    > PPP: got packet on i/f:5 protocol:0xc023
    > PPP: incoming packet contents: (length = 7)
    > C0 23 03 00 00 05 00 .#.....
    > PPP: got PAP packet code=0x03 id=0 i/f 5
    > PPP: received PAP NAK, authentication failed


    But the peer NAKs PAP.

    You would be surprised how often a PPP implementation is broken with
    respect to ACCM. I'd suggest imitating the peer and request an ACCM
    of a0000. Authentication failure often occurs when the peer ACCM is
    broken.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* For every credibility gap, there is a gullibility fill.
    -- R. Clopton */

  2. Re: authentication retry


    "Clifford Kite" wrote in message
    news4fclb.vn1.ln@corncob.inetport.com...
    > Darren Simons wrote:
    >
    > > PPP: got packet on i/f:5 protocol:0xc021
    > > PPP: incoming packet contents: (length = 32)
    > > FF 03 C0 21 01 03 00 1C 01 04 05 DC 02 06 00 0A ...!............
    > > 00 00 03 04 C0 23 05 06 E0 15 E2 7C 07 02 08 02 .....#.....|....

    >
    > The peer requests an ACCM of a0000 (02 06 00 0A 00 00 above).
    >
    > > PPP: got LCP packet code=0x01 id=3 i/f 5
    > > PPP: link i/f 5 is down
    > > PPPLINK: bringing up serial PPP interface 5
    > > PPPLINK: baud rate 38400: setting divisor to 14
    > > PPPLINK: Opened PPP serial on iface 5 at 38400 baud
    > > PPP: sending LCP config i/f 5
    > > PPPLINK: send CTL (sans CRC) packet contents: (length = 28)
    > > FF 03 C0 21 01 01 00 18 01 04 05 DC 02 06 00 00 ...!............
    > > 00 00 05 06 F0 5B 06 10 07 02 08 02 .....[......

    >
    > You request an ACCM of 0 (02 06 00 00 00 00 above).
    >
    > > PPP: LCP config request i/f 5
    > > PPP: sending LCP ACK i/f 5
    > > PPPLINK: send CTL (sans CRC) packet contents: (length = 32)
    > > FF 03 C0 21 02 03 00 1C 01 04 05 DC 02 06 00 0A ...!............
    > > 00 00 03 04 C0 23 05 06 E0 15 E2 7C 07 02 08 02 .....#.....|....

    >
    > You ACK the peer's request.
    >
    > > PPP: got packet on i/f:5 protocol:0xc021
    > > PPP: incoming packet contents: (length = 28)
    > > FF 03 C0 21 02 01 00 18 01 04 05 DC 02 06 00 00 ...!............
    > > 00 00 05 06 F0 5B 06 10 07 02 08 02 .....[......
    > > PPP: got LCP packet code=0x02 id=1 i/f 5
    > > PPP: received LCP ACK i/f 5. local_acked = 1

    >
    > The peer ACKs your request.
    >
    > > PPP: sending PAP auth i/f 5

    >
    > >>>>>>>>>>>>>>>>> pap packet should be here <<<<<<<<<<<<<<<<<<<<

    >
    > Was it *not* there, or did you just remove it because it contained
    > your name and password?


    removed as it displayed name password, i will try the broken ACCM
    thoughts.

    thanks
    Darren

    >
    > > PPP: got packet on i/f:5 protocol:0xc023
    > > PPP: incoming packet contents: (length = 7)
    > > C0 23 03 00 00 05 00 .#.....
    > > PPP: got PAP packet code=0x03 id=0 i/f 5
    > > PPP: received PAP NAK, authentication failed

    >
    > But the peer NAKs PAP.
    >
    > You would be surprised how often a PPP implementation is broken with
    > respect to ACCM. I'd suggest imitating the peer and request an ACCM
    > of a0000. Authentication failure often occurs when the peer ACCM is
    > broken.
    >
    > --
    > Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    > PPP-Q&A links, downloads: http://ckite.no-ip.net/
    > /* For every credibility gap, there is a gullibility fill.
    > -- R. Clopton */




+ Reply to Thread