[RadiusNT] malformed packet handling between RadiusNT 2.5.206 and 2.5.209

Josh Hillman ( (no email) )
Wed, 2 Feb 2000 12:49:38 -0500

What changed with "malformed packet" handling between RadiusNT 2.5.206 and
2.5.209?
Everything works fine with 2.5.206, but as soon as I change the executable
to 2.5.209 and restart the service, I get the following (debug=18)
eventhough "AllowMalformed=1":

Enterprise features enabled.

RadiusNT 2.5.209 (Emerald Standard) Initialized...

radrecv: Request from host c72cc20a code=1, id=129, length=99
Authenticate: from Max 1 - Invalid Password Length
Request from Max 1 - Malformed Packet
Resp Time: 15 Auth: 0/0 -> 0 Acct: 0/0/0 -> 0

Here's debug info after switching back to 2.5.206 (works fine):

RadiusNT 2.5.206 (Emerald Standard) Initialized...

radrecv: Request from host c72cc20a code=1, id=130, length=103
Sending Ack of id 130 to c72cc20a (Max 1)
Resp Time: 0 Auth: 1/0 -> 1 Acct: 0/0/0 -> 0

The NASes are all Max 40xx units running TOAS 7.0.22 (the latest available
for the 40xx series).

Josh

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