2 Replies Latest reply on Oct 5, 2018 6:03 AM by AxLi_1746341

    EAP-TLS issue: join_ent failed after leave_ent

    AxLi_1746341

      Hi  GauravS_31

       

      After apply the patch from below link

      https://community.cypress.com/thread/35745

      I have chance to get EAP-TLS work.

      But I found the join_ent fails after leave_ent.

      It seems not reliable...

      Can you check the issue?

       

      With FreeRTOS build:

      > join_ent LAB-WPA2-ENT eap_tls bob hello eap mschapv2 wpa2

      Joining : LAB-WPA2-ENT

      Successfully joined : LAB-WPA2-ENT

      Obtaining IPv4 address via DHCP

      IPv4 Network ready IP: 192.168.1.111

      Successfully retrieved the session information 0

      > leave_ent

      leave test: ok

      > join_ent LAB-WPA2-ENT eap_tls bob hello eap mschapv2 wpa2

      Joining : LAB-WPA2-ENT

      Failed to join : LAB-WPA2-ENT

      Joining : LAB-WPA2-ENT

      Failed to join : LAB-WPA2-ENT

      Joining : LAB-WPA2-ENT

      Failed to join : LAB-WPA2-ENT

      Join result 1055:

      failed

        ! mbedtls_ssl_handshake returned -0x2

      Error setting supplicant event handler 2

      >

       

      With ThreadX/NetX_Duo build:

      > join_ent LAB-WPA2-ENT eap_tls bob hello eap mschapv2 wpa2

      Joining : LAB-WPA2-ENT

      Successfully joined : LAB-WPA2-ENT

      Obtaining IPv4 address via DHCP

      DHCP CLIENT hostname WICED IP

      IPv4 network ready IP: 192.168.1.111

      Setting IPv6 link-local address

      IPv6 network ready IP: FE80:0000:0000:0000:462C:05FF:FE80:65FC

      Successfully retrieved the session information 0

      > leave_ent

      leave test: ok

      > join_ent LAB-WPA2-ENT eap_tls bob hello eap mschapv2 wpa2

      Joining : LAB-WPA2-ENT

      Successfully joined : LAB-WPA2-ENT

      Obtaining IPv4 address via DHCP

      DHCP CLIENT hostname WICED IP

      IPv4 network ready IP: 192.168.1.111

      Setting IPv6 link-local address

      IPv6 network ready IP: FE80:0000:0000:0000:462C:05FF:FE80:65FC

      Successfully retrieved the session information 0

      > leave_ent

      leave test: ok

      > join_ent LAB-WPA2-ENT eap_tls bob hello eap mschapv2 wpa2

      Joining : LAB-WPA2-ENT

      Failed to join : LAB-WPA2-ENT

      Joining : LAB-WPA2-ENT

      Failed to join : LAB-WPA2-ENT

      Joining : LAB-WPA2-ENT

      Failed to join : LAB-WPA2-ENT

      Join result 1007:

      failed

        ! mbedtls_ssl_handshake returned -0x2

      >

        • 1. Re: EAP-TLS issue: join_ent failed after leave_ent
          GauravS_31

          There seems to be an imbalance in memory allocation and deallocation after each join_ent and leave_ent. The net total allocated space would increase after each join_ent-leave_ent. It probably could cause a memory leak which means that even join is not expected to work after the error. We will check further to find the issue.

          • 2. Re: EAP-TLS issue: join_ent failed after leave_ent
            AxLi_1746341

            grsr wrote:

             

            There seems to be an imbalance in memory allocation and deallocation after each join_ent and leave_ent. The net total

            If this statement is true, it means memory leak.

            However, I feel it's not related to memory leak...

            It looks like if join_ent fails it will not work any more until reboot the device.

             

            Maybe you can write a simple test code to repeat testing

            join_ent && join_leave to ensure it is stable for use.