RE: [RadiusNT] RadiusNT changes

Robert F. O'Connor ( (no email) )
Wed, 1 Dec 1999 13:43:29 -0800

Our crash-after-stop-record problem (see the thread "Radius .175 crashing
*after* accounting record") continues to occur with .206. Do you need us to
reforward -X15 output, etc. again to re-evaluate this?

-Robert F. O'Connor
System Administrator, Metro.Net
sysadmin@metro.net

> -----Original Message-----
> From: radiusnt-request@iea-software.com
> [mailto:radiusnt-request@iea-software.com]On Behalf Of Dale E. Reed Jr.
> Sent: Tuesday, November 30, 1999 1:18 PM
> To: radiusnt@iea-software.com
> Subject: Re: [RadiusNT] RadiusNT changes
>
>
> Josh Hillman wrote:
> >
> > What changed between RadiusNT 2.5.205 and .206?
> > I don't even know what changed between .175 and .205, but I'm just happy
> > SNMP concurrency checking is working correctly now (I think) in .205.
>
> It fixed the rv ODBC error.
>
> Differences between 175 and 206 include:
>
> * Fixes to several SNMP pieces
>
> * USR Connect-Speed attribute mapping to Connect-Info
>
> * Domain Trim name feature (trimnames=2 or 3)
>
> * Massive Output cleanup (try -x18 for a clean log view)
>
> * Lots of small bug fixes. :)
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> IEA Software, Inc. www.iea-software.com
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
>

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart