Changes for page How to send none encryption LoRaWAN Packet
Last modified by Xiaoling on 2023/04/19 17:49
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,4 +1,4 @@ 1 - **Contents: ** 1 + **Table of** **Contents: ** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -6,17 +6,22 @@ 6 6 7 7 = 1. Introduce = 8 8 9 + 9 9 A standard LoRaWAN packet via UDP packet forward to LoRaWAN server is AES128 encryption. In this chapter, we will show how this packet looks like in the server and see the possibility to get the content of this packet. 10 10 12 + 11 11 [[image:image-20220527085838-1.png]] 12 12 13 13 Unencrypt Network modified from LoRaWAN 14 14 15 15 18 + 16 16 = 2. Analyze the LoRaWAN packet = 17 17 21 + 18 18 If the gateway is connected to LoRaWAN server via UDP packet fordward. We can set the server address to a UDP server to get the LoRaWAN packets. 19 19 24 + 20 20 [[image:image-20220527090005-2.png]] 21 21 22 22 UDP Server ... ... @@ -36,6 +36,8 @@ 36 36 37 37 ((( 38 38 Below is an example, from 44 + 45 + 39 39 ))) 40 40 41 41 [[image:image-20220527090122-4.png]] ... ... @@ -43,15 +43,21 @@ 43 43 Decode the packet 44 44 45 45 53 + 46 46 = 3. Difference between OTAA and ABP mode = 47 47 56 + 48 48 There are two mode for End Node: 49 49 50 50 * OTAA: Over the air activation. In this mode, the end node will send a Join Request to server, server will reply with a Join Accept and the end node will parse this Join Accept message to get the Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey). Because the AppSkey and NwkSkey is dynamic, OTAA mode provide more security. 51 -* ABP: Activation by personalization. There is no hand-shake with LoRaWAN server for activition. The end node will use fix Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey) to upload the packet. So the packet can be decode if someone know these fix keys .60 +* ABP: Activation by personalization. There is no hand-shake with LoRaWAN server for activition. The end node will use fix Dev Addr / APP Session Key(AppSkey / Network Session Key(NwkSKey) to upload the packet. So the packet can be decode if someone know these fix keys 52 52 62 + 63 + 64 + 53 53 = 4. Get and decode the packet = 54 54 67 + 55 55 According to above, it is possible to get the payload from sensor without LoRaWAN server: 56 56 57 57 1. Setting the end node to ABP mode ... ... @@ -59,8 +59,10 @@ 59 59 60 60 61 61 75 + 62 62 = 5. Use an unencrypt firmware = 63 63 78 + 64 64 If user doesn't care about the security of the data and use Dragino end node, it is possible that we provide a firmware without AES128 encrytion, so the server no need to decode packet. Please note this software is no LoRaWAN compatible and no security. 65 65 66 66 ((( ... ... @@ -72,10 +72,14 @@ 72 72 Unencrypt packet 73 73 74 74 90 + 75 75 = 6. limitation = 76 76 93 + 77 77 * None standard LoRaWAN protocol, it is not compatible with LoRaWAN server. 78 78 * No device management / ADR management defined in LoRaWAN protocol 79 79 * No security. 80 80 * No Downlink 81 81 * Only use for ABP 99 + 100 +