Yes. Ascend RADIUS ("patched Radius") does not support Proxy RADIUS.
You should not use a RADIUS server in a proxy chain that does not support
Proxy RADIUS -- even at the end.
To give a more detailed answer -- Ascend RADIUS does not support the
CHAP-Challenge attribute. The use of the CHAP-Challenge attribute is
required when using CHAP with Proxy RADIUS.
So, to answer the question in your Subject - this is not a bug in Access
Control. In fact, if you used Access Control in both locations it would
work. The problem is that you are trying to use Ascend RADIUS in a role
it was not designed to fill. You can certainly modify Ascend RADIUS to
do the right thing - you have the source code - but it might be better
to just use a different RADIUS server. (If you need a freebie look at
Merit RADIUS 2.x)
++ 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-->
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<HR>
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg10030.html">Re: (ASCEND) RADIUS authernate servers sequence</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg10027.html">(ASCEND) Pipeline P50 - 5.1Ap2</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg10008.html">(ASCEND) Another Ascend Access Control Bug ????</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg07356.html">(ASCEND) Modem card does not answer</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="mail2.html#10029"><STRONG>Main</STRONG></A></LI>
<LI><A HREF="thrd117.html#10029"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</BODY>
</HTML>