Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Jan 2014 19:43:14 -0600
From:      Dave Duchscher <daved@me.com>
To:        Darrel <levitch@iglou.com>
Cc:        Thomas Hoffmann <trh411@gmail.com>, FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   Re: freeradius3 error on freebsd10
Message-ID:  <56553BCF-B96F-4072-A77F-74010E56BEC0@me.com>
In-Reply-To: <alpine.GSO.2.00.1401221146510.22566@shell1>
References:  <alpine.GSO.2.00.1401221021290.3590@shell1> <CAB7-od=JrsU_LrF6xwzNxxJifFMPEA_YGD3ECU09tqDFJH4f=w@mail.gmail.com> <alpine.GSO.2.00.1401221146510.22566@shell1>

next in thread | previous in thread | raw e-mail | index | archive | help

On Jan 22, 2014, at 10:49 AM, Darrel <levitch@iglou.com> wrote:

> 
>>> 
>>> Perhaps this should be sent to the freeradius list.  I have not built
>>> freeradius3 anywhere else- so not sure.
>>> 
>>> "Errors reading dictionary:  dict_init: /usr/local/share/freeradius/
>>> dictionary.dhcp[208]:
>>> Type "tlv" can only be for "format=1,1".
>>> 
>>> I do not even want the dhcp dictionary.  It arrived with the others.
>>> 
>>> The only option I added to the build was "with postgresql support".
>>> 
>>> Anyone familiar with this?
>>> 
>>> Darrel
>> 
>> 
>> IIRC, that error means you are using a 2.x dictionary with a 3.x version.
>> You should not get that error with a clean 3.x installation. Are you
>> installing 3.x over 2.x? If so, I'd suggest wiping the 2.x version first,
>> than installing 3.x. For more in depth info I'd suggest the freeradius
>> lists.
>> 
>> - Tom
> 
> Totally new build.
> 
> /usr/ports/net/freeradius3
> 
> I just joined the freeradius users list.
> 
> Thank you,
> Darrel

I dug into this a little to see what is up and I think I have found the issue.  To manually fix your problem, you need to disable the DHCP dictionary by commenting out this line:

$INCLUDE dictionary.dhcp

in /usr/local/share/freeradius/dictionary and remove /usr/local/etc/raddb/mods-enabled/dhcp file.

What is going on is that freeradius 3 default setup is with DHCP enabled and its default configuration is setup that way.  The port by default, disables building with DHCP (currently fails to build properly with DHCP support) but does not fix up the default configuration.

--
DaveD




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56553BCF-B96F-4072-A77F-74010E56BEC0>