ication chap Called side: hostname NewYork username Chicago password 0 Secret2 interface BRI1/0 encapsulation ppp ppp authentication chap Now, the output from debug ppp authentication is a bit more verbose, as authentica- tion happens in both directions. I've included only the output for the called side here, for the sake of brevity: 20:01:59: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up 20:01:59: BR1/0:1 PPP: Using dialer call direction 20:01:59: BR1/0:1 PPP: Treating connection as a callin 20:02:00: %ISDN-6-LAYER2UP: Layer 2 for Interface BR1/0, TEI 66 changed to up 20:02:00: BR1/0:1 CHAP: 0 CHALLENGE id 2 len 28 from "NewYork" 20:02:00: BR1/0:1 CHAP: I CHALLENGE id 2 len 28 from "Chicago" 20:02:00: BR1/0:1 CHAP: Waiting for peer to authenticate first 20:02:00: BR1/0:1 CHAP: I RESPONSE id 2 len 28 from "Chicago" 20:02:00: BR1/0:1 CHAP: 0 SUCCESS id 2 len 4 20:02:00: BR1/0:1 CHAP: Processing saved Challenge, id 2 20:02:00: BR1/0:1 CHAP: 0 RESPONSE id 2 len 28 from "NewYork" 20:02:00: BR1/0:1 CHAP: I SUCCESS id 2 len 4 20:02:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1, changed state to up 20:02:05: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to 7801000 Chicago Basic (Non-AAA) Authentication Changing the sent hostname. Sometimes, the hostname of the calling router cannot be used for CHAP authentication. A common example is when you connect your router to an ISP. Figure 24-2 shows another simple two-router network: in this case, BobsRouter is connecting to a router named ISP. The service provider controlling the ISP router issues usernames and passwords to its clients. These usernames do not match the hostnames of the client's routers. Calling Called BRI 1/0 BRI 1/0 BobsRouter Figure 24-2. CHAP authentication with configured username Bob, the client who is using BobsRouter, has been given the username Bob-01 and the password SuperSecret1. On the calling side, I've configured the additional command ppp chap hostname. This has the effect of using the name Bob-01 instead of the rou