Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) Secret is Out
We have a Cisco 2524 at a remote site, connecting via BRI.
It worked until we upgraded our software from 5.0Ap42 to
5.0Ap48 in the hopes of fixing many of the ongoing problems
we've had with our Max 1800.
After much investigation and conversations between Cisco and
Ascend, we discovered that PAP authentication no longer worked
if CHAP was also available. Note that none of our settings or
configuration had changed on either end. This broke when
we upgraded to a new PATCH version of the software.
I have not seen this change documented. Is it yet another bug
that Ascend introduced when they were supposed to be fixing some,
or was this change actually intended (in a patch revision)?
The Ascend engineer we talked to said that the way authentication
was handled was a "matter of interpretation" when both PAP and
CHAP were offered, and acknowledged that the Ascend would not
interoperate properly with a lot of other devices. In fact, it
DID work until we upgraded the Ascend software. She was not
able to tell me why Ascend's interpretation changed between
patch revision levels.
Since our problems with dropped routes, lost packets, inability
to raise more than one channel, and inability to reset the routers
without manually resetting the ISDN lines have been going on for
nearly a year, we don't anticipate any real solutions from Ascend.
But we'd like to be sure that PATCH revisions will not break major
currently-operational features. Didn't Ascend learn anything from
their SLIP fiasco?
Mike Berger
Shouting Ground Technologies, Inc.
direwolf@shout.net
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups: