Ivan/Alan, Other then killing radiusd are there any other solutions to force radius to drop request if all databases cannot be reached ?
With the latest release 2.1.4 my failover works fine, but still if there is a network issue connecting to ALL Databases I do not see any practical reason returning Access-Reject as NAS treats radius as alive and cannot failover to another radius server. For my situation since radiusd keeps everything in DB and if ALL databases cannot be contacted the radiusd should not respond at all. Is there any way to force radiusd to drop request and not to respond with Access-Reject? Thanks for your reply. tnt-4 wrote: > >>Say I do not want to return reject in this case and I want the switch to >>understand that radius is down and retry another radius server (a >>backup/failover). > > So call a script that executes killall radiusd - that should do it. But > that's insane. > >>Because if I return reject the NAS device treats this as radius is UP and >>running. > > But your radius server *is* up and running. sql module is not working. So > fail-over to another sql server or users file. > > http://wiki.freeradius.org/Fail-over > > Ivan Kalik > Kalik Informatika ISP > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > > -- View this message in context: http://www.nabble.com/Freeradius-2.1-1%3A-failure-modes-tp22413666p22444908.html Sent from the FreeRadius - User mailing list archive at Nabble.com. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
