Amir Nathoo

Yes, same issue. I downloaded the factory test that simply uses the 2 modules to send/receive lora packets and it won't join unless I use the 868E6 band.

The Device unique ID is an interesting problem to solve. The reason behind the 8 bytes is that it allows us to follow the LoRaWAN Device EUI model if necessary....

Because one could impersonate a duck and join your cluster to hack into your network or cause harm. If you don't have a way to know the device joining the...

CDP currently doesn't have any mechanisms to perform device validation or for a device to securely be provisioned. What Brenton is referring to is that currently we simply hard code...

Here is an other document that outlines security features for LoRa devices: https://lora-alliance.org/wp-content/uploads/2020/11/la_faq_security_0220_v1.2_0.pdf Specifically point #5 is of interest.

My initial idea was that the device ID if kept secret, could participate in the encryption schema. There is actually a different approach to this where Device UID is not...

The only reason I picked 8 bytes is so the Device UID is compatible with LoRa/LoRaWAN EUID. Some LoRa chips even have that ID available. The bloom filter needs to...

Which version of CDP was the tests performed with? I think the problem might be in the calculation of MAX_DATA_LENGTH https://github.com/Call-for-Code/ClusterDuck-Protocol/blob/master/src/CdpPacket.h#L33 If the PATH section still existed the tested version...

Have you tried the one provided in CDP MemoryFree.h? It works for both ARM and ESP32 chips.

What board is your MamaDuck? I tried on my Heltec ESP32 WiFi v2 PapaDuck and it seems to be working: ` Serial.println( "[PAPA] Free Memory: " + String(freeMemory()) );` ```...