(RADIATOR) Radiator Error Logging

[Hugh Irvine]

Hello Harrison -

The only way I can think of to do this is to write a NoReplyHook and 
have it log whatever message you require.

There are some example hooks in the file "goodies/hooks.txt".

regards

Hugh



On Thursday, Jun 19, 2003, at 13:04 Australia/Melbourne, Harrison Ng 
wrote:

> Dear Sir,
>
> Our radiator generates following messages:
> INFO: AuthRADIUS: No reply after 0 retransmissions to 
> 123.123.123.123:1813 for void  (54)
>
> Since our customer doesn't need to enter his username, remote access 
> server sends out 'void' for default.
> Can we customize the message so that it includes Calling-Station-Id 
> attribute?
> We need to identify which record doesn't arrive remote accounting 
> server.
>
> The new message will look like this:
> INFO: AuthRADIUS: No reply after 0 retransmissions to 
> 123.123.123.123:1813 for void (85291234567) (54)
>
> **where (85291234567) represents Calling-Station-Id attribute
>
> Thanks for your help in advance!
>
> Regards,
> Harrison
>
> <InterScan_Disclaimer.txt>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1572 bytes
Desc: not available
URL: <http://www.open.com.au/pipermail/radiator/attachments/20030619/ae03969c/attachment.bin>