Spot on Arran!

Copied the dictionaries from the source tree into /usr/local/share/freeradius ( which previously contained FR2.x files) and away it went. 

Magic!
many thanks … now to get radsec working
A
On 15 Nov 2013, at 15:28, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:


On 15 Nov 2013, at 14:48, Alan DeKok <aland@deployingradius.com> wrote:

Alex Sharaz wrote:
Well I thought I’d got FR3 working on OS X but seem to have an issue with 

Error: /usr/local/etc/freeradius/mods-enabled/eap[17]: Unknown EAP
method <pick a module>

 Well, that's broken.  However, I do all my development on Mac OSX, and
Arran does his on Lion.  So it *does* work.

Arran does his on OSX 10.9 Mavericks on a shiny new Mid 2012 MBP,
but anyway, it shouldn't really matter...


Still running OSX lion at home on my dual quad core Mac Pro early 2008 ( or possibly 2007) coz without playing around can’t seem to upgrade to maverick.


If I go into mods-enabled/eap and comment out md5 then The message
apears for the next method defined and so on. Looking in /usr/local/lib/
however I can see,

 I suspect there's another issue.  What does the *rest* of the debug
output say?

Well that message is not related to dlopen or any library loading, it seems
like maybe it hasn't picked up the dictionaries, or is using an old version
of them... Check your freeradius.internal file for EAP-Type and that it has
an enum value for tls.

Here's the relevant code:

method = eap_name2type(name);
if (method == PW_EAP_INVALID) {
cf_log_err_cs(cs, "Unknown EAP method %s", name);
return -1;
}

eap_type_t eap_name2type(char const *name)
{
DICT_VALUE *dv;
dv = dict_valbyname(PW_EAP_TYPE, 0, name);
if (dv) {
return dv->value;
}
return PW_EAP_INVALID;
}

We know name is correct because it's printed in the debug message, so it
suggests that the dictionaries aren't being read in.

-Arran

Arran Cudbard-Bell <a.cudbardb@freeradius.org>
FreeRADIUS Development Team

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html