Some errors not captured in Module-Failure-Message

Adam Bishop Adam.Bishop at
Tue Jan 10 13:25:53 CET 2017

On Mon, Jan 09, 2017 at 03:34:03PM +0000, Adam Bishop wrote:
>>    Mon Jan  9 10:03:19 2017 : ERROR: (165330) eap: ERROR: Malformed EAP Message: Malformed EAP packet.  Length in packet header does not match actual length
> This should already set Module-Failure-Message?

It doesn't - I started looking at this one and can't figure out why nothing was logged for it. It seems to do the right thing (RERROR) but the corresponding linelog entry doesn't contain the message.

If anyone has a RADIUS packet with a malformed EAP message laying around (comments indicate the eap message is too short) I'll grab a full debug and backtrace.

>> I can correlate the entries by time manually, but this makes
>> things rather tedious; is there any way I can capture these in
>> using linelog?
> Does this work (for these errors, at least)?

I'll spin a build with this included and let you know, thanks. I don't envisage any problems.


Adam Bishop
Senior Infrastructure and Systems and Architect

  gpg: E75B 1F92 6407 DFDF 9F1C  BF10 C993 2504 6609 D460
    t: +44 (0)1235 822 245
 xmpp: adamb at

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.  

More information about the Freeradius-Users mailing list