> I am running Radius 2.0.1 on Solaris 2.5.1 against a PM3 runing comOS 3.7.
> I am seeing some issues related to the new version.
>
> 1) I noticed that a new directory is being used for the accounting 'detail'. It is using the
> IP address of the portmaster instead of the hostname. Does anyone know why or how
> to have it use the old directory based on hostname?
You should check to see that the RADIUS client & server has a functioning
DNS system and can resolve a host number into a name (ie. correct PTR
records in the IN-ARPA section of the DNS).
>
> 2) I noticed a 'Request-Authenticator' record in the accouting 'detail' log. The value is
> 'Unverified'. The troubleshooting section I have found referrs to this being related to the
> Shared Secret on the portmaster and the 'clients' file not matching. I have verified that
> they do match. Any ideas?
No. Sorry.
>
> 3) THE BIG PROBLEM... The radiusd daemon keeps dying. Sometimes it will run for 20-30
> minutes and sometimes it will run 60+ minutes before dying. Any ideas? I have tried the
> 'radiusd -s' option with no luck as well.
I had the same problem with RADIUS 2.0 and Linux 2.0.30. I fixed the
problem by upgrading to RADIUS 2.0.1. I suggest that you check the syslog
files and look for a message that says something like: RADIUSd died on
signal 100. If that is the message that you recieve then you probably had
the same problem that I did. The parent RADIUS process was killing its
orphaned children and accidently killed itself. If you can isolate the
problem I'm sure Livingston can fix it.
> Some of these seem like insignificant issues except that they could be an indication of a
> much larger issue or configuration that I have not encountered or addressed.
>
> None of these problems existed before the upgrade from radius 1.6.
>
> Any help is greatly appreciated
>
> Roger
>
>
>
Good Luck!
Tres
tres@chaffee.net
--If you think it to be idiot proof,
then you haven't met the "Latest 'n Greatest" idiot!