Hello Charlie -
There are a number of options, depending on what exactly you want to do.
Basically, Radiator can use a session database to control individual
simulataneous use, or it can use the AuthBy PORTLIMITCHECK clause to do much
more sophisticated port limit checking. You should have a look at the following
sections in the manual: 6.7, 6.38 and 13.1.
hth
Hugh
On Wed, 30 Aug 2000, ...Charlie... wrote:
> Hello All,
>
> I've noticed that quite often the above subject will come up. People are
> interested in either allowing or not allowing the use of multiple ports by
> the same user. We have always used other means (maxstat, pmmon) to control
> port use but now it looks as though we will need to use Radiator for both of
> the above functions. I looked in the FAQ's and did not find anything
> addressing this issue (surprising). I have also attempted to search the
> archives but quite often all I found was a post saying to search the
> archives. I would appreciate any help any of you could provide. We use a
> Unix passwd file.
>
> Thanks in advance
>
> Charlie
>
> P.S. Does any part of the manuel specifically address this issue?. We are
> using 216.3
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
