FreeRadius Proxy Status-Server with require_message_authenticator = yes
I am having issues when proxy servers are marked as down and freeradius send Status-Server and the remote server returns an Access-Accept without a Message-Authenticator. Debug: Ignoring invalid packet - Insecure packet from host xxx.xxx.xxx.xxx: Packet does not contain required Message-Authenticator attribute. You may need to set "require_message_authenticator = no" in the configuration. Then my home-servers are never marked as up again due to this behavior that the Access-Accept response does not contain a Message-Authenticator. I find it confusing that in the RFC for Status-Server in the Access-Accept response the Message-Authenticator is optional. https://www.freeradius.org/rfc/rfc5997.html Ideally I want to have require_message_authenticator = yes for all other requests to the home-servers and ignore it for Status-Server. Anyone else have experienced this issue and resolved it without setting require_message_authenticator = no? Sincerely, Jakob
On Oct 27, 2026, at 7:13 AM, Jakob Mellberg via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am having issues when proxy servers are marked as down and freeradius send Status-Server and the remote server returns an Access-Accept without a Message-Authenticator.
The remote server should really be fixed.
Debug: Ignoring invalid packet - Insecure packet from host xxx.xxx.xxx.xxx: Packet does not contain required Message-Authenticator attribute. You may need to set "require_message_authenticator = no" in the configuration.
Exactly.
Then my home-servers are never marked as up again due to this behavior that the Access-Accept response does not contain a Message-Authenticator.
Because the home server is broken.
I find it confusing that in the RFC for Status-Server in the Access-Accept response the Message-Authenticator is optional. https://www.freeradius.org/rfc/rfc5997.html
Things have changed since then. The following document defines new behavior: https://datatracker.ietf.org/doc/html/draft-ietf-radext-deprecating-radius-1...
Ideally I want to have require_message_authenticator = yes for all other requests to the home-servers and ignore it for Status-Server.
That behavior violates the updated RADIUS specifications.
Anyone else have experienced this issue and resolved it without setting require_message_authenticator = no?
Either set request_message_authenticator=no, or fix the home server so that it complies with the updated specifications. The recommendation above for Status-Server has been public for over 2 years now. People should fix their systems. Alan DeKok.
Hi! Thank you for the response! That clears everything up. Sincerely, Jakob 2026-10-28 04:10 skrev "[NAMN]" <alan.dekok@inkbridge.io> följande: On Oct 27, 2026, at 7:13 AM, Jakob Mellberg via Freeradius-Users <freeradius-users@lists.freeradius.org<mailto:freeradius-users@lists.freeradius.org>> wrote:
I am having issues when proxy servers are marked as down and freeradius send Status-Server and the remote server returns an Access-Accept without a Message-Authenticator.
The remote server should really be fixed.
Debug: Ignoring invalid packet - Insecure packet from host xxx.xxx.xxx.xxx: Packet does not contain required Message-Authenticator attribute. You may need to set "require_message_authenticator = no" in the configuration.
Exactly.
Then my home-servers are never marked as up again due to this behavior that the Access-Accept response does not contain a Message-Authenticator.
Because the home server is broken.
I find it confusing that in the RFC for Status-Server in the Access-Accept response the Message-Authenticator is optional. https://www.freeradius.org/rfc/rfc5997.html
Things have changed since then. The following document defines new behavior: https://datatracker.ietf.org/doc/html/draft-ietf-radext-deprecating-radius-1...
Ideally I want to have require_message_authenticator = yes for all other requests to the home-servers and ignore it for Status-Server.
That behavior violates the updated RADIUS specifications.
Anyone else have experienced this issue and resolved it without setting require_message_authenticator = no?
Either set request_message_authenticator=no, or fix the home server so that it complies with the updated specifications. The recommendation above for Status-Server has been public for over 2 years now. People should fix their systems. Alan DeKok.
participants (2)
-
Alan DeKok -
Jakob Mellberg