Proxying accounting to create a 'tee'

[John Morrissey]

On Sun, Aug 16, 2009 at 10:11:02AM +0200, Alan DeKok wrote:
> volkov at ufamts.ru wrote:
> > If home server does not respond, FR does not respond too -> NAS repeats
> > request -> FR writes request data to SQL again.
> 
>   So... configure the server to respond.  See the file
> raddb/sites-available/decoupled-accounting

Is decoupled-accounting (writing all detail to disk and replaying it
serialized with a detail listener) the only way to configure FreeRADIUS to
respond to the NAS?

I'm adapting robust-proxy-accounting for our environment and can't figure
out how (or if it's possible) to get FreeRADIUS to respond to the
originating NAS when proxying fails and the detail is logged for later
proxying.

Rejecting request 0 due to lack of any response from home server 66.133.129.108 port 1813
  Found Post-Proxy-Type 
 server buffered-radacct-dpi-proxy-tee {
+- entering group Fail
        expand: /var/log/freeradius/radacct/detail.dpi-proxy-tee -> /var/log/freeradius/radacct/detail.dpi-proxy-tee
rlm_detail: /var/log/freeradius/radacct/detail.dpi-proxy-tee expands to /var/log/freeradius/radacct/detail.dpi-proxy-tee
        expand: %t -> Fri Aug 21 20:10:39 2009
rlm_detail: Freeradius-Proxied-To = 66.133.129.108
++[detail.dpi-proxy-tee] returns ok
 }
Finished request 0.
Cleaning up request 0 ID 24 with timestamp +2
Going to the next request
WARNING: Marking home server 66.133.129.108 port 1813 as zombie (it looks like it is dead).
Waking up in 0.8 seconds.

john
-- 
John Morrissey          _o            /\         ----  __o
jwm at horde.net        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__