ISDN trace - bafflement

Dave Andersen (angio@aros.net)
Mon, 7 Oct 1996 20:16:52 -0600 (MDT)

I'm not entirely sure what parts of this LCP conversation translate to.
It's an ISDN customer using a Courier I-Modem trying to get a Sync PPP
connection. We can establish an async PPP connection without much
trouble.

Someone care to clue me in? (Promises of eternal gratitude may be
inserted here).

- Dave

Command> show sS22: Sending Request Connect - 64Kbps / Data
S22: Received Connect - B1
ppp_recv (S22): Bad PPP Address
Sending LCP_CONFIGURE_REQUEST to port S22 of 14 bytes containing:
01 01 00 0e 05 06 2f 4d 9c 83 03 04 c0 23
Received LCP_CONFIGURE_REQUEST on port S22 of 12 bytes containing:
01 01 00 10 11 04 05 f6 01 04 05 f6 08 02 07 02

Sending LCP_CONFIGURE_REQUEST to port S22 of 29 bytes containing:
01 02 00 1d 05 06 2f 4d 9c 83 03 04 c0 23 11 04
06 1c 12 02 13 09 03 00 c0 05 01 47 d6
Sending LCP_CONFIGURE_ACK to port S22 of 16 bytes containing:
02 01 00 10 11 04 05 f6 01 04 05 f6 08 02 07 02

Received LCP_CONFIGURE_ACK on port S22 of 10 bytes containing:
02 01 00 0e 05 06 2f 4d 9c 83 03 04 c0 23
Discarding PPP on port S22 - reply to old request
Received LCP_CONFIGURE_REJECT on port S22 of 2 bytes containing:
04 02 00 06 12 02
Sending LCP_CONFIGURE_REQUEST to port S22 of 27 bytes containing:
01 03 00 1b 05 06 2f 4d 9c 83 03 04 c0 23 11 04
06 1c 13 09 03 00 c0 05 01 47 d6
Received LCP_CONFIGURE_ACK on port S22 of 23 bytes containing:
02 03 00 1b 05 06 2f 4d 9c 83 03 04 c0 23 11 04
06 1c 13 09 03 00 c0 05 01 47 d6
S22: LCP Open
S22: Received Disconnect Normal Clearing
net: Bad wanted 59771, got 25
S22: Received Call Clear
S22: Session Terminated - Lost Carrier