Abhishek, Then why provide an option for ROUTING=OFF in the first place?
Pat From: ABHISHEK PANDEY [mailto:[email protected]] Sent: Tuesday, September 22, 2015 1:24 AM To: Agrawal, Sachin; Lankswert, Patrick; Schulhof, Gabriel Cc: iotivity-dev at lists.iotivity.org Subject: Re: Re: [dev] Discovery mechanism broken Hi Pat, Sachin Discovery issue was fixed by following commit from Vimala : https://gerrit.iotivity.org/gerrit/#/c/2863/ Regarding, disabling routing manager by default, I would like to clarify that only ROUTING=EP (Endpoint) is enabled by default. This was discussed in JIRA issue for routing manager (https://jira.iotivity.org/browse/IOT-565). >> Thiago's Comment : >> Do I understand correctly that if a routing manager is present on the >> network, a device built with ROUTING=OFF will not be able to reach all >> devices on the network? If so, please remove the ROUTING=OFF option. All >> devices should be support being routed. -- Thanks and Regards, Abhishek Pandey. ------- Original Message ------- Sender : Agrawal, Sachin<sachin.agrawal at intel.com<mailto:sachin.agrawal at intel.com>> Date : Sep 22, 2015 03:40 (GMT+05:30) Title : Re: [dev] Discovery mechanism broken Hi Pat, If we consider it as an optional feature, then it should not be enabled by default. Thanks Sachin From: Lankswert, Patrick Sent: Monday, September 21, 2015 2:58 PM To: Agrawal, Sachin; Schulhof, Gabriel Cc: markus.jung at samsung.com<mailto:markus.jung at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Discovery mechanism broken Sachin, It looks like we should disable routing manager as the default. Pat From: Agrawal, Sachin Sent: Monday, September 21, 2015 5:50 PM To: Schulhof, Gabriel Cc: Lankswert, Patrick; markus.jung at samsung.com<mailto:markus.jung at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Discovery mechanism broken Hi Gabriel, A new feature ?routing manager? has been added in master recently which is enabled by default. This feature modifies the definition of OCDevAddr data structure and includes a variable ?routeData? in OCDevAddr. When you compile client and server samples, you are compiling them without that flag and therefore there is a mis-match in the definition of OCDevAddr between your sample and the liboctbstack. If you compile your sample with ?DROUTING_EP, you should see normal results and discovery should work fine. Thanks Sachin From: Schulhof, Gabriel [mailto:[email protected]] Sent: Monday, September 21, 2015 12:36 PM To: Agrawal, Sachin Cc: Lankswert, Patrick; markus.jung at samsung.com<mailto:markus.jung at samsung.com>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Discovery mechanism broken Hey! In 1.0.0-RC1 the payload seems to be null, rather than a security payload. https://gist.github.com/gabrielschulhof/dcb4597683da1f000fc4 HTH, Gabriel [cid:image001.gif at 01D0F520.8E6A63C0] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=36652d682e3669a8aceaa78073a75bc6c2b7de0c5cff5d5e980e0125dee6fd9fd3d52e3ddee9306ded04226648eb720dce7100ee954f3d131b20909a04efd4d2748cfe1d4e847419cf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150922/3c3e745a/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/20150922/3c3e745a/attachment.gif>
