Chul Lee, There is nothing wrong with that address. It is a valid IPv6 address. The IoTivity stack has been able to handle IPv6 connections for several weeks. Last week a change was merged that makes IPv6 the preferred network. It uses a Dual Stack approach that allows both to work, but prefers IPv6. Of course, the security code will need to work with IPv6 as well. I am supporting that effort, in the form of answering any questions you have. You can force IoTivity to revert to IPv4-only. Let me know if you want to do that, but that can only be temporary. John Light Intel OTC OIC Development
From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ?? Sent: Tuesday, August 25, 2015 9:17 PM To: iotivity-dev at lists.iotivity.org Cc: ??? Subject: [dev] IP address in OCClientResponse seems invalid. Dear all, While testing security module(provisioning tool) with master branch. I performed the multicast device discovery. And then I try to extract endpoint information from OCCleintResponse such as IP address, etc. BTW, IP address in OCClientResponse seems invalid format as "fe80::52b7:c3ff:fea1:9e6a". Here is information for my test. - branch : latest master - Commit ID : "a3b45596b23319cc31826bd407adf80c7a69b12f" If anyone has information regarding this issue, please share to me. Thanks, Chul Lee. [cid:image001.gif at 01D0DFE9.5585F200] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=664566a9d0d362223fbf1ded070e709f8179503053e74b890cf2282830c3416bfcfabd80c3fe6049141ee34884fd53a813d69ea60670f66ef4bcdeced46ed5ee08cece8541bc14eacf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150826/0aec055f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150826/0aec055f/attachment.gif>
