[RadiusNT] cacheing bug??

Fri, 7 Jan 2000 17:04:17 +0800

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:

I have a USR netserver/16 acting as my NAS. Radius NT 3.0 is installed in an
NT 4.0 sp 5. The emerald management suite is also installed in this same
machine with sql 7.0 sp1. I also enable user proxy roaming. I setup romaing
servers and romaing domains for domain.com.

When the link to the remote radius (domain.com) is active(UP), i use a win98
machine to dialup into the NAS with the user@domain.com, this in turn will
force the radius to act as a proxy and forward it to domain.com. The
authentication process works, and i am able to browse the internet.

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: