What is the current status and roadmap for FreeRadius?

[Jorge Pereira]

Joshua,

If you are looking for some capability to use something like Java. we
would like to encourage you to create the Java support. what do you
think? I could imagine that below points as a first-step.

1. Take a look first at the rlm_example
https://github.com/FreRADIUS/freeradius-server/tree/master/src/modules/rlm_example
2. Use some other bindings as an example, e.g:
https://github.com/FreeRADIUS/freeradius-server/tree/master/src/modules/rlm_python
https://github.com/FreeRADIUS/freeradius-server/tree/master/src/modules/rlm_lua
https://github.com/FreeRADIUS/freeradius-server/tree/master/src/modules/rlm_perl
3. Then, here https://docs.oracle.com/javase/7/docs/technotes/guides/jni/
you could find all JNI documentation.

After that, it will be possible to forward all REQUEST packets to a
Java Class/Jar as today is possible to do using Lua/Python/Perl/Ruby.
--
Jorge Pereira

On Fri, Mar 15, 2019 at 3:47 PM Joshua Marshall <j.marshall at arroyo.io> wrote:
>
> Thank you for the speedy reply.  We're implementing stuff with FreeRadius
> and are having to abuse it in a few unorthodox ways.  Config files with
> silent errors or misconfigurations, using what seems to be undocumentd
> interactions with LDAP to handle passwords securely -- challenges which
> feel like they're from a bygone era.
>
> Looking at the roadmap, and you've probably had to answer these before, why
> not switch the codebase to C++ which has wrapped up much of the threading
> and modularization work already and has a number of good libraries to
> handle networking?  Why not use Antlr4 to run your grammars and make start
> and runtime problems more apparent as well as providing a more robust
> parsing method?
>
> What we are really feeling over here is a lack of modern behavior and
> features.  Which isn't just one thing, but an enormous amount of work and
> polish.  That isn't a thing we could ever just ask for and get -- it iosn't
> that easy and we know that.  But to know what is OK to ask and what might
> be possible requires context.
>
> On Fri, Mar 15, 2019 at 2:18 PM Alan DeKok <aland at deployingradius.com>
> wrote:
>
> > On Mar 15, 2019, at 2:07 PM, Joshua Marshall <j.marshall at arroyo.io> wrote:
> > >
> > > I don't have a problem needing solving, but I would like context about
> > > FreeRadius.  What is happening with the v4 work?
> >
> >   Lots.  There's a lot to do, but it's making good progress.
> >
> > https://wiki.freeradius.org/design/version4/Home
> >
> > >  What changes and challenges are being faced?
> >
> >   The main challenge is time.
> >
> >   The changes are sweeping.  While the configuration files look largely
> > similar, almost everything has changed under the hood.
> >
> >   Things which used to be impossible are now trivial.  But some simple
> > things have unfortunately gotten more complex.
> >
> >   The main thing is that the requests are now fully asynchronous.  The
> > interpreter has it's own scheduler, and each request has it's own
> > interpreter stack.  The result is that the server needs fewer threads to
> > actually run things.
> >
> > >  What does the roadmap look like?
> >
> >   See the Wiki page above.
> >
> > >  Is there going to be a formalization of unlang?
> >
> >   What does that mean?
> >
> > > What work is currently being done?
> >
> >   Lots and lots.  The best thing here is to watch the git log.
> >
> >   Perhaps a better question is this: What are you looking for?
> >
> >   i.e. if you just want to know about v4, download it and look.  On the
> > other hand, if you're looking for a particular feature, then it's best to
> > ask about that.
> >
> >   Alan DeKok.
> >
> >
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
>
> --
>
>
>
> Please be advised that this email may contain confidential information.
> If you are not the intended recipient, please notify us by email by
> replying to the sender and delete this message. The sender disclaims that
> the content of this email constitutes an offer to enter into, or the
> acceptance of, any agreement; provided that the foregoing does not
> invalidate the binding effect of any digital or other electronic
> reproduction of a manual signature that is included in any attachment.
>
>
>
> <https://twitter.com/arroyo_networks>
> <https://www.linkedin.com/company/arroyo-networks>
> <https://www.github.com/ArroyoNetworks>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html