Re: Port limit & concurrency checks, wholesale accounting, and dealing with dead servers

"Troy Settle" <[EMAIL PROTECTED]> wrote: > I'm sorry, I thought this was why most radius servers now have > concurrency checking built in. Why would FreeRadius have something like > radcheck if not to enforce the total number of concurrent logins each > user is allowed to have? FreeRADIUS does

RE: Port limit & concurrency checks, wholesale accounting, and dealing with dead servers

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Alan DeKok > Sent: Friday, February 20, 2004 3:25 PM > To: [EMAIL PROTECTED] > Subject: Re: Port limit & concurrency checks, wholesale > accounting, and dealing with

Re: Port limit & concurrency checks, wholesale accounting, and dealing with dead servers

"Troy Settle" <[EMAIL PROTECTED]> wrote: > I've searched a bit on this, but am coming up empty handed so far. Can > anyone point me in the right direction for enforcing port-limit as > passed by the home server? I don't think you're supposed to enforce it. The NAS is supposed to enforce it. >

Port limit & concurrency checks, wholesale accounting, and dealing with dead servers

I've searched a bit on this, but am coming up empty handed so far. Can anyone point me in the right direction for enforcing port-limit as passed by the home server? I've come to the conclusion that depending on my wholesale customers to enforce concurrency limits is not getting me very far. Sec