Hi Hugh
At 11:16 AM 2/3/00 +1100, Hugh Irvine wrote:
> > . Is the SessionDatabase DBM recomended if you have to serve lots of
> > sessions? I had the problem that the server ate up all the cpu (and
> started
> > to ignore requests) once i enabled the MaxSession option on a DBM with
> > about 1500 entries, and serving about 15 requests/sec
> >
>
>What version of Radiator are you running? And what hardware/software
>platform? We have recently had problems with DBM session databases on
>Solaris. There was also a fix to the session database code in Radiator 2.14
>(from history.html):
>
> Fixed a problem in the internal SessionDatabase,
> where it would ask
>all the NAS ports for all users to double check apparent logins.
We are running radiator 2.14.1 on FreeBSD 2.2.7 running on a 256Mb pentium
II compaq proliant. For the tests, all clients have NasType ignore
About the problem that the session database has to have the original
username, not the rewriten one: wouldnt it be posible to have both the
original username (to do the queries to the nas) and the rewriten username
(to do the concurrency verification)?
Regards
Alejandro Dau
PS: I downloaded the new version of AuthRADIUS.pm from the patches page
(the new feature for replyhook seems useful). I had some problems with it,
as radiator doesnt seem to reply to clients requests when an authby radius
section has the parameters 'NoForwardAuthentication' or
'NoForwardAccounting' enabled. My configuration works with the AuthRADIUS
that came with 2.14.1 but not with the one from the patches page. Here is
the authby radius section that I checked:
<AuthBy RADIUS>
NoForwardAuthentication
NoForwardAccounting
RetryTimeout 2
Retries 2
Host ww.xx.yy.zz
Secret asdf
</AuthBy>
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
