Hide Forgot
Description of problem: Radtest script is not working with eap-md5 option. This is becasue radeapclient binary is used for eap-md5 and this binary doesn't support -4 option (for IPv4) which is passed to the binary. Ugly workaround I have used: # Set the address family case "$family" in IPv4) [ "$radclient" = "$radeapclient" ] || OPTIONS="$OPTIONS -4" NAS_ADDR_ATTR="NAS-IP-Address" ;; IPv6) OPTIONS="$OPTIONS -6" NAS_ADDR_ATTR="NAS-IPv6-Address" ;; *) echo "ERROR: unknown address family ($family)" >&2 usage esac Version-Release number of selected component (if applicable): freeradius-2.1.10-5.el6.x86_64 How reproducible: always Steps to Reproduce: 1. radtest -t eap-md5 .... Actual results: Usage message Expected results: authentization working Additional info:
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: radtest with eap-md5 fails because it invokes radeapclient passing an ip family argument. Consequence: radtest fails because radeapclient fails to recognize ip family. Fix: radeapclient in the current freeradius release now recognizes the ip family argument. Result: radtest now works with eap-md5.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0881.html