> Have you ever tested secure transfer between >iotivity-constrained(zepyhr) and iotivity?
No, I don?t believe this has ever been tested on Zephyr. It should however be close enough to have it working, barring any needed fixes to the port, since the rest of the code is common. > 1. If the coap payload exceeds 100, the packet is broken. Because >default > CONFIG_NET_NBUF_DATA_SIZE value is small. Are you seeing this on the receive side or the send side on Zephyr? Do you happen to know the actual size of the packet that was sent? That will give us more data. Regarding NBUF_DATA_SIZE, as I understand it is supposed to be small and characteristic of typical packet sizes. > 2. Zepyhr's Ip adapter sends secure packets to udp_recv6 instead of >dtls_recv6. Good catch. Yes, that should be fixed. - Kishen Maloor Intel Open Source Technology Center From: JeongHun Kim <[email protected]> on behalf of JeongHun Kim <jhun1105.kim at samsung.com> Reply-To: "jhun1105.kim at samsung.com" <jhun1105.kim at samsung.com> Date: Wednesday, March 15, 2017 at 4:25 AM To: "Macieira, Thiago" <thiago.macieira at intel.com>, "iotivity-dev at lists.iotivity.org" <iotivity-dev at lists.iotivity.org>, Kishen Maloor <kishen.maloor at intel.com> Subject: RE: Re: [dev] IoTivity-Constrained on frdm-f64k Hi Thiago, Thank you for your kind answer. As you said, we are developing ipv4 as an option in zephyr port. Additionally i have a few question about the security implementation of iotivity-constrained. Have you ever tested secure transfer between iotivity-constrained(zepyhr) and iotivity? I found some problem in zepyhr with secure mode. 1. If the coap payload exceeds 100, the packet is broken. Because default CONFIG_NET_NBUF_DATA_SIZE value is small. 2. Zepyhr's Ip adapter sends secure packets to udp_recv6 instead of dtls_recv6. Is security for zephyr under development? Or is development done? Kind Regards, junghun kim. --------- Original Message --------- Sender : Thiago Macieira <thiago.macieira at intel.com> Date : 2017-03-08 01:34 (GMT+9) Title : Re: [dev] IoTivity-Constrained on frdm-f64k Em segunda-feira, 6 de mar?o de 2017, ?s 19:38:18 CET, Maloor, Kishen escreveu: > > I think zepyhr's DHCP config doesn't work because >IoTivity-Constrained?s > > Zephyr port have only ipv6. > > > > Yes. port/zephyr/src/ipadapter.c only supports IPv6. Feel free to > add IPv4 support if you require it, and submit a patch. It shouldn?t be > too hard; you?d have to update the ipadapter as well as the project > configuration. We may accept the patch, but I don't see the point. On a constrained device, you want to limit the amount of memory required. Since IPv6 is mandatory and sufficient, IPv4 would be overhead. You may want to use IPv4 for non-OCF needs, though I highly recommend requiring IPv6. And your constrained device should not be talking to the Internet. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center <img src='http://ext.samsung.net/mail/ext/v1/external/status/update?userid=jhun1 105.kim&do=bWFpbElEPTIwMTcwMzE1MTEyNTUyZXBjbXMxcDgyMzM1MDg0NzQ5MDk4YjY2NDky OWZiYjFjNjhkODE4ZCZyZWNpcGllbnRBZGRyZXNzPWtpc2hlbi5tYWxvb3JAaW50ZWwuY29t'
