Re: Mal-Formed Packet

David Moore ( (no email) )
Tue, 5 May 1998 07:14:56 +1000

I am not sure on this point either, we have USR TC and we are getting
authentication and accounting I have not setup anything in the registry. Am
I missing or going to miss some records?. We have Emerald 2.2.38 I am not
yet using Radius 2.5

David Moore

-----Original Message-----
From: Dale E. Reed Jr. <>
To: <>
Date: Tuesday, May 05, 1998 3:48 PM
Subject: Re: Mal-Formed Packet

>Michael Whisenant wrote:
>> If you are referring to the output on the debug screen, then you must
>> USRobotics equipment. USRobotics does not fully comply with the RADIUS
>> protocol. You will need to use regedit and all a registry key to allow
>> accounting packets to be entered correctly. You can get the details from
>> the ftp site and read the readme file. But for reference in regedit
>> HKEY_Local_Machine\Software\IEA\RadiusNT Add a value AllowMalformed = 1.
>> This will correct the reported error.
>Because of the abundance of non-RFC compliant RADIUS clients sending
>attributes with a length of two (which is what the above registry lets
>"slide" if you set it) RadiusNT 2.5.105 and higher now default to
>allowing an Attribute length of two. You can set the above registry
>setting to 0 if you don't want to allow them.
>Dale E. Reed Jr. (
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today |
> ----------------------------------------------------------
> RadiusNT Mailing List