Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
.gitignore | D | 12-May-2024 | 111 | 8 | 7 | |
Makefile | D | 12-May-2024 | 419 | 16 | 11 | |
Makefile.contiki | D | 12-May-2024 | 904 | 34 | 18 | |
README | D | 12-May-2024 | 961 | 31 | 21 | |
coap-observer.c | D | 12-May-2024 | 6.1 KiB | 187 | 110 | |
coap_config.h | D | 12-May-2024 | 5 KiB | 210 | 118 | |
radvd.conf.sample | D | 12-May-2024 | 194 | 15 | 12 | |
server.c | D | 12-May-2024 | 7 KiB | 223 | 138 |
README
1Example of libcoap running on contiki 2===================================== 3 4To run the example, do 5 6 $ make 7 $ sudo ./server.minimal-net 8 9(and in a second terminal) 10 11 $ sudo ip -6 a a aaaa::1/64 dev tap0 12 13and query `coap://[aaaa::1000]/time?ticks` with any coap tool, 14or query `coap://[aaaa::1000]/.well-known/core` 15 16This will 17 18* download contiki from the upstream git sources 19* build the server application 20* run the server application, creating a virtual network device tap0 (unless 21 that exists) 22* configure your network interface to make the server accessible. 23 24* return the appropriate response from the server to the client. 25 26The server creates a resource for 'time' with a query 'ticks'. This is 27reported for `.well-known/core`. The work flow for adding more resources does 28not differ from regular libcoap usage. If you seem to run out of memory 29creating the resources, tweak the number of pre-allocated resources 30in `coap_config.h.contiki`. 31