Handling of duplicates in clients.conf

A.L.M.Buxey at lboro.ac.uk A.L.M.Buxey at lboro.ac.uk
Thu Mar 26 10:52:12 CET 2009


Hi,

> Thanks for taking the time to share your thoughts Alan.  I recently
> started investigating SQL for client and huntgroup definitions and I
> appreciate your insight.  Does using the SQL approach still require a
> server restart to refresh any changes?  Do you know if there are any
> plans to refresh the clients via radmin?  (I realize this isn't a
> trivial matter..)

use dynamic-clients - this calls an SQL query which, if the target is now in 
your DB will update the client list on the fly. no server restarts needed.
radmin lists and shows the client etc

> What are your thoughts about treating the conflict as a more severe
> error and not allowing the server to start?  Does this seem better than
> the current approach for people that aren't using SQL?  It just seems
> like there must be a better means of notifying the admin of the
> configuration issue than breaking the valid clients found after the
> conflicting entry.  It's very easy to miss the current error message
> among all of the other startup messages.  If the server failed to start
> and this error was prominently displayed, I think the configuration
> problem would be noticed more quickly.  

I seem to recall the error message being one of the last things printed
out before the server barfed

alan




More information about the Freeradius-Users mailing list