Hi, I am evaluating v3.0.7. When running as a daemon, every time when I saw the following "Failing proxied request" message in the radius.log, the radius daemon aborted immediately. Tue Mar 10 16:51:43 2015 : Proxy: Marking home server x.x.x.x port yyyy as zombie (it has not responded in 30.000000 seconds). When running in debug mode, freeradius process never exited. The "Failing proxied request" message was still occasionally seen in the debug output. But it then followed with the received status-check response message and continued (see last 3 lines): (365) No proxy response, giving up on request and marking it done Marking home server x.x.x.x port yyyy as zombie (it has not responded in 30.000000 seconds). PING: Waiting 4 seconds for response to ping PING: Next status packet in 20 seconds (365) ERROR: Failing proxied request for user "145094624@wlan.network.org", due to lack of any response from home server x.x.x.x port yyyy (365) Found Post-Proxy-Type Fail-Authentication (365) There was no response configured: rejecting request (365) Using Post-Auth-Type Reject (365) # Executing group from file /usr/local/etc/raddb/sites-enabled/WiFi (365) Post-Auth-Type REJECT { (365) attr_filter.access_reject: EXPAND %{User-Name} (365) attr_filter.access_reject: --> 1454094624@wlan.network.org (365) attr_filter.access_reject: Matched entry DEFAULT at line 16 (365) [attr_filter.access_reject] = updated (365) eap: Either EAP-request timed out OR EAP-response to an unknown EAP-request (365) eap: Failed to get handler, probably already removed, not inserting EAP-Failure (365) [eap] = noop (365) policy remove_reply_message_if_eap { (365) if (&reply:EAP-Message && &reply:Reply-Message) { (365) if (&reply:EAP-Message && &reply:Reply-Message) -> FALSE (365) else { (365) [noop] = noop (365) } # else = noop (365) } # policy remove_reply_message_if_eap = noop (365) } # Post-Auth-Type REJECT = updated (365) Sent Access-Reject Id 88 from z.z.z.z:aaaa to w.w.w.w:bbbb length 20 (365) Finished request (365) <done>: Cleaning up request packet ID 88 with timestamp +145 Waking up in 3.9 seconds. (449) Received response to status check 449 (1 in current sequence) (449) Marking home server x.x.x.x port yyyy alive Ready to process requests I guess it was due to a difference in timing when waiting for a status response from home servers. I tried different parameters in proxy.conf, but in vain. Can anyone suggest what parameters to adjust in proxy.conf? Or is it just a bug? Thanks in advance. Fu