22: Sending Request Connect - 64Kbps / Data
S22: Received Connect - B1
Received LCP_CONFIGURE_REQUEST on port S22 of 11 bytes containing:
01 1c 00 0f 03 05 c2 23 05 05 06 0f 1c b2 1f
Sending LCP_CONFIGURE_ACK to port S22 of 15 bytes containing:
02 1c 00 0f 03 05 c2 23 05 05 06 0f 1c b2 1f
Sending LCP_CONFIGURE_REQUEST to port S22 of 14 bytes containing:
01 01 00 0e 05 06 4e 9a 75 66 03 04 c0 23
Received LCP_CONFIGURE_ACK on port S22 of 10 bytes containing:
02 01 00 0e 05 06 4e 9a 75 66 03 04 c0 23
S22: LCP Open
Received CHAP_CONF_CHALLENGE on port S22 of 16 bytes containing:
01 01 00 10 04 0f 1c b3 a4 64 6f 77 61 2d 67 77
S22: Couldn't find CHAP user xxxx-gw
Received LCP_ECHO_REQUEST on port S22 of 8 bytes containing:
09 01 00 0c 0f 1c b2 1f a4 64 6f 77
Sending LCP_ECHO_REPLY to port S22 of 12 bytes containing:
0a 01 00 0c 4e 9a 75 66 a4 64 6f 77
Received CHAP_CONF_CHALLENGE on port S22 of 16 bytes containing:
01 02 00 10 04 0f 1c db 09 64 6f 77 61 2d 67 77
S22: Couldn't find CHAP user xxxx-gw
Received LCP_ECHO_REQUEST on port S22 of 8 bytes containing:
09 02 00 0c 0f 1c b2 1f a4 64 6f 77
Sending LCP_ECHO_REPLY to port S22 of 12 bytes containing:
0a 02 00 0c 4e 9a 75 66 a4 64 6f 77
The cisco is supposed to be using chap to connect to the PM,
but it looks like the bi-directional parts may not be working right.
The name xxxx-gw is an existing name in our raddb...shouldn't it be?
Thanks again,
Laughing in the Machine, www.ibs-us.net/~ben 45.5183754N/-122.6750031W
--Ben Kirkpatrick IBS 503.227.7010 fax 503.227.5778 page 503.229.3199
I hate my parents for not naming me Sallie Mae