This came to our attention regarding the ESVAnet radiusd support of
session limiting, as per the suggestion from Carl Rigney on how it could
be done.
The general idea is for radiusd to keep a table of which users are on
which ports, adding an entry when an accounting "start" record is
received and rmoving it when an accounting "stop" record is received.
It now appears that it is possible to receive a "start" record and then
never receive a corresponding "stop" record. Instead, we receive a new
"start" record when the port is reused. This becomes more apparent now
that we have switched our lines to round-robin hunting.
I would regard this as a bug. ComOS should never send an accounting
"start" record without later sending a corresponding "stop" record when
and if the session terminates for any reason.
Comments? Am I off base here?
--
("`-/")_.-'"``-._ Leo Savage
. . `; -._ )-;-,_`)
(v_,)' _ )`-.\ ``-' leo@esva.net
_.- _..-_/ / ((.'
((,.-' ((,/ http://www.esva.net/~leo/