Hi, A couple of questions on Acct-Interim-Interval 1. I wanted to know if the Acct-Interim update that comes from the NAS has any relevance as far as the user session maintained in the radius server is concerned. Meaning that is it treated like a keep-alive of some sort. If the Acct-Interim-Interval is configured to be 100 seconds and the NAS sends the Interim-Update after 200 seconds does the freeradius server care ? 2. What is the typical value of this attribute, I ask because if this value is configured to be small then it will generate a lot of interim updates from a NAS that supports large number of subscribers. At the same time I am not sure how the service providers who deploy the server use this Attribute and how often do they want the updates. Thanks, Vinay
Hi,
-----Original Message----- From: freeradius-users-bounces@lists.freeradius.org [mailto:freeradius->users-bounces@lists.freeradius.org] On Behalf Of Vinay Wagh Sent: 02 October 2007 20:47 To: FreeRadius users mailing list Subject: Questions on Acct-Interim-Interval
Hi,
A couple of questions on Acct-Interim-Interval
1. I wanted to know if the Acct-Interim update that comes from the NAS has any relevance as far as the user session maintained in the radius server is concerned. Meaning that is it treated like a keep-alive of some sort. If the Acct-Interim-Interval is configured to be 100 seconds and the NAS sends the Interim-Update after 200 seconds does the freeradius server care ?
Acct-Interim-Update is an extrension to the Radius protocol to make it more robust for people who do accounting. It avoids losing the totallity of your session accounting if the stop record gets lost (or the NAS becomes unavailable). Not a keep-alive really...
2. What is the typical value of this attribute, I ask because if this value is configured to be small then it will generate a lot of interim updates from a NAS that supports large number of subscribers. At the same time I am not sure how the service providers who deploy the server use this Attribute and how often do they want the updates.
Interim updates increase the load on the NAS, especially with a lot of sessions. 100s sounds very short and could impact your authentication performance. I would send every 60mn or more. Anyone's tried below with a lot of subscribers maybe?
Thanks, Vinay
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
David Roze ---- http://www.netexpertise.eu
Vinay Wagh wrote:
A couple of questions on Acct-Interim-Interval
These are really questions for the IETF RADIUS standards group. That being said, they are partially covered in my document: http://www.ietf.org/internet-drafts/draft-ietf-radext-fixes-08.txt It will be issued as an RFC in a few weeks to months. Anyone implementing RADIUS systems *should* read it. They should also read my other document: http://www.ietf.org/internet-drafts/draft-ietf-radext-design-00.txt Which discusses protocol design issues.
1. I wanted to know if the Acct-Interim update that comes from the NAS has any relevance as far as the user session maintained in the radius server is concerned. Meaning that is it treated like a keep-alive of some sort. If the Acct-Interim-Interval is configured to be 100 seconds and the NAS sends the Interim-Update after 200 seconds does the freeradius server care ?
Many RADIUS servers *will* care. In some cases, it *is* treated as a signal that the user session is still alive.
2. What is the typical value of this attribute, I ask because if this value is configured to be small then it will generate a lot of interim updates from a NAS that supports large number of subscribers. At the same time I am not sure how the service providers who deploy the server use this Attribute and how often do they want the updates.
See RFC 2869 for recommended values. Alan DeKok.
participants (3)
-
Alan DeKok -
David Roze -
Vinay Wagh