They want to do these things.
>Sending LCP_CONFIGURE_REQUEST to port S29 of 29 bytes containing:
>01 02 00 1d 05 06 24 0d e9 a9 03 04 c0 23 11 04
>06 1c 12 02 13 09 03 00 c0 05 01 4a 51
>Sent to port S29: 31 bytes LCP Request-2
> Magic-Number = 0x240de9a9
> Authentication-Protocol = PAP
> MP-MRRU = 1564
> MP-Short-Seq-Num-Header
> MP-Endpoint-Disc = 0x0300c005014a51
We want these things.
>Sending LCP_CONFIGURE_REJECT to port S29 of 8 bytes containing:
>04 02 00 08 17 04 00 00
>Sent to port S29: 10 bytes LCP Reject-2
> Link-Disc-for-BACP = 0x0000
We say, sure, we can do what you want. EXCEPT BACP - we don't do that yet.
>Received LCP_CONFIGURE_REQUEST on port S29 of 31 bytes containing:
>01 02 00 23 01 04 05 dc 11 04 05 dc 13 13 01 6c
>4b 91 98 11 8a 66 ff cd bd 17 f3 7b e3 52 58 17
>04 00 00
>Fixed #bytes to match #found...
>Recvd from port S29: 37 bytes LCP Request-2
> Max-Recieve-Unit = 1500
> MP-MRRU = 1500
> MP-Endpoint-Disc = 0x016c4b9198118a66ffcdbd17f37be35258
> Link-Disc-for-BACP = 0x0000
Instead of answering our request, they ask for the same things again.
Including BACP, which we already NAK'd. You don't include enough here, but
if this continues like this, the problem is the other end is not playing
by the rules. When we NAK something, they are supposed to agree and stop
asking for it.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566