1 Reply Latest reply on May 11, 2014 7:25 PM by nikvh

    Net_Dut dhcp client issue

      Hi,

       

      Net_Dut dhcp client in the SDK3.0.0 or later could not get the IP address from some APs, such as Mercury MW300R.

      If i used static IP address for testing when using SDK3.0.0, the ping worked fine.

      And i captured the wireless packets with Omnipeek, and found the DUT had connected to the AP, but could not get the IP address.

      When i use SDK2.4.0 and tested with same AP with same setting, DHCP client worked fine, it could get the ip address.

       

      --------------------------------------- SDK2.4.0  DHCP client work fine---------------------------------------

      SDK2.4.0, run snip.apsta, DHCP client work fine.
      Platform BCM943362WCD4 initialised
      Started ThreadX v5.5
      Initialising NetX v5.6
      Creating Packet pools
      Starting Wiced v2.4.0
      WWD SDIO interface initialised
      WLAN MAC Address : 40:2C:F4:AF:30:89
      ------NetX_Duo wiced_network_up
      Joining : test_wiced
      Successfully joined : test_wiced
      Obtaining IPv4 address via DHCP
      Setting IPv6 link-local address---2.4.0
      IPv4 network ready IP: 192.168.1.110
      Pinging 192.168.1.1 every 1000ms with a 900ms timeout.
      ------NetX_Duo wiced_network_up
      Setting IPv6 link-local address---2.4.0
      IPv4 network ready IP: 192.168.0.1
      Ping timeout
      Ping Reply : 6 ms
      Ping Reply : 1 ms
      Ping Reply : 0 ms
      Ping Reply : 5 ms
      Ping Reply : 18 ms
      --------------------------------------- WICED v3.0.0 DHCP client issue ---------------------------------------

      Starting WICED v3.0.0
      Platform BCM943362WCD4 initialised
      Started ThreadX v5.6
      Initialising NetX v5.7_sp1
      Creating Packet pools
      WWD SDIO interface initialised
      WLAN MAC Address : 40:2C:F4:AF:30:89
      WLAN Firmware    : wl0: Feb 10 2014 11:29:55 version 5.90.230.7 FWID 01-555f783e
      ------NeX_Duo wiced_network_up
      Joining : test_wiced
      Successfully joined : test_wiced
      Obtaining IPv4 address via DHCP
      Setting IPv6 link-local address----
      nx_ip_status_check failed
      Pinging 0.0.0.0 every 1000ms with a 900ms timeout.
      ------NeX_Duo wiced_network_up
      Setting IPv6 link-local address----
      IPv4 network ready IP: 192.168.0.1
      Ping error
      Ping error
      Ping error
      Ping error

      --------------------------------------- WICED v3.0.0 static IP work fine---------------------------------------

       

      Starting WICED v3.0.0
      Platform BCM943362WCD4 initialised
      Started ThreadX v5.6
      Initialising NetX v5.7_sp1
      Creating Packet pools
      WWD SDIO interface initialised
      WLAN MAC Address : 40:2C:F4:AF:30:89
      WLAN Firmware    : wl0: Feb 10 2014 11:29:55 version 5.90.230.7 FWID 01-555f783e
      ------NeX_Duo wiced_network_up
      Joining : test_wiced
      Successfully joined : test_wiced
      Setting IPv6 link-local address----
      IPv4 network ready IP: 192.168.1.3
      Pinging 192.168.1.1 every 1000ms with a 900ms timeout.
      ------NeX_Duo wiced_network_up
      Setting IPv6 link-local address----
      IPv4 network ready IP: 192.168.0.1
      Ping Reply : 6 ms
      Ping Reply : 0 ms
      Ping Reply : 2 ms
      Ping Reply : 0 ms

       

       

      Best regards,

      CaiX

        • 1. Re: Net_Dut dhcp client issue

          WICED SDK 3.0.x provides the latest version of ThreadX, NetX, and NetX_Duo and we have discovered that the newer NetX_Duo DHCP client increases the number of padding bytes in the DHCP packets. This is perfectly valid behaviour although as you've discovered not all access points have perfectly implemented DHCP servers and they do not process the larger, padded packets correctly.