I have setup FreeRadius to log all the commands entered from the procurve command line and it rocks except for on some of my 5400's it is sending the Calling-Station-Id wrong.
The Calling-Station-Id is this case should be the IP address of the device which has telneted / ssh'd into the switch. What is slightly more annoying is that the switch is definitely aware of the IP it should be sending as if I turn on "aaa accounting exec start-stop" to log the sessions of people on the switch it is showing the correct ip in my logs (below). A "show telnet" also shows the correct IP. Basically I want to get to the point where I can pointpoint what command was entered by who, without having to create a separate login for everyone who uses the switches.
Below I have attached a few logs from my freeradius server showing that the exec accounting is logging the ip correctly, but the command logging is not:
I believe now that this is a bug in the newer versions of ProCurve Firmware, definately from K.13.57 and maybe one or two versions before.
There also seems to be further issues with Radius since version K.13.63
Routing Switches now have trouble locating the radius server (which is on a different subnet) however L2 edge switches, sending their radius requests through the routing switches are still working.
