radclient can no longer send a Status-Server on non standard port using stdin

Chaigneau, Nicolas nicolas.chaigneau at capgemini.com
Wed Jun 18 11:29:00 CEST 2014

Since the following commit:


We can no longer use radclient to send a Status-Server request on a non standard RADIUS port without creating a "response filter" file.
That means we can't use stdin such as:

echo "<attributes>" | radclient <address>:<port> status <secret>

Or else we get:

(0) Can't determine expected response to Status-Server request, specify a well known RADIUS port, or a response filter with a Response-Packet-Type attribute

That's annoying... stdin is practical :/

Can you do something about this ?



This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-devel/attachments/20140618/0c801f96/attachment.html>

More information about the Freeradius-Devel mailing list