Re: (ASCEND) Another Ascend Access Control Bug ????

[Tim Basher <basher@alpha.CES.CWRU.Edu>]

> NAS -----> patched Rasdius from Acend ---> OK
> NAS -----> Ascend Access Contol ------> Patched Radius ----> Error
> 
> I found out that this only happens with CHAP-Authorisation. So the
> Ascend secrets are ok.
> 
> Any Ideas ????

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:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: Re: (ASCEND) RADIUS authernate servers sequence
• Next by Date: (ASCEND) Pipeline P50 - 5.1Ap2
• Prev by thread: (ASCEND) Another Ascend Access Control Bug ????
• Next by thread: (ASCEND) Modem card does not answer
• Index(es):
  • Main
  • Thread