Setting AllowMalformed=3 worked.
I remember the issues with Ascend and the malformed packets, which is why
the option was checked (=1) in the RadiusNT Admin.
RadiusNT Admin 2.5.267 only has one option for it though: checked or
unchecked (1 or 0), so anytime RadiusNT options are saved, "AllowMalformed"
gets reset back to 1 instead of 3. Is there a newer admin that accomodates
3.5.263 had the same problem, but with TrimName--this was fixed in 2.5.267
when two other options were added to the admin.
> Josh Hillman wrote:
> > What changed with "malformed packet" handling between RadiusNT 2.5.206
> > 2.5.209?
> > Everything works fine with 2.5.206, but as soon as I change the
> > to 2.5.209 and restart the service, I get the following (debug=18)
> > eventhough "AllowMalformed=1":
For more information about this list (including removal) go to: