I wont be adding NASes, but users will do, so i am thinking 0-10 a day.
Linking to a dynamic list using interal its not a good solution, becouse i
will need to wait for list update after adding NAS.
Other solution i am thinking is to run two instances of server and restart
them in round robin and use iptables to redirect packets to actual working
server.
Goal is to serveradius to third party as a service, so users will add their
own nases, modified them etc, at this stage i cannot really say how many
times a day i will need a restart, but i am wondering about also about
following soltion:
Run two servers:
Primary and Secondary, primary will be restarted once a day, and secondary
every time NAS list will be changed. After adding a NAS primimary will not
respond (unknown NAS) so NAS will ask secondary instead) also request from
other nases will not be lost becouse primary is not restarded on NAS list
change.
What do you think ?
________________________________
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
g] On Behalf Of Marinko Tarlac
Sent: 23 January 2008 10:05
To: FreeRadius users mailing list
Subject: Re: NAS list update without restarting radius server.
Well how many times per day do you add nases?
On Jan 23, 2008 10:20 AM, liran tal <[EMAIL PROTECTED]> wrote:
Hey Alan,
On Jan 23, 2008 9:47 AM, Alan DeKok
<[EMAIL PROTECTED]> wrote:
liran tal wrote:
> Maybe freeradius can read the nas list from sql at
startup to some
> linked list and this list will be updated every
given interval with a query
> to the database.
It's more complicated than that. The NASes need to
be deleted, too.
And this has to be done without affecting normal
server operation.
As always, patches are welcome.
Well, every given interval a query will run on the database
server to get the
list of nases and it will build a new linked list based on
that and delete
the other nodes and free the pointers of those.
I guess that coming up with a method to check against each
nas if it's
there or not, and to remove or add it based on a check is
do-able
but would probably face some efficiency issues where-as I
think it
would be proper to create a new linked list with whatever
nases that
query returns and free the previous linked list from memory.
I haven't had a look at the relevant code but it seems quite
basic
to implement unless I'm over-seeing some critical aspects
:-)
I'll be glad to take a look if you can refer me to the
current piece
of code where freeradius handles the nas lists read from the
database
and stores them.
Regards,
Liran Tal.
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
