> Radius nt 3.0 has cacheing. My understanding is that this allows users to
> still be authenticated from cached data , in the event of link failure
> between the radius server and the radius client.
> I tried to verify this if it really works. My experiment failed. This is how
> i set it up:
RadiusNT caches the data in your sql database to allow folks to
authenticate and receive accounting data when it looses it's database
It doesn't cache previous authentications proxied from other radius
> Then without changing anything, i pull the 'plug' to simulate a link
> failure. the radius server cannot ping or trace route to the remote radius
> server. I then dialup into the NAS. Authentication fails. On the radius -x15
> screen, we see a lot of 'forwarding' but no response from the remote radius
> server (since the link is down).
> At this point, shouldnt the radius server switch over to the cache data and
> authenticate the user??
> btw, i enable radius nt to cache 5 days initial.
For more information about this list (including removal) go to: