Thanks in advance for your support.
I want to share with the community some strange behaviours when chirpstack handle join Requests.
End nodes work according to LoRaWAN 1.0.2 protocol.
This standard version states that end devices SHALL use the following frequencies when handling join requests:
- 868100000 Hz
- 868300000 Hz
- 868500000 Hz
The join request was initiated in an end node to evaluate the actual behaviour. This node was sending join requests among 8 different frecuency channels, the three default ones and
- 867100000 Hz
- 867300000 Hz
- 867500000 Hz
- 867700000 Hz
- 867900000 Hz
After some repetitions, the general behaviour was according to the referenced standard: only sending join accept to frames sent through default channel frequencies. However, I can report a couple non-supported cases:
The first case shows a received join request with a valid channel frequency that should be accepted but that was never done. Every test was performed with the same app session keys so they would not be a problem.
- Join Request detail
The second case shows a received join request with an invalid channel frequency that should be rejected but that was accepted.
- What checks are performed on the network server for accepting join requests?
- Why I saw this behaviour?
Thanks in advance.