RADIUS authentication might fail with Fireware v12.11.1 when the Firebox is in FIPS mode

A Firebox with FIPS mode enabled might experience issues authenticating to a RADIUS server after the device is upgraded to Fireware v12.11.1.

You might see log entries similar to these messages from the admd (authentication) process in Traffic Monitor:

admd RADIUS:Failed to generate HMAC hash for request  Debug
admd admDoAuthentication: failed to send access-request to radius server  Debug


Problemumgehung/Lösung:

This issue will be resolved in a future update.

To workaround this issue:

• Downgrade to Fireware v12.11
  or
• Disable FIPS mode

If your Firebox does not support FIPS mode in Fireware v12.11 and higher, WatchGuard recommends you disable FIPS mode. FIPS 140-3 is supported in Fireware v12.11 and higher with these hardware models:

• Firebox T series: T20, T20-W, T40, T40-W, T80, NV5, T25, T25-W, T45, T45-PoE, T45-W-PoE, T45-CW, T85-PoE
• Firebox M series: M290, M390, M590, M690, M4800, M5800

For instructions on how to disable FIPS mode, and information on support devices, go to FIPS Support in Fireware.