If the server is started with the option { type: 'udp6' }, some of the messages are read twice from the server (same messageId and contents). This may reflect a bug in the COAP Library or it may be a problem on the way we handle the messages (maybe registering the listeners twice?). It doesn't seem to reproduce using IPv4.
If the server is started with the option
{ type: 'udp6' }
, some of the messages are read twice from the server (same messageId and contents). This may reflect a bug in the COAP Library or it may be a problem on the way we handle the messages (maybe registering the listeners twice?). It doesn't seem to reproduce using IPv4.It can be reproduced using the tests for https://github.com/telefonicaid/lightweightm2m-iotagent