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:44:56 CEST 2014

Ah sorry, I'm lagging a bit behind HEAD.


-----Message d'origine-----
De : freeradius-devel-bounces+nchaigne=capgemini.fr at lists.freeradius.org [mailto:freeradius-devel-bounces+nchaigne=capgemini.fr at lists.freeradius.org] De la part de Arran Cudbard-Bell
Envoyé : mercredi 18 juin 2014 11:38
À : FreeRadius developers mailing list
Objet : Re: radclient can no longer send a Status-Server on non standard port using stdin

On 18 Jun 2014, at 10:29, Chaigneau, Nicolas <nicolas.chaigneau at capgemini.com> wrote:

> Since the following commit:
> https://github.com/FreeRADIUS/freeradius-server/commit/ae041317eaebb49
> 584fc60383418da01a627c49e
> 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 ?

Yes I went back in time and fixed it yesterday.

echo "Message-Authenticator = 0x00" | radclient -x status testing123 Sending Status-Server Id 254 from to
	Message-Authenticator = 0x00
Received Access-Accept Id 254 from to length 20

radclient will now figure out request types from expected response types too.

Arran Cudbard-Bell <a.cudbardb at freeradius.org> FreeRADIUS Development Team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

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.

More information about the Freeradius-Devel mailing list