COA server times out

Mark Antony mark.antony.4 at
Thu May 13 23:16:37 CEST 2021

Thanks, I have located the dictionary that comes with Freeradius and switched to that one.

I got everything else working. I have one last question:

Do I also have to uncomment the following line in /etc/freeradius/3.0/clients.conf:

client localhost {
   #  A pointer to the "home_server_pool" OR a "home_server"
   #  section that contains the CoA configuration for this
   #  client.  For an example of a coa home server or pool,
   #  see raddb/sites-available/originate-coa
   coa_server = my-coa

Because even with this line commented out, my COA setup works as expected. What is the purpose of this pointer?


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, 12 May 2021 21:44, Alan DeKok <aland at> wrote:

> > On May 12, 2021, at 4:37 PM, Mark Antony via Freeradius-Users freeradius-users at wrote:
> > I'm now using a Python based COA-Client to consume the COA messages from Freeradius.
> OK.
> > I'm using this freeradius dictionary:
> Uh... why? FreeRADIUS does come with dictionaries. Why go to a 7 year-old third-party GitHub account, when you could get the, directly from FreeRADIUS?
> > It seems to work. But there is a new error thrown by Freeradius, which I don't understand. Can you guide me here?
> There's no error, because the log message doesn't say "error". It's just a warning message, You can ignore it.
> > Is it because I still haven't implemented the part where the NAS disconnects the user (need to code this), and because the user is not yet disconnected this error below is thrown?
> No.
> The server has no idea whether or not the NAS disconnected the user. The only thing that FreeRADIUS sees is a Disconnect-ACK.
> Alan DeKok.

More information about the Freeradius-Users mailing list