Maybe I'm a glutton for punishment. :-)
Several months ago, I set up session limits for my customers. I am
currently using a memory database becuase we can't "justify the cost" of
using SQL (according to my boss).
The problem I hit was that one of my NASes uses a special
User-Service-Type (I think that's the one) of Virtual, and I didn't want
those logged in my session database.
So I posted to the list under the assumption that I would be allowed to
use my SQL server for the project, but I have been expressly forbidden by
someone who doesn't know much about it. :-)
The solution presented was to make a handler to send requests that use the
'Virtual' type to the memory DB, and all the stuff that I care about to
the SQL DB.
Well, now that I've been degraded to a memory DB, this option won't work.
So I had a great idea.
I made a module called SessNONE.pm that does nothing... that is, add,
delete, and clearNas do nothing and exceeded always returns zero.
It seems to work okay, but I think the problem is in my config. Check
this out:
------
<SessionDatabase INTERNAL>
Identifier InMemory
</SessionDatabase>
<SessionDatabase NONE>
Identifier Void
</SessionDatabase>
<Handler NAS_Port_Type = Virtual>
SessionDatabase Void
</Handler>
<Realm DEFAULT>
SessionDatabase InMemory
RewriteUsername s/^([^@]+).*/$1/
RewriteUsername s/^\s*$/unauthenticated/
RewriteUsername tr/A-Za-z0-9_@//cd
AcctLogFileName %L/detail/detail.%Y%m%d
AcctLogFileFormat %{Timestamp} %{Acct-Session-Id} %{User-Name}
%{NAS-IP-Address} %{Acct-Status-Type} %{Service-Type} %{NAS-$
PasswordLogFileName %L/password.log.%Y%m%d
RejectHasReason
<AuthBy DBFILE>
Filename %D/users.dbm
AddToReply User-Name="%U"
NoDefaultIfFound
</AuthBy>
</Realm>
-------
What happens is that session limits are completely ignored, because
according to my trace, everyone is handled with the 'Void' session
database!!! Did I make a mistake in this config?
Thanks for your help... if anyone else is interested in SessNONE.pm let me
know...
--
Dave Lloyd
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
