COA server times out

Mark Antony mark.antony.4 at
Wed May 12 22:37:43 CEST 2021

Alright, I got it.

I'm now using a Python based COA-Client to consume the COA messages from Freeradius.

I'm using this freeradius dictionary:

It seems to work. But there is a new error thrown by Freeradius, which I don't understand. Can you guide me here?

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?

Just trying to understand.

(24)     post-proxy {
(24) eap: No pre-existing handler found
(24)       [eap] = noop
(24)     }

More in context:

(24) Sent Disconnect-Request Id 19 from to length 28
(24)   User-Name = "mark"
(24) Sent Accounting-Response Id 236 from to length 0
(24) Finished request
(24) Cleaning up request packet ID 236 with timestamp +240
Waking up in 2.4 seconds.
(24) Clearing existing &reply: attributes
(24) Received Disconnect-ACK Id 19 from to length 20
(24) server default {
(24)   # Executing section post-proxy from file /etc/freeradius/3.0/sites-enabled/default
(24)     post-proxy {
(24) eap: No pre-existing handler found
(24)       [eap] = noop
(24)     } # post-proxy = noop
(24) }


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, 11 May 2021 12:38, Alan DeKok <aland at> wrote:

> On May 11, 2021, at 3:58 AM, Mark Antony via Freeradius-Users freeradius-users at wrote:
> > I have setup freeradius to disconnect the NAS when certain conditions are met.
> > However the COA server can't be reached or doesn't react, so the requests get duplicated and sent over and over again, until it times out.
> What do you think we can do here?
> What changes to the FreeRADIUS configuration will make the other system start replying to packets?
> Alan DeKok.

More information about the Freeradius-Users mailing list