On Linux, the WCM relies on the following libraries that are linked directly into the WCM:
|Function||Libraries we have integrated with||Notes|
|SSL library||libssl||Version must be >= 1.0.2h. (Earlier versions do not support the public certificate that the Cirrent cloud uses.)|
|HTTP client library||libcurl|
|HTTP server||microhttpd||Only used for SoftAP, ZipKey AP|
On Linux, the WCM uses the following processes:
|Function||Processes we have integrated with||Notes|
|Interface to Wi-Fi radio||wpa_supplicant|
|Wireless access point||hostapd||Only used for SoftAP, ZipKey AP|
|DNS||dnsmasq||Only used for SoftAP, ZipKey AP|
|DHCP server||dnsmasq||Only used for SoftAP, ZipKey AP|
You will want to verify that your platform has all of these components installed before trying to install the WCM. To do this, just run the compatibility checker as described here.
The WCM will take care of starting/stopping these processes as necessary, so you should not run any of these processes independently. If they are in other start-up scripts, they should be removed from those scripts to avoid conflicting with the WCM.
If your product uses dhclient or udhcpd (or any other DNS/DHCP server) you should remove these from any startup scripts also, as they will conflict with the processes that the WCM uses (udhcpc, dnsmasq).
HTTP Server co-existence
If your product uses WCM's softAP implementation for local onboarding (when not in range of a ZipKey network), the WCM will take care of bringing up an HTTP server while softAP is up. You should not run your own HTTP server during this time as it may conflict. When the WCM notifies you that the product is on the private network, the WCM will bring down its HTTP server and you can bring up your HTTP server.