A.L.M.Buxey@lboro.ac.uk wrote:
however, I note in the debug log, lots of these sorts of entries:
Tue Feb 12 16:25:26 2013 : Error: rlm_eap (EAP): No EAP session matching state 0x4344573643464e11
That *may* come from the changes to the EAP cache. It's supposed to track re-transmits through a different proxy path. The old code would give this error message. The new code should allow EAP to continue. But it's possible that the code gets confused.
I *believe* that this is just a fresh new incoming EAP session...
Which means there should be no State attribute at *all*.
and so therefore there would be no state that is matched...so, not really an Error at all? Have I presumed correct with this - or is it the client trying to do a fast reauth that may have been cached?
The fast re-auth re-starts EAP. Alan DeKok.