Actually it is *requesting* the CHAP protocol and NACKing PAP....
>Dring: Decoder Ring for Livingston Product PPP traces
>-----------------------------------------------------
>
>Received LCP_CONFIGURE_REQUEST on port S45 of 27 bytes containing:
>01 01 00 1F 01 04 05 F2 03 04 C0 23 05 06 00 0F 0D EE 07
>02 08 02 13 09 03 00 40 F9 11 40 D1
> Packet Info: Code: 01, ID: 01, 31 bytes.
> Maximum-Receive-Unit [0x01], length: (4 bytes) 1522 bytes [0x05F2]
> Authentication-Protocol [0x03], length: (4 bytes), Password
>Authentication Protocol [0xC023]
> Magic-Number [0x05], length: (6 bytes), [0x000F0DEE]
> Protocol-Field-Compression [0x07], length: (2 bytes)
> Address-and-Control-Field-Compression [0x08], length: (2 bytes)
> Multilink-Endpoint-Discriminator [0x13], length: (9 bytes),
>[0x030040F91140D1]
> Class [0x03]: IEEE 802.1 MAC Address 00 40 F9 11 40 D1
>
>Sending LCP_CONFIGURE_NAK to port S45 of 9 bytes containing:
>03 01 00 09 03 05 C2 23 05
> Packet Info: Code: 03, ID: 01, 9 bytes.
> Authentication-Protocol [0x03], length: (5 bytes), Challenge
>Handshake Authentication Protocol [0xC22305]
>---
>jstorms@livingston.com
>Diplomacy: The art of saying good doggie
>while seaching for a big rock.
>
Kevin