On Thu, Jan 31, 2008 at 03:22:41PM +0100, Alan DeKok <aland@deployingradius.com> wrote a message of 18 lines which said:
The purpose of "radclient" is to send *anything* in a RADIUS packet, even things that violate the RFC's. In this case, you will need to manually add a Message-Authenticator to the input attributes.
OK, many thanks, now it works: lilith:~ % echo "Message-Authenticator = 42" | radclient jezabel status toto Received response ID 131, code 2, length = 49 Reply-Message = "FreeRADIUS up 0 days, 00:02" Which RFC should I read, by the way? 2865 says very little about Server-Status. Otherwise, your explanation makes sense. But, in that case, the example in the man page of radclient is wrong: EXAMPLE A sample session that queries the remote server for Status-Server (not all servers support this, but FreeRADIUS has configurable support for it). $ echo "User-Name = fnord" | radclient 192.168.1.42 12 s3cr3t Sending request to server 192.168.1.42, port 1812. radrecv: Packet from host 192.168.1.42 code=2, id=140, length=54 Reply-Message = "FreeRADIUS up 21 days, 02:05"