Recording Module-Failure-Message when using PEAP

[Alan DeKok]

Adam Bishop wrote:
> It seems the extra Access-Challenge -> Access Request before the reject is sent when using PEAP is wiping the state clean(?), so I’m unsure how to persist attributes so they can be logged in post auth.

  See the "cache" module.  You can cache attributes, and later read them
out of the cache.

> Is this unintentional behaviour, or is my config wrong?

  It's just the way the server works.  The only way to track information
between packets is via a DB, or the cache module.

> Also, there seems to be some memory corruption loading the "server" block in the debug output: "server { # from file p.�{�".

  That was fixed a while ago.

  Alan DeKok.