New name to reflect new functionality (was RE: DHCP code in 2.0.4+)
aland at deployingradius.com
Thu Jun 11 10:09:18 CEST 2009
Martin Lorentz wrote:
> FreeRadius should always be called FreeRadius. It's almost a brand name,
> which is very well known, and has an excellent reputation.
> How could this be organized, in the source tree or elsewhere? A new
> server core maybe called Flex-"Something" without any knowledge of
> RADIUS, DHCP or the like? An "add-on" package called FreeRadius, another
> called FlexDHCP? Kind of confusing, there must be a better way.
I think the best way is to have a new project that contains additional
documentation on the web explaining how to configure the additional
protocols. We could also have a git tree based on FreeRADIUS, but with
the RADIUS parts stripped out, for example.
I've started some of that work in the git "master" branch. The
various "listen" handlers are now in plug-in modules. The server core
is gradually having all of the RADIUS portions removed. If I can figure
out how to move the RADIUS state machine into the modules, then the core
would be *completely* protocol agnostic.
In the long term, migrating the FreeRADIUS code base into something
more flexible is a good idea.
More information about the Freeradius-Users