RE: Looking to pay for customization
Thank you all for your comments. What I don't understand is that it seems like it was very easy to do in a previous version: http://lists.cistron.nl/pipermail/freeradius-devel/2005-January/007870.html http://lists.cistron.nl/pipermail/freeradius-devel/2005-January/007871.html Can something similar be done in version 2? On 13-Apr-09, at 11:46 PM, Eric Geier wrote:
Hi, if anyone is interested in customizing the source code for me, please check out either site:
http://www.getacoder.com/projects/c_developer_radius_expe_102912.html
http://www.odesk.com/jobs/Developer-with-RADIUS- Experience_~~f48a82c177d7e1b 3?tot=129&pos=7
I would like FreeRADIUS to check incoming requests based upon the domain (derived from the username), instead of the NAS IP addresses.
Eric Geier wrote:
Thank you all for your comments.
What I don't understand is that it seems like it was very easy to do in a previous version: http://lists.cistron.nl/pipermail/freeradius-devel/2005-January/007870.html http://lists.cistron.nl/pipermail/freeradius-devel/2005-January/007871.html
Yes. Things change. The code in 2.x is a lot more capable than 1.x. However, as a result, it has some limitations that 1.x didn't. e.g. Shared secrets can now be any length, not just 32 characters. However, this means that the shared secrets *cannot* be defined per request packet. They *must* be defined per client.
Can something similar be done in version 2?
See "dynamic clients". That code could be updated to "peek" at the entire packet, and create new clients based on more than just the IP address. But it *is* more work than it would have been in 1.x. Alan DeKok.
participants (2)
-
Alan DeKok -
Eric Geier