That isn't what it does. Port-Limit is defined in the RFC. It limits
the number of ports that can be aggregated in one MP connection.
It has NOTHING to do with concurrent logins.
They do have a feature that kind of does concurrent login control, but
it has, as all such features to date have had, loopholes.
>Hmmm...telebit is a holdover that we're currently using. So..are you
>suggesting that an isp must all of a sudden replace all of its older
>terminal servers to convert to radius? If so, economics are going to
I believe Telebit does RADIUS now.
And actually, it is common for ISPs to replace oddball older equipment
to simplify network admin tasks and avoid these very situations.
>in the process of switching the ciscos to radius. It sounds as if you're
>just entering into the market. Radius is a fairly new scheme... I think
>its entered into the limelight within the last year maybe last year and a
A lot longer than that - I didn't join Livignston until August 1995, and
long before I came here RADIUS was a a hot issue. Back at Xylogics I got
asked several times when Xylo was going to support RADIUS. (That's where
I was before here.) And it was widely discussed on USEnet and industry
mailing lists.
>half. I may be worng but I think the very first version of radius was
>released less than two years ago.. ISPs like ours have had to deal with
That is very wrong. VERY wrong.
RADIUS was first fielded in 1992. Several vendors - such as Ascend
and Computone, have been using it for some time now. It was more than
two years ago that additional vendors started adding it, and many have
had support for over a year. At this point I believe every major NAS
vendor supports RADIUS.
>remote authentication for the last four years and longer.
That's nice - RADIUS was there. Livingston was first of course. I
believe Ascend had it in their first access products. Computone had it
from the start in their PowerRacks I believe. Cisco has had it for
a while.
>number of users online. The number of users online traditionally
>increases from 4pm to 1am. The time it takes for the radius server to
>individually poll and check each radius device would take too long during
Wrong. I know, our next generation server handles conncurrent logins
cleanly and natively. And it will outperform the current generation
servers handily. You only need to poll IF you show the user is still on
AND they have reached their limit.
So polling only need occur in cases of missed STOP records, delayed STOP
records, and actual attempts at abuse. Under the vast, VAST majority of
use no polling need be done.
>busy hours. Theoretically the latency would force the radius device to use
>the secondary authenticator.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588