The constructor of the eap_buf_chain_wr class initializes attributes using the parameters passes to it. NOTE the buffer allocated from the stack or from the heap must allocate additional bytes for memory guards. The EAP_MEM_GUARDS(size) macro increases the size with count of memory guard bytes. The example use of eap_buf_chain_wr is as follows. NOTE all sanity checks are ignored in the example.

         u8_t packet_buffer[EAP_MEM_GUARDS(EAP_MAX_LOCAL_PACKET_BUFFER_LENGTH)];
 eap_buf_chain_wr_c response_packet(
     eap_write_buffer, m_am_tools, packet_buffer,
     sizeof(packet_buffer), true, false, EAP_MEM_GUARD_LENGTH);
 const u32_t eap_header_offset = get_type_partner()->get_header_offset(
     &MTU, &trailer_length);
 eap_header_wr_c * const eap_response = (eap_header_wr_c * const)
     response_packet.get_data_offset(eap_header_offset,
         (EAP_MAX_LOCAL_PACKET_BUFFER_LENGTH
         -(eap_header_offset+ trailer_length)));
        

The constructor of the eap_buf_chain_wr class initializes attributes using the parameters passes to it. The example use of eap_buf_chain_wr is as follows. NOTE all sanity checks are ignored in the example.

         u8_t packet_buffer[EAP_MEM_GUARDS(EAP_MAX_LOCAL_PACKET_BUFFER_LENGTH)];
 eap_buf_chain_rd_c response_packet(
     eap_read_buffer, m_am_tools, packet_buffer,
     sizeof(packet_buffer), false);
 const u32_t eap_header_offset = get_type_partner()->get_header_offset(
     &MTU, &trailer_length);
 eap_header_rd_c * const eap_response = (eap_header_rd_c * const)
     response_packet.get_data_offset(eap_header_offset,
         (EAP_MAX_LOCAL_PACKET_BUFFER_LENGTH
         -(eap_header_offset+ trailer_length)));
        

The constructor of the eap_buf_chain_wr class initializes attributes using the parameters passes to it. New buffer is allocated from heap. The example use of eap_buf_chain_wr is as follows. NOTE all sanity checks are ignored in the example.

         eap_buf_chain_rd_c response_packet(
     eap_write_buffer_e, m_am_tools,
     PACKET_BUFFER_LENGTH);
 const u32_t eap_header_offset = get_type_partner()->get_header_offset(
     &MTU, &trailer_length);
 eap_header_rd_c * const eap_response = (eap_header_rd_c * const)
     response_packet.get_data_offset(eap_header_offset,
         (PACKET_BUFFER_LENGTH
         -(eap_header_offset+ trailer_length)));
        

The destructor of the eap_buf_chain_base_c class checks memory guards and frees the allocated buffer.

The add_data() function adds data to the end of the buffer. If the buffer is empty the data is added to begin of the buffer.

The add_data() function adds data to the end of the buffer. If the buffer is empty the data is added to begin of the buffer.

The add_data_to_offset() function adds data to the offset of the buffer.

The add_data() function adds data to the offset of the buffer.

Function checks the memory guard bytes.

Function checks the all memory guard bytes.

Forses the inheritance.

The get_buffer_length() function returns the length of buffer in bytes.

The get_data() function function returns pointer to the data. NOTE user of the eap_buf_chain_wr class must obtain the pointer to the data using this or the get_data_offset() function. These functions can handle the memory guard.

The get_data_length() function returns count of data bytes in the buffer.

The get_data_offset() function returns pointer to the data in offset (p_offset). NOTE user of the eap_buf_chain_wr class must obtain the pointer to the data using this or the get_data() function. These functions can handle the memory guard.

This is used in testing.

The set_do_packet_retransmission() function gets the re-transmission flag of this packet.

This gets whether this packet must be encrypted (true) or not (false). Encryption means the WLAN data encryption on the air (WEP, TKIP or CCMP). Using this flag to tell the encryption allows the configuration of the temporal key beforehand the key is used. This is optimization to fasten the key configuration.

This gets whether the sender is client or server. This is used in testing.

The get_is_manipulated() function returns flag to indicate this packet is manipulated. This is used for testing purposes.

The get_is_valid() function returns the status of the object.

The get_is_valid() function returns the status of the data included in object.

The get_random_error_type() function returns the type of manipulation of the packet. This is used for testing purposes.

This function returns the index of sent packet. This is used for testing purposes.

This gets the pointer of sender stack. This is used in testing.

This function initializes the eap_buf_chain_base_c object.

Function zeroes the data buffer.

The set_buffer_length() function allocates the buffer of length bytes.

The set_data_length() function set the data length in the buffer.

This is used in testing.

The set_do_packet_retransmission() function sets the re-transmission flag of this packet. Packet will be re-transmitted by lower layer when do_packet_retransmission_when_true is true. Packet will not re-transmitted by lower layer when do_packet_retransmission_when_true is false.

This sets whether this packet must be encrypted (true) or not (false). Encryption means the WLAN data encryption on the air (WEP, TKIP or CCMP). Using this flag to tell the encryption allows the configuration of the temporal key beforehand the key is used. This is optimization to fasten the key configuration.

This sets whether the sender is client or server. This is used in testing.

The set_is_manipulated() function sets flag to indicate this packet is manipulated. This is used for testing purposes.

Function sets the memory guard bytes.

The set_random_error_type() function sets the type of manipulation of the packet. This is used for testing purposes.

This function sets the index of sent packet. This is used for testing purposes.

This sets the pointer of sender stack. This is used in testing.

This is pointer to data of eap_buf_chain_base_c . This decreases memory print of eap_buf_chain_base_c . This decreases stack usage of EAP_Core.