Hi Mike,
I went ahead anyway and added the AddtoReply for all the 12 attributes that I
receive from the merit server, and yes, the merit server stopped complaining and I
can't seem to duplicate the problem since. Prior to the config changers, it was
complaing about simultaneous users even though I did not specific any max sessions.
We have to really wait till it gets real busy to verify that the problem is gone.
Meantime, it is looking good.
Thanks Mike.
Dennis
> > Apparently, the Merit server needs vital attributes like
> > the NAS port and ip address otherwise it seems to occasionally fail the
> > authehtication.
> Hmmm, Im not convinced thats the problem. I would not normally expect things
> like NAS-Port ,Called-Station-Id etc to be returned in reply packet. And in any
> case, if Merit insisted on those being in the reply (which I know it does not)
> then I would expect it to fail every time, not just sometimes.
>
> >
> > NOW for the question.. (Sorry I am so long winded), how I could get
> > radiator to return back all the attributes that the merit server sends
> > over? Would AddToReply be the solution and if so, could anyone suggest
> > an example?
> Yes thats possible with AddToReply, with something like:
>
> AddToReply NAS-Port=%{NAS-Port},\
> Called-Station-Id=%{Called-Station-Id}
>
> etc.
>
> But I seriously think that wont fix the problem.
>
> I am more inclined to think the problem lies upstream in their Merit server or
> in the network.
>
> You may need to work with your upstream provider to check their Merit server
> logs and see if you can get any clues from there.
>
> Hope that helps.
>
> Cheers.
>
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
