Hmmm - The "logic" of the request does not really make much sense... If the FreeRadius server is responding to the NAS but the mysql server back-end is not responding that does not mean the "radius" server is broken...
I would think you could setup to authenticate through multiple mysql backend servers to handle the event of the primary being offline or down instead of forcing a purfectly good working radius server to "act" like it was down.... and if you setup a secondary freeradius server to handle the event of the primary going down you can use the mysql servers that the first radius server points to for authentication by the second radius server so they have a common shared database (double redundancy). Check the email archives - I remember someone answered how to setup multiple sql servers to be used for user authentication in freeradius (which is what you really want to do here)... if the first mysql server is not responding the second (or next in line) will perform the response instead.... gm... ----- Original Message ----- From: "jesk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, May 30, 2004 6:38 AM Subject: Re: mysql failover > On Friday 28 May 2004 17:36, jesk wrote: > > hi everybody, > > > > is there a way to configure freeradius to NOT answer to a NAS if the > > mysql-backend is down, so that the nas can switch to the next secondary > > configured freeradius server with its own mysql-backend? > > i tested freeradius and shutted down the mysqlserver, the request from > > the nas came in and freeradius rejected the request in cause of the > > closed mysqldb-handle, now the nas rejected the ppp session and didnt > > requested the secondary freeradius. > > can somebody help me? > > > > > > thanks in advance, > > > > christian > > > > > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > > no way? > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
