<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">OH! I've looked too many lines of code over the last week.<div><br></div><div>I have no idea how to patch but will investigate. Was thinking we might have to use nas-id instead.</div><div><br></div><div>The ultimate intention was to use the mac address of the nas and a nas specific shared secret. </div><div><br></div><div>In your opinion, are there better ways to deal with dynamic clients?</div><div><br></div><div>Thanks again</div><div><br></div><div><br><div><div>On 24 Oct 2011, at 19:52, Phil Mayers wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 10/24/2011 07:02 PM, JennyBlunt wrote:<br><blockquote type="cite">If I put in default authorize section, the called-station-id is present.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">What I just don't understand is why it doesn't work in dynamic hosts and<br></blockquote><br>As per the comments in the "sample" dynamic-clients:<br><br># The request that is processed through this section<br># is EMPTY. There are NO attributes. The request is fake,<br># and is NOT the packet that triggered the lookup of<br># the dynamic client.<br>#<br># The ONLY piece of useful information is either<br>#<br># Packet-Src-IP-Address (IPv4 clients)<br># Packet-Src-IPv6-Address (IPv6 clients)<br>#<br># The attributes used to define a dynamic client mirror<br># the configuration items in the "client" structure.<br><br>You'll need to patch the source to make what you want work. This may (or may not) be a generally useful patch; the problem is that, in many cases, a single NAS might have >1 Called-Station-Id e.g. multiple BSSIDs for a wireless AP.<br>-<br>List info/subscribe/unsubscribe? See <a href="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html</a><br></div></blockquote></div><br></div></body></html>