I'll do that, however unless the fail-over has something to do with
freeradius, we already do it (with our access servers)... the problem
is... freradius is sending a reject packet back when it doesn't get a
responce from the database....
EXAMPLE:
Database server gets restarted (for whatever reason) at 4am when we do
some maintence.
I now need to restart every one of our radius servers.. because they
don't reconnect the ODBC stream to MS SQL!
On 6/16/06, Michael Lecuyer <[EMAIL PROTECTED]> wrote:
I think that authenticating everyone if the database went down would be
called 'foolsafe' :) If your database is down you're out of business.
There are much better 'failsafe' methods - search for fail-over in the
FreeRadius documentation.
Matt wrote:
> Ok,
> Well with no answer to this question let me ask it another way...
>
> In the event of database (via ODBC) failure... is there a way I can
> make the radius server go into "failsafe" mode, and just authenticate
> anything?
>
> On 6/15/06, Matt <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>> We use FreeRadius with unixODBC and the rlm_sql to connect to a
>> Microsoft SQL database. All works great... except if the SQL database
>> goes down, firewall has the translate table, someone trips over a
>> network cable.... anything that causes the connection between the
>> radius and SQL to be disturbed, it just says
>>
>> "There are no DB handles available...." instead of reconnecting... the
>> only way I've found to reconnect, is to restart...
>>
>> Any comments or thoughts on this problem?
>>
> - List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
