Technical data

Cisco AS5300 Configuration 2-33
Step 10—Testing Async PPP Connections
(j) See 21:35:03.978.
After LCP negotiates, authentication starts. Authentication must happen before any
network protocols, such as IP, are delivered. Both sides authenticate with the method
negotiated during LCP. The Cisco AS5300 is authenticating the test PC using
CHAP. The test PC is not authenticating the access server in this test case.
(k) See 21:35:03.982.
Outgoing challenge from hq-sanjose.
(l) See 21:35:04.162.
Incoming CHAP response from the test PC, which is shows the username
joe-admin.
(m) See 21:35:04.182.
An outgoing success is sent from the NAS—authentication is successful.
(n) See 21:35:04.186.
PPP is up. The Cisco AS5300 PPP link is now open and available to negotiate any
network protocols supported by both peers.
(o) See 21:35:04.314 through 21:35:04.322.
The test PC requests support for Microsoft Point-to-Point Compression (MPPC).
The Cisco AS5300 rejects this request. The access server’s integrated modems
already support hardware compression, and the Cisco IOS is not configured to
support software compression.
(p) See 21:35:07.274 through 21:35:07.478.
The primary and secondary DNS addresses are negotiated. At first, the test PC asks
for 0.0.0.0. addresses. The access server sends out a CONFNAK and supplies the
correct values. Values include an IP address from the pool, the primary DNS
address, and the backup DNS address.
(q) See 21:35:07.426.
The test PC sends an incoming request saying that the new values are accepted.
Whenever the access server sends out a CONFNAK that includes values, the test PC
still needs to come back and report acceptance of the new values.
(r) See 21:35:07.458 through 21:35:07.490.
An outgoing CONFACK is sent for IPCP. The state is open for IPCP. A route is
negotiated for the IPCP peer, which is 10.1.2.2.