Hi - The acct-session-id attribute has the length defined as =>3 in RFC 2059. Is anyone aware of any practical limitations on the length of this attribute? Does FreeRadius support the length of this attribute to be let say 300bytes, and are you aware of any other Radius servers that may have problem with larger lengths? Thanks, Marlon
Marlon Duksa wrote:
The acct-session-id attribute has the length defined as =>3 in RFC 2059.
See RFC 2865 for the most recent definition of RADIUS.
Is anyone aware of any practical limitations on the length of this attribute?
RFC 2865 limits the maximum length of an attribute.
Does FreeRadius support the length of this attribute to be let say 300bytes, and are you aware of any other Radius servers that may have problem with larger lengths?
The limit is 253 bytes. I suspect that many NASes and servers won't handle that. My guess is that 32 bytes is OK. But for anything over 64 bytes, the odds of it working go down sharply. Alan DeKok.
Thanks Alan. Why do you think that anything longer than 64bytes would be hard to implement in NASes? Marlon On Tue, Mar 30, 2010 at 3:37 PM, Alan DeKok <aland@deployingradius.com>wrote:
The acct-session-id attribute has the length defined as =>3 in RFC
Marlon Duksa wrote: 2059.
See RFC 2865 for the most recent definition of RADIUS.
Is anyone aware of any practical limitations on the length of this attribute?
RFC 2865 limits the maximum length of an attribute.
Does FreeRadius support the length of this attribute to be let say 300bytes, and are you aware of any other Radius servers that may have problem with larger lengths?
The limit is 253 bytes. I suspect that many NASes and servers won't handle that. My guess is that 32 bytes is OK. But for anything over 64 bytes, the odds of it working go down sharply.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (2)
-
Alan DeKok -
Marlon Duksa