Re: PPP Call Back/Chap Authentication

From: emonk@xxxxxxx
Date: Tue May 29 2001 - 20:45:57 GMT-3


   
Dirar,

How about using pap authentication and on R3 do not add
any interesting traffic to your dialer-list? This way R3
can never call R2. Now R3 will call R2 back using the
callback server command. But it will not initiate a call
sequence. They only want R2 to be able to initiate a
call sequence. This is what they are getting at in the
question.
> >From: Dirar Hakeem <dirarhakeem@yahoo.com>
> >Reply-To: Dirar Hakeem <dirarhakeem@yahoo.com>
> >To: ccielab@groupstudy.com
> >Subject: PPP Call Back/Chap Authentication
> >Date: Tue, 29 May 2001 15:30:50 -0700 (PDT)
> >
> >This problem is from one of the Wichita University
> >labs (# 3 if someone has done before). The requirment
> >reads as follows:
> >
> >R3 should never call R2. R2 should call R3 with
> >authentication but not be challenged by R3. R3 must
> >then call R2 back with userid userY, where Y is the
> >rack number.
> >
> >I know about the "callin" keyword, but I'm a little
> >confused on what exactly the question means. I think
> >the first part about R3 never calling R2 is not
> >possible for call back, but I'm not sure but what they
> >mean when they say "with authentication but not be
> >challenged by R3." Is the answer to simply add
> >callin, or is this more involved??
> >
> >Any help is welcome.
> >
> >Thanks
> >



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:56 GMT-3