From: Martin, Chris (chris@xxxxxxxxxxxx)
Date: Wed May 30 2001 - 17:26:40 GMT-3
Why do so many people get this wrong??? Please see me post with example
configs
----- Original Message -----
From: "louie kouncar" <lkouncar@UU.NET>
To: "'Daniel C. Young'" <danyoung99@mediaone.net>; "'Groupstudy (E-mail)'"
<ccielab@groupstudy.com>
Sent: Wednesday, May 30, 2001 1:00 PM
Subject: RE: ppp authentication w/ dialer profiles
> Daniel,
>
> When using dialer interface the PPP Authentication PAP/ CHAP goes on the
BRI
> (Physical) interface and not the Dialer (logical) interface...
>
> Thanks
>
> Louie J. Kouncar
> TCO3 Senior Data Center Engineer
> UUNET
> W-703-343-6645
> C-703-304-2460
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Daniel C. Young
> Sent: Wednesday, May 30, 2001 3:23 PM
> To: Groupstudy (E-mail)
> Subject: ppp authentication w/ dialer profiles
>
>
> Group,
>
> Just need a clarification: when configuring isdn with dialer profiles,
where
> do the ppp parameters need to go to (physical interface or dialer
> interface)? --specifically, the 'ppp authentication' command.
>
> The reason we are asking is that we excluded 'ppp authentication' from the
> physical interface but applied it to the dialer interface, and 'debug ppp
> authentication' showed no output for authentication.
>
>
>
>
> In case you want to include this information...This is with 'ppp auth' on
> the dialer interface (no authentication debug message). See bellow:
>
> 15:16:29: BR0 DDR: rotor dialout [priority]
> 15:16:29: BR0 DDR: Dialing cause ip (s=172.16.120.1, d=172.16.120.2)
> 15:16:29: BR0 DDR: Attempting to dial 384020
> 15:16:29: ISDN BR0: TX -> SETUP pd = 8 callref = 0x16
> 15:16:29: Bearer Capability i = 0x8890
> 15:16:29: Channel ID i = 0x83
> 15:16:29: Called Party Number i = 0x80, '384020'
> 15:16:29: ISDN BR0: RX <- CALL_PROC pd = 8 callref = 0x96
> 15:16:29: Channel ID i = 0x89
> 15:16:29: Signal i = 0x05 - Confirm tone on
> 15:16:29: ISDN BR0: RX <- ALERTING pd = 8 callref = 0x96
> 15:16:29: Signal i = 0x01 - Ring back tone on
> 15:16:29: ISDN BR0: RX <- CONNECT pd = 8 callref = 0x96
> 15:16:29: Signal i = 0x3F - Tones off
> 15:16:29: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
> 15:16:30: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
> 15:16:30: BR0:1 PPP: Treating connection as a callout
> 15:16:30: ISDN BR0: TX -> CONNECT_ACK pd = 8 callref = 0x16
> 15:16:30: BR0:1 DDR: dialer protocol up
> 15:16:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed
> state to up
> 15:16:36: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 384020
> 384020
>
> r1#s deb
> Dial on demand:
> Dial on demand events debugging is on
> PPP:
> PPP authentication debugging is on
> ISDN:
> ISDN Q931 packets debugging is on
>
> Yet, the call was placed, and the line still went up. Once we placed it on
> the physical interface, the handshake occured properly as it should.
> Puzzling...truly puzzling.
>
> Now, on Cisco's web site for PPP Callback Over ISDN:
> http://www.cisco.com/warp/public/793/access_dial/isdn-ppp-callback.html
>
> You will notice that one router is configured with legacy ddr and the
other
> with dialer profiles. The router with the dialer profiles, maui-nas-04,
has
> the 'ppp authentication' command on its dialer interface -- not the
physical
> interface!
>
> Later, we tested various combinations of 'ppp authenticaion' on bri0 and
> dialer0 and found the following:
> br0 on r1, d0 on r2 --> OK
> br0 on r1, br0 on r2 --> OK
> d0 on r1, d0 on r2 --> Call connect, but no authenticaion (see above)
> br0 & d0 on r1, br0 on r2 --> OK
> br0 & d0 on r1, br0 & d0 on r2 --> NO GO!
>
> Our theory is that 'encapsulation ppp' needs to go on at least one
physical,
> but where are all othe ther ppp parameters supposed to go?
>
> Can anyone verify and explain this?
>
> Regards,
> Daniel & Raymond
> **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:57 GMT-3