The constructor initializes member attributes using parameters passed to it. abs_eap_am_tools_c.

The destructor of the eap_core class does nothing special.

This function cancels timeout for received EAP-Failure.

Re-transmission is used to test protocols. This function cancels retransmissions.

This function cancels timeout for a session.

Add configuration of accepted EAP-types. }

This function creates EAP-Response/Identity.

The adaptation module calls the eap_acknowledge() function after any Network Protocol packet is received. This is used as a success indication. This is described in RFC 2284 "PPP Extensible Authentication Protocol (EAP)". Mostly there is only one session in the client. The server does not need eap_acknowledge() function because server (EAP-authenticator) sends the EAP-success message.

Gets flag whether this session is marked removed. Session is removed later if it is not reused.

The get_partner() function returns pointer to partner class.

This function handles EAP-Request/Identity.

Prevents all notifications.

Re-transmission is used to test protocols. This function inits retransmission of sent packet.

This function cancels previous session timeout and initializes new timeout for the session.

The load_type() function function indicates the lower level to load new module including EAP-type. The type parameter is the requested EAP-type.

eap_core_map_c class increases reference count each time reference to stored object is get. Here is always just one state for one session so no references are used.

eap_core_map_c class increases reference count each time reference to stored object is get. Here is always just one state for one session so no references are used.

2003-10-01 draft-ietf-eap-rfc2284bis-06.txt chapter 2.1 Support for sequences: An EAP conversation MAY utilize a sequence of methods. A common example of this is an Identity request followed by a single EAP authentication method such as an MD5-Challenge. However the peer and authenticator MUST utilize only one authentication method (Type 4 or greater) within an EAP conversation, after which the authenticator MUST send a Success or Failure packet. Once a peer has sent a Response of the same Type as the initial Request, an authenticator MUST NOT send a Request of a different Type prior to completion of the final round of a given method (with the exception of a Notification-Request) and MUST NOT send a Request for an additional method of any Type after completion of the initial authentication method; a peer receiving such Requests MUST treat them as invalid, and silently discard them. As a result, Identity Requery is not supported. A peer MUST NOT send a Nak (legacy or expanded) in reply to a Request, after an initial non-Nak Response has been sent. Since spoofed EAP Request packets may be sent by an attacker, an authenticator receiving an unexpected Nak SHOULD discard it and log the event. Multiple authentication methods within an EAP conversation are not supported due to their vulnerability to man-in-the-middle attacks (see Section 7.4) and incompatibility with existing implementations. }

This function processes EAP-packet with known EAP-type.

Re-transmission is used to test protocols. This function resends the packet.

This function must reset the state of object to same as state was after the configure() function call. If object reset succeeds this function must return eap_status_ok. If object reset fails this function must return corresponding error status.

This function calls reset() for one eap_base_type_c object.

This function sends EAP-Response/Identity.

The EAP Core calls the send_eap_nak_response() function when EAP-authentication with requested EAP type is not possible.

This function sends EAP-Response/Notification.

This function initializes timeout for received EAP-Failure.

Marks this session removed. Session is removed later if it is not reused.

The set_partner() function sets pointer to partner class.

This function calls shutdown() for one eap_base_type_c object.

Marks this session not removed. Session is not removed it is reused.

This stores the current EAP-type. When requested, we send our ID using our default EAP-type. This is our best quess of other peer's EAP-type. Other peer will sent the real EAP-type later and we can NAK it then and send our own EAP-type. This is due the limitations of EAP-protocol.

This is the queried EAP-identity. This is saved because other EAP-types may be load afterwards and they may query EAP-identity.

Latest received EAP-identifier. Used only for EAP-Request/Identity handling in client. Ensures that the EAP-Response/Identity is sent with the latest EAP-identifier.

This flag prevents server receiving of multiple EAP-Response/Identity message. This is set true after the server accepts EAP-Response/Identity message.

Server received EAP-Response from client. Server must not sent any other EAP-type. Server could send EAP-Failure or EAP-Success. Client sent a response. Client must not accept any other EAP-type.

This indicates whether this object is client (true) or server (false). In terms of EAP-protocol whether this network entity is EAP-supplicant (true) or EAP-authenticator (false).

This indicates whether the authentication role of this object is client (true) or server (false). In terms of EAP-protocol whether this network entitys authentication role is EAP-supplicant (true) or EAP-authenticator (false). NOTE the LEAP type changes authentication role during the authentication session.

Tells whether this is tunneled EAP-session. For example inside PEAP or TTLS tunnel. This causes some changes to timeouts.

This flag indicates that this object is marked to removed asynchronously. The very same object could be taken use before the removing timer elapses.

This is back pointer to object which created this object. Packets are sent to the partner.

Re-transmission is used to test protocols. This stores the information to resent a message. This is used for testing purposes.

Re-transmission is used to test protocols. This is the maximum count of retransmission of one message. This is used for testing purposes.

Re-transmission is used to test protocols. This is the time after resent a message. This is used for testing purposes.

This is the maximum time authentication could succeed. Authentication is terminated after this time elapses. The EAP-type could change the timeout by calling set_session_timeout() function.