Hi,
I can't seem to find any reference to making the
contents of the clients.conf accessible via SQL. We are
constantly making edits, and having to constantly reload
the server doesn't make sense.
Pointers to where I missed putting it into
MySQL, or if anyone knows how to would
Morning Tuc,
On Dec 31, 2007 2:15 AM, Tuc at T-B-O-H.NET [EMAIL PROTECTED] wrote:
Hi,
I can't seem to find any reference to making the
contents of the clients.conf accessible via SQL. We are
constantly making edits,
Have you thought about using a web application to manage your
On Wed, 2007-02-07 at 16:56 +0100, Alan DeKok wrote:
Maybe simply reloading the nas configuration from SQL at configurable
time intervals would do that?
Send a patch. :)
I'd love to, but at the moment I'm no real C coder.
The difficulty with doing automatic reloads is timing, and
Luca Corti wrote:
Please forgive my ignorance, but how is this different from what
Freeradius already does when handling SIGHUP?
There are some issues with the servers handling of HUP.
Wrt cron + kill -HUP I think that it may be a bit overkill just to
reload the NAS table.
Yes.
An
On Fri, 9 Feb 2007, Alan DeKok wrote:
The immediate question that comes to mind is Does FreeRADIUS reread its
configuration when it receives a -HUP?.
The immediate answer is have you tried reading the documentation?
To which I'd have to reply no (WRT this, anyways) and then ask if you
were
Gaddis, Jeremy L. wrote:
The immediate question that comes to mind is Does FreeRADIUS reread its
configuration when it receives a -HUP?.
The immediate answer is have you tried reading the documentation?
Alan DeKok.
--
http://deployingradius.com - The web site of the book
On Sat, 2007-02-03 at 12:12 +0100, Alan DeKok wrote:
It should be possible to mitigate the DoS potential somewhat, but
someone still has to write the code.
Maybe simply reloading the nas configuration from SQL at configurable
time intervals would do that?
ciao
Luca
-
List
Luca Corti wrote:
On Sat, 2007-02-03 at 12:12 +0100, Alan DeKok wrote:
It should be possible to mitigate the DoS potential somewhat, but
someone still has to write the code.
Maybe simply reloading the nas configuration from SQL at configurable
time intervals would do that?
Send a
On Wed 07 Feb 2007 17:56, Alan DeKok wrote:
Luca Corti wrote:
On Sat, 2007-02-03 at 12:12 +0100, Alan DeKok wrote:
It should be possible to mitigate the DoS potential somewhat, but
someone still has to write the code.
Maybe simply reloading the nas configuration from SQL at
Dan Mahoney, System Admin wrote:
My second question is, now that I've got a list of all my NASes in
SQL, has anyone written (or added to beta or something similar) code to do
*those* via SQL? Specifically we already have all our network devices
(and shared secrets) in a SQL database
Hey all,
Two questions, related to SQL...
1:
I recently became enamored by the power of SQL, and while I find no easy
way through SQL to do multiple check-items easily in a logical
fall-throughable order.
I.e. through SQL how would one do (for an entry level tech):
Jeremy nas-ip-address=the
11 matches
Mail list logo
