I.e. Portmaster bundles the username/pw up, sends it to the radius server
(hoping for a quick response of ACK or NAK). How long does the PM wait for
that ACK or NAK (in seconds). By my tests, it looks like 8-10 seconds.
WHY? I'm working on a new method of multi-line usage control (i.e. no
more multiple logins) building on the old esva code for radius 1.16.
ACtually I patched almost every hole/conceptual problem that MegaZone
through on this list a while back (yea i know everyone at the IETF meeting
came up with these theoretical limits etc). I have a method that can
check to make 100% sure, but needs about 5 seconds on average to query
the pms to double check a multiple login etc, and setting my own internal
time out of 15 seconds to auto-ACK the user in case of internal failure on
the radius server is NOT workign since the PM is apparently folling the
rfc quite perfectly and re-sending its queries to get the job done before
I can be 100% sure of the first query.
MAke sense? It barely does to me after way too many hours coding today...
Adam Wills Global 2000 Communications
Director of Networking Systems 1840 Western Ave.
sysadmin@global2000.net Albany, NY, 12203
http://www.global2000.net (518) 452-1465