Hi Gabriel, thanks for reporting the issue you saw. I do know that several of the Microsoft devs that were working on Security features earlier this year definitely had things working under Windows, up to and including secure Resource discovery, onboarding and provisioning, etc., so I think it should work. OSX is another story and I can't speak to that.
I'm not set up for Windows or OSX development (and don't have bandwidth right now to debug this issue anyway) but I think it's almost always helpful to capture and attach the log files from the Client and Server apps when filing a bug. It might reveal something like a failed DTLS handshake or similar issue, which would be a good clue as to where to look. If you can, capture the IoTivity logging output from your Linux (successful) run, and the Windows (failed) run, and attach them to the JIRA ticket. I can't guarantee someone will look at it right away but it'll definitely make it more likely! Thanks, Nathan -----Original Message----- From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Schulhof, Gabriel Sent: Tuesday, October 10, 2017 12:42 PM To: iotivity-dev <iotivity-dev@lists.iotivity.org> Subject: Re: [dev] Talking to a coaps endpoint Hey, all! I have been able to issue requests over coaps on Linux now. Nevertheless, the exact same setup fails on Windows and OSX. I have filed https://jira.iotivity.org/browse/IOT-2705 to that effect, but there has been no reaction so far. Are there any plans to make coaps work on Windows? Has it worked for anyone? What about OSX? Please let me know, and TIA for any information, Gabriel On Thu, Sep 7, 2017 at 10:01 AM, Schulhof, Gabriel <gabriel.schul...@intel.com> wrote: > Hey, all! > > I'm trying to figure out what is needed to talk over coaps. > > I have built iotivity with SECURED=1 RD_MODE=all EXC_PROV_SUPPORT=1. > > I have created a client/server pair in C such that the client performs > a GET request to the server. > > The client directs its request by constructing an absolute URL from > the OCEndpointPayload sent by the server, thus > coap://<address>:<port><resource_path>. This works. > > However, when I try to direct a request at the coaps endpoint > advertised by the server, it hangs and I get OC_STACK_GATEWAY_TIMEOUT. > > The client/server pair can be seen at [0] and downloaded from [1]. > > To build, please edit in the Makefile the value of IOTIVITY_PREFIX to > point to the iotivity repo root on your system and the value of > BIN_PATH to point to out/<platform>/<arch>/<debug|release> as you have > built it. Please build your iotivity with the scons flags I show > above! > > The build also makes use of glib for asynchronicity, so please install > your glib development package if you don't yet have it! > > Please let me know what else I need to do to get requests over coaps to work! > > TIA for your help, > > > > Gabriel > > [0] > https://gist.github.com/gabrielschulhof/517b3518353e95a45b08eb21d43158 > 40 [1] > https://gist.github.com/gabrielschulhof/517b3518353e95a45b08eb21d43158 > 40/archive/9cdc05b0da4715983155c0a9155038a3e41fdb50.tar.gz _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
