> The State is OK. That's good. The EAP-Message starts off with > "0x0100", which looks like the correct EAP packet type (1), but the > wrong sequence number (0). The client SHOULD have responded with a > sequence number of 4, I think. At least, that's what the Cisco > clients do.
I'll take a look at the patch that gets submitted, but technically, the HP client is correct per the RFCs. The EAP RFC simply says that the sequence number must be "different". Only the EAP-TLS RFC states that the sequence number must be numerically sequential. > And the EAP module doesn't see a sequence number of 4, so it ignores > the request. Hmm... as per above, this may need to be looked at... Non-TLS EAP types must be able to handle non-sequential sequences while the TLS-based EAP types must be sequential to be RFC-compliant. -- --Mike ---------------------------------- Michael Griego Wireless LAN Project Manager The University of Texas at Dallas - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
