(RADIATOR) Radiator Session Handling and SNMP...

[Rickard Ekeroth]

Hello Hugh!

I wrote to you guys a while ago about the behaviour of Radiator when it
queries a NAS using SNMP. I am not sure if my reply to the reply that you
sent me was sent properly. Anyway here are my thoughts again:

If Radiator fails to query a NAS for a specific session using SNMP it will
assume that the session in question is not on the NAS. However during the
following back-off period (60 seconds) the behaviour is the reverse:
Radiator assumes that the session is still on the NAS and the user is denied
access based on max session count.

Should not the behaviour be the same in both cases? Personally I would
prefer if the Radiator denied access in both cases. This is because I have a
consumption debit scheme based on accounting stop packets and I would prefer
not to delete sessions unless I am sure that it is not on the NAS anymore
(because I can not debit a session that did not receive a stop packet since
I do not know the actual session time).

Regards,

Rickard Ekeroth @ SpiderNet
Software Developer / Analyst
rickard at spidernet.net
+35722844870

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.