Kind words from overseas... :-)
We have an option ("-x") which when added to the command line of
either of the above programs (see the radcheck.8 and radpwtst.8
man pages in the distribution) breaks out the received a/v pairs
into printable ASCII (using fprint_attr_val() BTW) and is fairly
useful in tracking down problems. Also the server may be started
with one, two, three or four (currently) such -x options and it
leaves similar debugging output into a (compile time comfigurable)
radius.debug file. One may also send USR1 signals to a running
server to increase the debugging level. The USR2 signal stops
the debug trace. Two levels is sufficient to reveal a/v pairs
as the enter and exit the server...
Assuming the server's PID is 1234 (and you can send signals to it):
% kill -USR1 1234
% kill -USR1 1234
% tail -f ./raddb/radius.debug
^C
% kill -USR2 1234
should get you started...
Regards,
web...
-- William Bulley, N8NXN Senior Systems Research Programmer Merit Network Inc. Domain: web@merit.edu 4251 Plymouth Road MaBell: (313) 764-9993 Ann Arbor, Michigan 48105-2785 Fax: (313) 747-3185