The latest Ascend dictionary is at:
I had to add a whole slew of entries into our db that were missing
(Ascend-specific ones for the most part).
> -----Original Message-----
> From: Dale E. Reed Jr. <email@example.com>
> To: firstname.lastname@example.org <email@example.com>
> Date: Wednesday, 22 September 1999 12:46
> Subject: Re: [Emerald] Radius and Ascend TNT
> >Network Operation Centre wrote:
> >> Hi,
> >> We currently use emerald and radiusnt with Livingston PM's and Cisco's
> >> it all works fine. We have just added an Ascend TNT to our list of Term
> >> Servers and this is the error radius reports when the TNT tried to auth
> >> user
> >> Wed Sep 22 10:19:19 1999: Request from max1.adl.world-link.com.a -
> >> Packet
> >> Wed Sep 22 10:20:52 1999: Request from max1.adl.world-link.com.a -
> >> Packet
> >> But when we try with merit radius on a Linux machine it seems to work
> >> perfect.
> >> Can anyone help
> >Check Allow malformed in the RadiusNT admin and restart RadiusNT. If
> >start RadiusNT in "-x15 -X" mode and send me the binary debug dump from
> >the TNT, I'll show you why its a "malformed" packet. Most vendors are
> >leniant towards this, but we try to adhere to the RFC by default.
> >Nothing against Merit (because of their roots, before the RFC was
> >they are one of the more RFC-loose servers out there.
> >Dale E. Reed Jr. Emerald and RadiusNT
> >IEA Software, Inc. www.iea-software.com
> >For more information about this list (including removal) go to:
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: