This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3235S: Does the stock SimpleLink WiFi DHCP client track the time_server from the DHCP response?

Part Number: CC3235S

We have some equipment with the CC3235S SimpleLink WiFi 'at_commands' stock app going into some companies which do not allow NTP (time) to exit their corp firewall. They say that we should be using the standard 'time_server' value returned by their DHCP servers (is option 4 from RFC2132). The stock AT+NetCfgGet only seems to track/save the DHCP responses for IP, subnet, gateway, and DNS.

Is there any way to see DHCP options which were returned by DHCP servers, but possibly not processed?

Has anyone else had to deal with this? I can't believe this doesn't come up for other suppliers.

We DO use a simple NTP client, but our normal pool.ntp.org queries are blocked. We are hoping not to have to manually reconfigure an inhouse time_server address for each of these customers (and they do all seem a bit annoyed that we'd need to! :-} ) 

  • Hi,

    NWP DHCP client does not have integrated feature to obtain NTP server address by DHCP option 42. If you need this you should bypass internal DHCP client by your own DHCP client code. Depending on requiems it may to be needed bypass internal TCP/IP stack as well.

    btw... option 4 is not correct option. For NTP it is DHCP option 42.

    Jan

  • Sure, that's what I suspected. There's lots of DHCP client code out there. Just a little disappointing. I do see they have SNTP code in the package.

    Our customers are large hospitals, who are very paranoid about any DOS exposure - for example, since our products use TLS with various certs, time being too far out of whack prevents even opening sockets.