I would just like to take this opportunity to thank RedHat for their wonderfully consistent naming of packages. I just did not *think*, being so used to RedHat version numbers being way out of sync with reality, thanks to their backport policy. (Departs to *fix* things - with prejudice.) Thanks for pointing out my stupidity to me. -----Original Message----- From: freeradius-users-bounces+rmasters=bunnings.com.au@lists.freeradius.org [mailto:freeradius-users-bounces+rmasters=bunnings.com.au@lists.freeradi us.org] On Behalf Of John Dennis Sent: Wednesday, 24 November 2010 8:38 PM To: FreeRadius users mailing list Cc: Alexander Clouter Subject: Re: eap-gtc error in authentication On 11/24/2010 03:51 AM, Alexander Clouter wrote:
Hi,
Robert Masters<RMasters@bunnings.com.au> wrote:
We've been working on using Freeradius on RHEL5.4 to link a Motorola RFS6000 with Oracle OID.
We've had a number of hiccoughs along the way, and solved most of
them -
mainly thanks to the archives of this list.
We are now getting the following error: "rlm_eap_gtc: ERROR: Clear-test User-Password is required for authentication."
"Bad UNIX sysadmin *BAD*"
My git log tells me you are running a version of FreeRADIUS from *before* Aug 15 2006. Maybe I am the first to tell you, but it is 2010, and nearly 2011 :)
The 2.x version of FreeRADIUS on RHEL 5 is available under the package name freeradius2. This is documented in the RHEL release notes and the Red Hat FreeRADIUS FAQ http://wiki.freeradius.org/Red_Hat_FAQ -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ************************************************************************ Bunnings Legal Disclaimer: 1) This email is confidential and may contain legally privileged information. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this email in error, please notify us immediately by return email and delete the document. 2) All emails sent to and sent from Bunnings Group Limited. are scanned for content. Any material deemed to contain inappropriate subject matter will be reported to the email administrator of all parties concerned. ************************************************************************