Hello Lisa -
On Thu, 14 Dec 2000, Lisa Goulet wrote:
> Hi Hugh,
>
> Thanks for your response. Here are more details and the config file:
>
> I have a proxy that executes the handler below. My master radius server does
> a check for port limits(Identifier LocalCheck). Following that, the call is
> handed off to a customer radius server(Identifier zonnetproxy). Since they
> are both "AuthBy RADIUS"s, I'm using the Synchronous flag. The log shows
> that the proxy does wait for reply from the first server before processing
> further requests.
>
> As this is causing the NAS to time out a lot, I would like to speed up the
> process a bit and have the proxy respond to other requests. Only, I'm not
> sure how. You've mentioned the ReplyHook but I'm not sure where to start.
>
I have to ask the question - why don't you do the AuthBy PORTLIMITCHECK
directly on this box, instead of proxying the request? It would be a *much*
simpler solution.
In any case, with two AuthBy RADIUS clauses, you will indeed have to use a
ReplyHook in the first one at least. This ReplyHook will check the reply status
of the request and if it is Access-Accept, then it will call the second AuthBy
RADIUS. You will also have to take care that the first AuthBy RADIUS clause
does not reply to the NAS, because it will send an Access-Accept if the AuthBy
PORTLIMITCHECK passes.
There is an example ReplyHook in the file "goodies/hooks.txt" in the Radiator
2.17.1 distribution (its the fifth example in the file).
BTW - if you would like me to write this for you, send a purchase order for a
couple of hours consulting time to Joanne ([EMAIL PROTECTED]).
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.
