I have two CC3200 Launchpad eval boards, running stock firmware. It looks like mDNS service name collision is not implemented on these boards per the api documentation (see below). When I run the iOS WiFi starter app, run Smart Config, provide a device name, both of the boards are provisioned with that device name, but only one comes back in discovery. I'm not an mDNS expert. Can someone explain what is going on here? Is this a bug? Seems like this should be a valid use case and mDNS should handle this.
========================
13.5.3 API – Register Service
Description: This API registers a service and advertises it if mDNS is started and the device has an IP address (STA) or up (P2P or AP). The service is kept in the mDNS database; only one registration is needed. This registered service is offered by the application.
The service name should be the full-service name according to DNS-SD RFC, meaning the value in the name field of the SRV answer.
Example of a service name:
• PC1._ipp._tcp.local
• PC2_server._ftp._tcp.local
If the service is unique (see the Options parameter in Table 13-5), mDNS probes the service name to ensure its uniqueness before starting to announce the service on the network. If it is not unique, a number will be added to identify it.
Return
= 0 – Success
<0 – A kind of error
API name
int sl_NetAppMDNSRegisterService( const char*
Parameters:
pServiceName, ServiceNameLen,
unsigned char const char* unsigned char unsigned short Port, unsigned long TTL, unsigned long Options);
========================
-Mark