I have an Intel Edison and a Dell 3290 gateway (WRLinux) and I'm finding that platform and device discovery seem to work, resource discovery often does not, and CRUDN ops on a particular resource never work.
This is running server code on the Edison and client code on the gateway. I've tried my code, and I've used the sample code, and nothing works consistently. On the other hand running client code on an Ubuntu VM seems to talk to a server on the Edison ok. Mostly. Without going into details I suspect the problem is network config. For example, if I use CT_DEFAULT in my client discovery calls I get nothing. If I go with CT_IP_USE_V4 the discovery calls work but not get/put/post on a resource. CT_IP_USE_V6 does not work for anything (which probably makes sense, see below). The Edison defaults to IPv4 on wlan0. Shouldn't that work? I finally figured out how to make it use IPv6, but naturally cannot find a way to make it go back to V4, or to run a dual stack. To complicate things, the gateway is connected by ethernet wire to my wireless router, which is connected to my cable modem. So my devhost and my Edison can connect wirelessly to the gateway, or to the router. So there's a whole bunch of networking going on and I'm a long way from being a network expert. For my purposes IPv4 is just fine, but obviously I need CRUDN ops to work. Does the code for resource.get etc. somehow assume IPv6? Any advice welcome. I bet the farm on Iotivity for the Intel Ultimate Coder Challenge, and I was *so* close (how does remote realtime interactive programming of IoT widgets <https://simplecore.intel.com/ultimatecoder/developing-gateway-part-ii-programming-iotivity/> grab you?), but if I can't get these things to communicate by Friday I'm going to lose that bet. -Gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160712/2dbe3c71/attachment.html>
