Hi Jaehyun,
Your update fixed the issue that dtls messages are handled in coap not in dtls.
Thanks very much.
Taehwa
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10048):
https://lists.iotivity.org/g/iotivity-dev/message/10048
Mute This Topic: h
Hello IoTivity dev!
Now I'm working on IoTivity-Lite zephyr porting.
The problem is when security option is on, DTLS handshake isn't managed
properly.
I'm building a OCF server device and if the device gets DTLS client hello, that
packet is handed over
to coap engine and when checking packet, be
Hi!
I'm trying to figure out how to use oc_storage_configuration function in Zephyr
porting.
In comment says following.
/**
It expects the device name, flash sector size and
maximum read/write size separated by comma:
device_name,flash_sector_si
Hi!
I'm trying to port IoTivity-Lite server to zephyr.
But, It seems Zephyr project updated and changed a lot compared to the time
when IoTivity-Lite port to zephyr code was written.
(The current version of Zephyr is 1.13)
In Zephyr project, no more make used but cmake. some of configuration name
6 ( https://lists.iotivity.org/g/iotivity-dev/message/9966 )
>
>
>
>
>
>
>
>
>
> Hi,
>
>
>
>
>
>
>
> Having the .octt file will help but the issue you're reporting:
>
>
>
>
>
>
>
> For Smart Home Dev
Hello, iotivity-dev!
I'm preparing OCF Certification and I'm doing it using IoTivity-Lite.
When I'm testing CT1.1.6 OCF Endpoint the problem occurs.
In CT1.1.6, before starting the test, an ACE which grants "anon-clear" access to
any Resource that has a CoAP Endpoint is added.
(It looks like fol
[Edited Message Follows]
Hello!
I'm preparing to OCF certification and testing my server using OCF Conformance
Tool(2.2.0).
I passed or got warning for almost tests but the only remaining test is the
CT1.7.8.11.
The process of the test is following(I omitted some process for convenience).
1. F
I'm preparing to OCF certification and testing my server using OCF Conformance
Tool(2.2.0).
I passed or got warning for almost tests but the only remaining test is the
CT1.7.8.11.
The process of the test is following(I omitted some process for convenience).
1. Four random UUIDs for DOXS, AMS, CM