(RADIATOR) Should Radiator handle RetryTimeout = 0 as a special case ?

[Hugh Irvine]

Salut Christophe -

Comment va la vie? Toujours bien j'espere.

As it happens, I wrote some custom code that implemented exactly this 
behaviour for one of our customers, and since then we have incorporated it 
into the base code. Here is the relevant section from the manual (6.27.25).
 
IgnoreAccountingResponse

  This optional flag causes AuthBy RADIUS to ignore replies to accounting 
requests, instead of forwarding them back to the originating host. This can 
be used in conjunction with the AccountingHandled flag in a Handler or Realm 
(see Section 6.15.10 ) to ensure that every proxied accounting request is 
replied to immediately, and the eventual reply from the remote Radius server 
is dropped.


This is supported in the latest version of Radiator - 2.18.1.

OK?

A+

Hugues


On Tuesday 15 May 2001 01:43, Christophe Wolfhugel wrote:
> The idea behind the title, is to be able to blindly forward and
> forget a packet to a third host, typically for non reliable
> recording.
>
> Typically this would just concern accounting packets :
>
> 	<AuthBy RADIUS>
> 		Host	my-unreliable-session-db
> 		IgnoreAuthentication
> 		IgnoreAccountingResponse
> 		RetryTimeout 0
> 	...
>
> RetryTimeout 0 would then mean a special handling in sendHost :
>
>   - do not update pendingRequests;
>   - do not call add_timeout.
>
> Does this make sense ?

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