From: John Kaberna (jkaberna@xxxxxxxxxxxx)
Date: Thu Feb 22 2001 - 19:17:26 GMT-3
Has the line stayed up the whole time? I'm guessing two things. 1. The
line has stayed up the whole time and is therefore already authenticated.
2. There is somehow an alternate route. Do a traceroute just to make sure
it is going over the ISDN line. I'm not sure about either of those though.
You should add the username and password back in to the hub router. It does
not need to be on the remote router since authentication is only one-way.
Anyone else?
John
----- Original Message -----
From: "BUI, TIN T (SBCSI)" <tb4565@sbc.com>
To: "'John Kaberna'" <jkaberna@netcginc.com>; <ccielab@groupstudy.com>
Sent: Thursday, February 22, 2001 2:04 PM
Subject: RE: ISDN Multilink
> Looks like the dialer load-threshold does work. However, something really
> strange is happenning. I took out "username user5 password cisco" and
> corresponding username on both routers so that there are no username
> statements on both routers. Interesting enough, I'm still able to ping
from
> R3 to R5. In other words, somehow it's authenticating even without
username
> statements in global configs for both routers. Something is really
strange.
> I turned on debug ppp auth and debug isdn q931 and debug isdn events and I
> cannot see what username is being sent. It's almost like it's not using
any
> type of authentication. Am I missing something?
>
> -----Original Message-----
> From: John Kaberna [mailto:jkaberna@netcginc.com]
> Sent: Wednesday, February 21, 2001 4:18 PM
> To: BUI, TIN T (SBCSI); ccielab@groupstudy.com
> Subject: Re: ISDN Multilink
>
>
> In order to get 2 channels you need to configure dialer load-threshold.
PPP
> multilink by itself is not enough. For the one-way authentication
question
> you do not need to configure a callback. The hub router receiving the
call
> (router with ppp chap refuse callin) should authenticate the incoming
call.
> But the spoke router placing the call shouldnt need to authenticate the
hub
> router. I am also wondering why you are using the same hostname on both
> routers as far as ppp chap is concerned. I'm not sure if that would make
a
> difference but its definitely not good practice and the proctor may think
> you don't know what your doing.
>
> PS I even remove the ppp chap user.... on all routers and also used
> incorrect names on dialer remote-name and R3 still can ping R5..
>
> ----- Original Message -----
> From: "BUI, TIN T (SBCSI)" <tb4565@sbc.com>
> To: <ccielab@groupstudy.com>
> Sent: Wednesday, February 21, 2001 3:36 PM
> Subject: ISDN Multilink
>
>
> > Hi, I have 2 questions with this ISDN configuration. Question 1, I'm
> having
> > problems with getting the 2nd B channel to come up with Multilink. R3
is
> > dialing R5 and only bri0:1 comes up. Am I doing something wrong?
> >
> > Second question regards ppp chap refuse callin, is this how I can get R3
> to
> > dial R5 and R5 will refuse authentication from R3 using Chap. In this
> > instance, I want R3 to authenticate not R5. This solution seems to
simple
> > because of only 1 statement. Right now, it does work with this
statement,
> > but I'm thinking that I need to do callback or something. Can someone
> > explain? thanks. Here's the configuration:
> >
> > On R3:--->
> >
> > interface BRI0
> > no ip address
> > no ip directed-broadcast
> > ip ospf interface-retry 0
> > dialer pool-member 1
> > isdn switch-type basic-ni
> > isdn spid1 0835866101
> > isdn spid2 0835866301
> > !
> > interface Dialer1
> > ip address 170.100.35.243 255.255.255.240
> > no ip directed-broadcast
> > encapsulation ppp
> > ip ospf interface-retry 0
> > dialer remote-name r5
> > dialer string 8358662
> > dialer string 8358664
> > dialer pool 1
> > dialer-group 1
> > ppp authentication chap
> > ppp chap hostname user5
> > ppp multilink
> >
> > On R5:--->
> >
> > interface BRI0
> > no ip address
> > no ip directed-broadcast
> > ip ospf interface-retry 0
> > dialer pool-member 1
> > isdn switch-type basic-ni
> > isdn spid1 0835866201
> > isdn spid2 0835866401
> > !
> > interface Dialer1
> > ip address 170.100.35.245 255.255.255.240
> > no ip directed-broadcast
> > encapsulation ppp
> > ip ospf interface-retry 0
> > dialer remote-name r3
> > dialer string 8358661
> > dialer string 8358663
> > dialer pool 1
> > ppp authentication chap
> > ppp chap hostname user5
> > ppp chap refuse callin
> > ppp multilink
> >
> > > > Tin T. Bui
> > > > Senior Network Manager
> > > > CCNP, CNE, MCP
> > > > Network Management Center
> > > > SBC Services Inc.
> > > > 7337 Trade Street, Rm 1110
> > > > San Diego, Ca 92121
> > > > Office #: 858-886-4644/858-886-4589
> > > > Pager #: 858-494-0482
> > > > Fax #: 858-549-4103
> > > > Email: tb4565@sbc.com
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:57 GMT-3