Problems with freeradius accounting proxy

Phil Pierotti phil.pierotti at
Mon Feb 15 22:00:00 CET 2010

Hi Alan,

The main reason my initial checking was with tcpdump was to identify what
the packets were doing.

ACCT request IN from LNS - check
ACCT request OUT to downstream RADIUS - no

So the problem is not due to the downstream RADIUS failing to respond at
all. (ie genuinely/obviously dead)

Overnight I upgraded to 2.1.8, and now the behavior has changed, slightly.

Freeradius is complaining in the logs, but now it looks like enough
back-n-forth is happening that my LNS doesn't lose its mind any more.

Freeradius is deciding that my accounting proxy destination 'looks like it
is dead'.

Tue Feb 16 07:45:32 2010 : Proxy: Marking home server {{radius-ip}}  port
1813 as zombie (it looks like it is dead).

I'm not entirely sure why, though. TCPDUMP shows a stream of accounting
requests being proxied to that server, and being received from that server,
while at the same time freeradius continues to log 'looks like it is dead'

Also, status check (via request) succeeds, naturally,  given that its not
the auth proxy that freeradius is complaining about.
(single downstream RADIUS configured as auth+acct)

Phil P

Tue Feb 16 07:46:31 2010 : Proxy: Received response to status check 68398
(563 in current sequence)

On Mon, Feb 15, 2010 at 6:23 PM, Alan DeKok <aland at>wrote:

> Phil Pierotti wrote:
> > TCPDUMP shows the accounting requests are still being received on the
> > freeradius box, but the outbound/proxied messages have just stopped.
> >
> > Any suggestions as to what might be wrong/where to look?
>   The logs from the server?
>  I don't understand why you're looking at tcpdump, and not the
> FreeRADIUS logs.
>  In 2.1.7, you can also use "raddebug" to get the debug logs from a
> running server.
>  Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Freeradius-Users mailing list