Thanks Alan. I found I actually needed to put: server = home.example.com to make it work, which makes sense I think? I find that, if the home servers are down and the relay is re-tried, I see additional Proxy-State = 0x.... values added to the packet which then eventually gets sent once the servers come back up. Is there an easy way to avoid this? Regards, Adrian -----Original Message----- From: freeradius-users-bounces+adrian.p.smith=bt.com@lists.freeradius.org [mailto:freeradius-users-bounces+adrian.p.smith=bt.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: 14 November 2013 14:56 To: FreeRadius users mailing list Subject: Re: robust-proxy-accounting question adrian.p.smith@bt.com wrote:

Hopefully a simple one...

If I want to use the robust-proxy-accounting example for ALL accounting requests that hit my server, what additional configuration do I need to route everything to it?

Just tell the accounting listener to use it, instead of the default virtual server: listen { type = acct server = robust-proxy-accounting ... } You'll have to ensure the pre/post-proxy sections get used, too. Arran and I are planning changes for v4 which should clean this up. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

...

Thanks Alan.

I found I actually needed to put:

server = home.example.com

to make it work, which makes sense I think?

If that's what's in the file...

And you should probably change the names to make more sense for your environment.

Yes, thanks, have now done that.

...

I find that, if the home servers are down and the relay is re-tried, I see additional Proxy-State = 0x.... values added to the packet which then eventually gets sent once the servers >>come back up. Is there an easy way to avoid this?

Upgrade. IIRC, that's a bug in an old version of the software.

Yes, correct, an upgrade did the trick.

Alan DeKok.