Thanks Alan. <br>Why do you think that anything longer than 64bytes would be hard to implement in NASes?<br>Marlon<br><br><div class="gmail_quote">On Tue, Mar 30, 2010 at 3:37 PM, Alan DeKok <span dir="ltr">&lt;<a href="mailto:aland@deployingradius.com">aland@deployingradius.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Marlon Duksa wrote:<br>
&gt;  The acct-session-id  attribute has the length defined as =&gt;3 in RFC 2059.<br>
<br>
</div>  See RFC 2865 for the most recent definition of RADIUS.<br>
<div class="im"><br>
&gt; Is anyone aware of any practical limitations on the length of this<br>
&gt; attribute?<br>
<br>
</div>  RFC 2865 limits the maximum length of an attribute.<br>
<div class="im"><br>
&gt; Does FreeRadius support the length of this attribute to be let say<br>
&gt; 300bytes, and are you aware of any other Radius servers that may have<br>
&gt; problem with larger lengths?<br>
<br>
</div>  The limit is 253 bytes.  I suspect that many NASes and servers won&#39;t<br>
handle that.  My guess is that 32 bytes is OK.  But for anything over 64<br>
bytes, the odds of it working go down sharply.<br>
<div><div></div><div class="h5"><br>
  Alan DeKok.<br>
-<br>
List info/subscribe/unsubscribe? See <a href="http://www.freeradius.org/list/users.html" target="_blank">http://www.freeradius.org/list/users.html</a><br>
</div></div></blockquote></div><br><input id="gwProxy" type="hidden"><input onclick="jsCall();" id="jsProxy" type="hidden"><div id="refHTML"></div>