I have Radius 2.0 compiled and running on FreeBSD 2.2.1. Here's the
start message from syslog:
Apr 30 18:51:58 hermes radius[7458]: ./radiusd-2.0: RADIUS version 2.0
96/10/30 NDBM NOSHADOW PASSCHANGE flat_users
The daemon has been sucessfully operating (about 2 weeks now) without
incident for a crew of pm2er30s and some USR Netservers 16/Is.
Last week we added a Shiva Access Switch (SAS). At first I only turned on
the RADIUS authentication in the SAS. Immediately messages like these
popped up in the logfile:
Apr 30 18:51:58 hermes radius[7458]: could not cache client datum for
host SAS-1.GrandHaven.novagate.net
Apr 30 18:51:58 hermes radius[7458]: could not cache client datum for
host 205.138.138.13
Apr 30 18:54:44 hermes radius[7458]: could not cache client datum for
host SAS-1.GrandHaven.novagate.net
Apr 30 18:54:44 hermes radius[7458]: could not cache client datum for
host 205.138.138.13
It does it constantly on both the primary and secondary RADIUS servers.
Well, regardless of the syslog message the server was authenticating so I
left it alone. Then I turned on RADIUS accounting in the SAS and
nothing. No accounting records were being recorded anywhere (primary or
secondary). So it appears that the SAS and RADIUS accounting do not like to
work with one another. All of a sudden (today) RADIUS started acting up
with the USR Netservers in addition to the SAS. Here's a snippet from the
syslog:
Apr 30 19:00:34 hermes radius[7473]: could not cache client datum for
host X2-1.GrandHaven.novagate.net
Apr 30 19:00:34 hermes radius[7473]: could not cache client datum for
host 205.138.138.18
Yes, just to make sure I double checked the clients file. I have entries
for the FQDN, the IP address, and the RAS name with the correct auth key
for all of the units.
Any ideas on what might be causing this? Anyone had any success with
RADIUS accounting and the Shiva Access Switch? TIA!
Sincerely,
Dave Munroe
gatekeeper@novagate.com