Re: (PM) AT&T WinModem

John Nowack (john@tremont.dpc.net)
Tue, 2 Jun 1998 22:41:16 -0500

>If the connection had truely succeeded to the point that there was no more
>lcp negotiation, then the sho modem should show CONNECTED. If it says
>CONNECTING, then its still negotiating. I would suggeste a dump of the
>0x51 into the decoder ring to see what the final disposition is of the lcp
>negotiation.
It does succeed to the point that it debug 0x51 the conenction successful
up to the point that it says Conenction succeeded.

Here is the dump (PAP munged, of course) (I missed the first couple packets):

Found Livingston dump format

Sending LCP_CONFIGURE_REJECT to port S3 of 7 bytes containing:
04 02 00 07 0d 03 06
Sent to port S3: 9 bytes LCP Reject-2
Callback = 0x06

Received LCP_CONFIGURE_REQUEST on port S3 of 16 bytes containing:
01 03 00 14 02 06 00 0a 00 00 05 06 00 01 ec c3
07 02 08 02
Fixed #bytes to match #found...
Recvd from port S3: 22 bytes LCP Request-3
Async-Control-Char-Map = 0x000a0000
Magic-Number = 0x0001ecc3
Protocol-Field-Comp
Addr-and-Ctl-Field-Comp

Sending LCP_CONFIGURE_ACK to port S3 of 20 bytes containing:
02 03 00 14 02 06 00 0a 00 00 05 06 00 01 ec c3
07 02 08 02
Sent to port S3: 22 bytes LCP Accept-3
Async-Control-Char-Map = 0x000a0000
Magic-Number = 0x0001ecc3
Protocol-Field-Comp
Addr-and-Ctl-Field-Comp
Skipping: S3: LCP Open

Received PAP_AUTH_REQ on port S3 of 22 bytes containing:
Fixed #bytes to match #found...
Recvd from port S3: 2 bytes PAP <badlen=0,4> unknown<0x0>
Skipping: xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx
Skipping: xx xx xx xx xx xx

Sending PAP_AUTH_ACK to port S3 of 20 bytes containing:
02 01 00 14 0f 4c 6f 67 69 6e 20 53 75 63 63 65
65 64 65 64
Sent to port S3: 22 bytes PAP Accept-1
<Login Succeeded>

Sending IPCP_CONFIGURE_REQUEST to port S3 of 16 bytes containing:
01 01 00 10 02 06 00 2d 0f 00 03 06 cd f2 5a 64
Sent to port S3: 18 bytes IPCP Request-1
IP Comp Proto = Van Jacobson 15 0
IP Address = 205.242.90.100
Skipping:

Received IPCP_CONFIGURE_REQUEST on port S3 of 36 bytes containing:
01 01 00 28 02 06 00 2d 0f 01 03 06 00 00 00 00
81 06 cd f2 5a 02 82 06 00 00 00 00 83 06 00 00
00 00 84 06 00 00 00 00
Fixed #bytes to match #found...
Recvd from port S3: 42 bytes IPCP Request-1
IP Comp Proto = Van Jacobson 15 1
IP Address = 0.0.0.0
Pri DNS = 205.242.90.2
Pri Netbios NS = 0.0.0.0
Sec DNS = 0.0.0.0
Secy Netbios NS = 0.0.0.0

Sending IPCP_CONFIGURE_REJECT to port S3 of 10 bytes containing:
04 01 00 0a 84 06 00 00 00 00
Sent to port S3: 12 bytes IPCP Reject-1
Secy Netbios NS = 0.0.0.0

Sending LCP_PROTOCOL_REJECT to port S3 of 21 bytes containing:
08 02 00 15 80 fd 01 01 00 0f 12 06 00 00 00 01
11 05 00 01 04
Sent to port S3: 23 bytes LCP Protocol-Reject-2 CCP 80 fd 01 01 00 0f

Received IPCP_CONFIGURE_ACK on port S3 of 12 bytes containing:
02 01 00 10 02 06 00 2d 0f 00 03 06 cd f2 5a 64
Fixed #bytes to match #found...
Recvd from port S3: 18 bytes IPCP Accept-1
IP Comp Proto = Van Jacobson 15 0
IP Address = 205.242.90.100
Skipping:

Received IPCP_CONFIGURE_REQUEST on port S3 of 30 bytes containing:
01 02 00 22 02 06 00 2d 0f 01 03 06 00 00 00 00
81 06 cd f2 5a 02 82 06 00 00 00 00 83 06 00 00
00 00
Fixed #bytes to match #found...
Recvd from port S3: 36 bytes IPCP Request-2
IP Comp Proto = Van Jacobson 15 1
IP Address = 0.0.0.0
Pri DNS = 205.242.90.2
Pri Netbios NS = 0.0.0.0
Sec DNS = 0.0.0.0

Sending IPCP_CONFIGURE_NAK to port S3 of 16 bytes containing:
03 02 00 10 82 06 00 00 00 00 83 06 cd f3 ad 44
Sent to port S3: 18 bytes IPCP Refuse-2
Pri Netbios NS = 0.0.0.0
Sec DNS = 205.243.173.68
Skipping:

Received IPCP_CONFIGURE_REQUEST on port S3 of 30 bytes containing:
01 03 00 22 02 06 00 2d 0f 01 03 06 00 00 00 00
81 06 cd f2 5a 02 82 06 00 00 00 00 83 06 cd f3
ad 44
Fixed #bytes to match #found...
Recvd from port S3: 36 bytes IPCP Request-3
IP Comp Proto = Van Jacobson 15 1
IP Address = 0.0.0.0
Pri DNS = 205.242.90.2
Pri Netbios NS = 0.0.0.0
Sec DNS = 205.243.173.68

Sending IPCP_CONFIGURE_REJECT to port S3 of 10 bytes containing:
04 03 00 0a 82 06 00 00 00 00
Sent to port S3: 12 bytes IPCP Reject-3
Pri Netbios NS = 0.0.0.0

Received IPCP_CONFIGURE_REQUEST on port S3 of 24 bytes containing:
01 04 00 1c 02 06 00 2d 0f 01 03 06 00 00 00 00
81 06 cd f2 5a 02 83 06 cd f3 ad 44
Fixed #bytes to match #found...
Recvd from port S3: 30 bytes IPCP Request-4
IP Comp Proto = Van Jacobson 15 1
IP Address = 0.0.0.0
Pri DNS = 205.242.90.2
Sec DNS = 205.243.173.68

Sending IPCP_CONFIGURE_NAK to port S3 of 10 bytes containing:
03 04 00 0a 03 06 cd f2 5a 70
Sent to port S3: 12 bytes IPCP Refuse-4
IP Address = 205.242.90.112

Received IPCP_CONFIGURE_REQUEST on port S3 of 24 bytes containing:
01 05 00 1c 02 06 00 2d 0f 01 03 06 cd f2 5a 70
81 06 cd f2 5a 02 83 06 cd f3 ad 44
Fixed #bytes to match #found...
Recvd from port S3: 30 bytes IPCP Request-5
IP Comp Proto = Van Jacobson 15 1
IP Address = 205.242.90.112
Pri DNS = 205.242.90.2
Sec DNS = 205.243.173.68

Sending IPCP_CONFIGURE_ACK to port S3 of 28 bytes containing:
02 05 00 1c 02 06 00 2d 0f 01 03 06 cd f2 5a 70
81 06 cd f2 5a 02 83 06 cd f3 ad 44
Sent to port S3: 30 bytes IPCP Accept-5
IP Comp Proto = Van Jacobson 15 1
IP Address = 205.242.90.112
Pri DNS = 205.242.90.2
Sec DNS = 205.243.173.68
Skipping: S3: IPCP Open
Skipping: LCP IPCP Open
Skipping: Connection Succeeded

At that point sho mx shows the modem "Active", and show sx shows the status
"Connecting." No more packets are sent, but the line will stay up until
the user drops it from his end (I had him sit for minutes like this).

John

--
John Nowack
john@dpc.net
DPConsultants, Inc.
Sys Admin -- dpc.net
309-925-2451
-
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/>