• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 39 subscribers
  • Views 920 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Supported DHCP options for CC3100

Brian Costabile1
Prodigy 100 points
Other Parts Discussed in Thread: CC3100

I'm assuming that the DHCP domain-search option is not supported because I have to send fully-qualified-domain-names into the sl_NetAppDnsGetHostByName function. Is that true? Is support of this option on the roadmap?

Typical things that the host processor would want to be able to display to users: host-name, domain-name, domain-name-servers, domain-search. I had a previous post asking about domain-name-servers and I understand the host processor is only allowed access to the primary. What about the other DHCP parameters? Any plans on supporting access to these other options?

  • 0
    TI__Mastermind 18455 points

    Hi Brian,

    Yes, you need to provide full domain name.
    Currently we are not looking into changing that.

    We don't have any plans on providing other DHCP parameters, has all of them are relevant only to the DHCP client which is inside the CC3100.
    Can you please comment on what is the use for these parameters from your point of view?

    Thanks,
    Alon

  • 0 in reply to Alon Srednizki
    Prodigy 100 points
    Hi Alon, Thanks for your response.

    My company has a product where we deploy thousands of wireless devices in a hospital with a local server acting as a gateway to the cloud. Our existing Linux based WiFi device takes the domain name from the DHCP response and uses that to create the local server's fully qualified domain name (FQDN) to do a DNS lookup. In Linux we have access to all of the parameters from the DHCP negotiation. We use the NTP server name that the hospital provides to do time synchronization to internal NTP servers and we use the DNS Server List and Domain Search List just to display to anyone maintaining the devices. Some hospitals require static network configurations so we need to support manual input of all those things (NTP servers, Domain Name Servers, Domain Search List, Etc.). In Linux, this is also no problem.

    With the CC3XXX, I'm not able to do a complete static configuration so our new device won't work for some of our customers. Most customers use DHCP, so it's not a deal-stopper. Not being able to do the auto-server-discovery is also not a deal-stopper, but it means the new devices will be more expensive to deploy because our technicians will need to configure each device with the FQDN of our server.

    I was hoping others might chime in with similar requests so these could be considered for future releases.

    Thanks again,
    -Brian
  • 0 in reply to Brian Costabile1
    TI__Mastermind 18455 points

    Hi Brian,

    Thanks for the elaborate response.

    The ability to set the domain name is actually a secured roadmap item for us.
    Unfortunately, I can't provide more details, specifically, a schedule for it quite yet.

    Please try to follow our future announcements for more information.

    Thanks,
    Alon