I think the consensus is that this is a bad idea for a generic feature/enhancement. If you wish to do this on a specific installation, and accept the responsibility for the potential security breach ;( then you have access to the RADIUS source, and should be able to do this with a little "hacking". Our security group would for sure reject this request for AAC for the same reasons. Kevin ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <STRONG>Follow-Ups</STRONG>: <UL> <LI><STRONG><A HREF="msg09775.html">Re: (ASCEND) ASCEND RADIUS FEATURE REQUEST</A></STRONG></LI> <UL> <LI><EM>From</EM>: ascend@digistar.com</LI> </UL> </UL> <!--X-Follow-Ups-End--> <!--X-References--> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg09627.html">(ASCEND) ASCEND RADIUS FEATURE REQUEST</A></STRONG></LI> <UL> <LI><EM>From</EM>: ascend@digistar.com</LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg09673.html">Re: (ASCEND) RADIUS IP pools: Adding second MAX</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg09672.html">Re: (ASCEND) _very_ poor ISN generation on Ascend MAX</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg09635.html">Re: (ASCEND) ASCEND RADIUS FEATURE REQUEST</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg09775.html">Re: (ASCEND) ASCEND RADIUS FEATURE REQUEST</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail14.html#09674"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd201.html#09674"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>