Hi I had a general question regarding the behavior of an RADIUS server in the following scenario:
When using the EAP attributes (<draft-aboba-radius-rfc2869bis-10.txt), Radius has the "EAP Start" packet for the client to indicate to the radius server about the start of an authentication handshake. Now, the server can send a response packet with the "Session-Timeout" attribute optionally included in its response, indicating to the NAS how long the session must remain active. What would be the behavior in a case where the "Session-Timeout" attribute is not set by the server ? Is there a default value for the duration of this authenticated session that the NAS would use ? Or is this session authenticated for an infinite duration of time. This question would make sense in the context where the NAS would also implement the accounting attributes as well. In such a case, the NAS would be sending an "Accounting Start" packet to the accounting server whenever it sends a "Start" packet to the RADIUS server. However, when does it send the "Accounting Stop" packet to the accounting server, if there is no corresponding "Session-Timeout" associated with this session ? Regards Prashant ========================== Prashant Murthy @ LVL7 Systems http://www.geocities.com/prashthy ========================== - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
