Parsing accouting records after the fact does that.
But that does NOT work for realtime needs, as I have explained countless
times. Because of the way RADIUS works you have a race condition inherent
in the system that is COMMON, not rare. It is far too easy to have the
accounting records show someone logged in when they are not. Especially
with ISDN when someone can disconnect and reconnect in litterally a second
or two.
>Why doesn´t Livingston say "Sorry, we are aware of the problem of multiple
>logins, but we currently have no solution for it". Instead, you tell the ISPs
>that this problem is no problem.
I've never said it isn't a problem, I said there is no good technical solution
now and none we can see without a new system. And since this is a problem
shared by all, and the IETF has asked for people to work on this, we're are
against running off and making up some kind of proprietary system to do it.
It would be a lot of work, and we'd have to do it over when someone finally
decides to form a WG to address it. And the demand, while there are a few
vocal people, really isn't close to the demand for other features.
I'm all for a *real* solution. But it doesn't seem that it is important
enough to the people asking for one to actually invest the time in a WG to
develop one.
Think about it - a real resource management protocol could handle multiple
logins, RADIUS IP pools, maybe even cover filter distribution (yes we
have ChoiceNet, but maybe an open system), serve location tables from a
central server, etc...
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588