I guess I could just use &quot;NAS-Identifier&quot; plus &quot;NAS-IP-Address&quot; and carry on, because I can&#39;t see anywhere that Packet-Src-Ip-Address from our NASes. We have just 2 NASes, so I&#39;ll skip the huntgroups.<br>

<br>Thanks for your answers!<br><br><div class="gmail_quote">2012/6/15 alan buxey <span dir="ltr">&lt;<a href="mailto:A.L.M.Buxey@lboro.ac.uk" target="_blank">A.L.M.Buxey@lboro.ac.uk</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hi,<br>
<div class="im"><br>
&gt; Packet-Src-Ip-Address is one way. Or set huntgroups for your own<br>
&gt; NASes (NAS-IP-Address, etc), then just check for membership of the<br>
&gt; huntgroup.<br>
<br>
</div>NAS-IP-Address - dangerous....its something that can clash with remote sites -<br>
as its local specific - and therefore the IP addresses used might be the same.<br>
<span class="HOEnZb"><font color="#888888"><br>
alan<br>
</font></span><div class="HOEnZb"><div class="h5">-<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>