Hi everybody,
I found the solution to my problem of defining a IP pool on Radiator for
Cisco AS5300. The following lines are necessary :
aaa new-model
aaa authentication ppp wap group radius
aaa authorization network default group radius
aaa accounting update newinfo
aaa accounting network wap start-stop group radius
interface Group-Async0
encapsulation ppp
async dynamic address
async mode interactive
ppp authentication chap pap wap
ppp accounting wap
Furthermore, the following user profile lines were necessary :
fluxus Password = "*****"
Service-Type = Framed-User,
Framed-Protocol = PPP
Thanks to Hugh for his help about that. Gildas.
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la
> part de Hugh Irvine
> Envoy� : lundi 4 septembre 2000 09:19
> � : Gildas PERROT; [EMAIL PROTECTED]
> Objet : Re: (RADIATOR) Radiator ip pool allocation and Cisco 5300 +
> other problems ?
>
>
>
> Salut Gildas -
>
> On Sat, 02 Sep 2000, Gildas PERROT wrote:
> > Hi everybody,
> >
> > I am trying to define the ip pool on Radiator instead of on the
> Cisco for
> > more flexibility. Even if Radiator is returning a
> Framed-IP-Adress in the
> > Access-Accept packet, the Cisco is not sending it in the Start
> Accounting
> > packet but is sending another IP address (defined in a local
> pool) in the
> > Alive Accounting packet ! Any idea about how to solve that problem ?
> >
>
> I think this is due to the Cisco configuration that is allocating from its
> local pool, instead of from the Framed-IP-Address.
>
> > Note : I could not find any information in mailing list
> archives that could
> > help me.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
