Re: Freeradius-Users Digest, Vol 95, Issue 30
The most recent (which hasn't changed in some time now) can be found: http://dev.coova.org/svn/cjradius/trunk/freeradius/rlm_jradius/rlm_jradius.c Cheers, David
Date: Thu, 7 Mar 2013 11:02:17 -0500 From: Arran Cudbard-Bell <a.cudbardb@freeradius.org> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Failed to load module "jradius" freeradius server Message-ID: <C9EB7AE3-492A-4D59-BE04-1645044DC3E8@freeradius.org> Content-Type: text/plain; charset=iso-8859-1
On 7 Mar 2013, at 10:55, Iftakhul Anwar <anwar@meruvian.org> wrote:
Actually i install freeradius from apt-get ,
Right, so jradius won't have been built.
jradius support is going away, it will *NOT* be in Version 3 unless someone contributes a new version of the module which works with the updated jradius protocol.
-Arran
On 7 Mar 2013, at 17:54, David Bird <wlan@mac.com> wrote:
The most recent (which hasn't changed in some time now) can be found: http://dev.coova.org/svn/cjradius/trunk/freeradius/rlm_jradius/rlm_jradius.c
Ok. The main issues with that code are: * It won't compile against current master branch. * It doesn't use the connection pool API which is an absolute requirement for all modules in 3.0. * If the protocol encoding has changed, then protocol version mismatches should be detected and the user should be informed of what's happened unless the protocol encodings are interoperable. * The protocol will need to be extended to pack nested TLVs, and possibly to deal with extended TLVs. Though this work is dependent on the final stage of the talloc changes. If you're willing to work with us to make those changes, then we'd be happy to include rlm_jradius in version 3.0. -Arran
participants (2)
-
Arran Cudbard-Bell -
David Bird