(RADIATOR) postauthhook, Access-Reject problem.

[Hugh Irvine]

Hello Steve -

I suspect the problem is due to an internal change in the replyTo() 
call.

It should look like this (in recent versions of Radiator):

  # Reply to the Client that sent the request.
     $p->{Client}->replyTo($p);
     return;

BTW - for clarity, I would suggest using the correct PostAuthHook 
parameter passing, as it is quite confusing using a proxy ReplyHook as 
a template. You will find some example hooks in the file 
"goodies/hooks.txt" in the distribution.

regards

Hugh


On Tuesday, Dec 31, 2002, at 10:34 Australia/Melbourne, Steve Wilson 
wrote:

> The attached is our postauthhook file which we use to see if the user
> has exceeded their quota of usage, this is calculated on a rolling 30
> days. The problem we have is that when a user has used 150% or more we
> are trying to send a reject, and due to safety in the script we return 
> 1
> second session timeout. The user receives an "Access-Accept" with the
> reply message and attributes clearly showing that this user should not
> have connected. Where are we going wrong with the changing of the 
> return
> code ?
>
> -- 
> Steve Wilson <radiator at swsystem.yorks.com>
> <QOS-0808>

-- 
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.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.