On 18 Jun 2014, at 10:29, Chaigneau, Nicolas <nicolas.chaigneau@capgemini.com> wrote:
Since the following commit:
https://github.com/FreeRADIUS/freeradius-server/commit/ae041317eaebb49584fc6...
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 127.0.0.1 status testing123 Sending Status-Server Id 254 from 0.0.0.0:47287 to 127.0.0.1:1812 Message-Authenticator = 0x00 Received Access-Accept Id 254 from 127.0.0.1:1812 to 127.0.0.1:47287 length 20 radclient will now figure out request types from expected response types too. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2