couldn't reconnect to the home server

[Alan DeKok]

On Sep 23, 2019, at 7:34 PM, Prem Khanal <prem.khanal at n4l.co.nz> wrote:
> 
> I have configured freeradius 3.0.19 as proxy server which forwards radius
> accounting packets to specific home servers based on NAS IP. The problem I
> am having is once the connectivity to the home server goes down, the radius
> proxy can not reestablish the connection to the home server.

  See the documentation in proxy.conf.

> If I delete detail and detail.work files and restart the freeradius service
> everything starts working well. I was wondering if I am missing something
> in configuration that is causing this problem.

  You've configured the server to do status checks:

> No response to status check 38206 ID 139 for home server xx.xx.xx.xx port
> 1813
> Waking up in 1.5 seconds.
> PING: Waiting 10 seconds for response to ping
> (38208) Sent Status-Server Id 97 from 0.0.0.0:49764 to xx.xx.xx.xx:1813
> length 0
> (38208)   Message-Authenticator := 0x00
> (38208)   NAS-Identifier := "Status Check 6430. Are you alive?"
> PING: Next status packet in 10 seconds
> Waking up in 9.5 seconds.
> PING: Waiting 10 seconds for response to ping
> (38209) Sent Status-Server Id 119 from 0.0.0.0:49764 to xx.xx.xx.xx:1813
> length 0
> (38209)   Message-Authenticator := 0x00
> (38209)   NAS-Identifier := "Status Check 6431. Are you alive?"
> PING: Next status packet in 10 seconds
> Waking up in 0.4 seconds.
> No response to status check 38208 ID 97 for home server 210.55.219.165 port
> 1813

  The home server isn't responding to status checks, so FreeRADIUS thinks it's still dead.

  Make the home server respond to status checks.  Or, configure Access-Request status checks.  Or, disable status checks completely.  This is all documented in proxy.conf.

  Alan DeKok.