Re: (PM) What is: CCP_CONFIGURE_REQUEST ?

Thomas C Kinnen (tkinnen@livingston.com)
Sat, 10 Apr 1999 09:54:28 -0700

Paul Gregg wrote:
>

> Significantly ComOS seems to be erroring in ppp.c ? See trace below.
>

> debug 0x51
> shows:

Put this though the java PPP decoder, SMart Agent or the web based decoder
at:

http://www.livingston.com/tech/support/dring.html

Received IPCP_CONFIGURE_ACK on port S1 of 6 bytes containing:
02 01 00 0A 03 06 D4 6C 40 64
Packet Info: Code: 0x02, ID: 0x01, 10 bytes.
IP-Address [0x03], length: (6 bytes), [212.108.64.100]
**** S1: IPCP Open

And you'll see that it's trying to do STAC. Try turning off compress and
see what happens.

Sending CCP_CONFIGURE_REQUEST on port S1 of 5 bytes containing:
01 04 00 09 11 05 00 01 03
Packet Info: Code: 0x01, ID: 0x04, 9 bytes.
Compression type=Stac Electronics LZS [0x11] length: (5 bytes)
Padding Protocol [0x000103]

Sending CCP_CONFIGURE_REQUEST on port S1 of 5 bytes containing:
01 05 00 09 11 05 00 01 03
Packet Info: Code: 0x01, ID: 0x05, 9 bytes.
Compression type=Stac Electronics LZS [0x11] length: (5 bytes)
Padding Protocol [0x000103]

Sending CCP_CONFIGURE_REQUEST on port S1 of 5 bytes containing:
01 06 00 09 11 05 00 01 03
Packet Info: Code: 0x01, ID: 0x06, 9 bytes.
Compression type=Stac Electronics LZS [0x11] length: (5 bytes)
Padding Protocol [0x000103]

Sending CCP_CONFIGURE_REQUEST on port S1 of 5 bytes containing:
01 07 00 09 11 05 00 01 03
Packet Info: Code: 0x01, ID: 0x07, 9 bytes.
Compression type=Stac Electronics LZS [0x11] length: (5 bytes)
Padding Protocol [0x000103]

-- 
Thomas C Kinnen - <tkinnen@ra.lucent.com> <tkinnen@sobhrach.com>
[RADIUS Test Engineer] - LUCENT Technologies RABU
"All of the opinions stated above are my own and not my employer's,
unless they were given to me by my employer"
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>