Last modified by Xiaoling on 2023/04/19 17:49
<
From version < 16.1 >
edited by Edwin Chen
on 2022/08/23 11:59
To version < 1.8 >
edited by Xiaoling
on 2022/05/12 11:53
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,101 +1,74 @@
1 - **Table of** **Contents： **
1 + **Contents： **
2 2  
3 3  {{toc/}}
4 4  
5 -
6 -
7 7  = 1. Introduce =
8 8  
9 -
10 10  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.
11 11  
9 +[[image:https://wiki.dragino.com/images/thumb/3/36/Unencrypt_Network_3.png/600px-Unencrypt_Network_3.png||height="476" width="600"]]
12 12  
13 -[[image:image-20220527085838-1.png]]
14 -
15 15  Unencrypt Network modified from LoRaWAN
16 16  
17 -
18 -
19 19  = 2. Analyze the LoRaWAN packet =
20 20  
21 -
22 22  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.
23 23  
17 +[[image:https://wiki.dragino.com/images/thumb/5/57/None_Encryption_1.png/600px-None_Encryption_1.png||height="259" width="600"]]
24 24  
25 -[[image:image-20220527090005-2.png]]
26 -
27 27  UDP Server
28 28  
29 29  
30 30  We can get one of the LoRaWAN packet and analyze it. See below
31 31  
32 -[[image:image-20220527090050-3.png]]
24 +[[image:https://wiki.dragino.com/images/thumb/b/b9/None_Encryption_2.png/600px-None_Encryption_2.png||height="497" width="600"]]
33 33  
34 34  Analyze the data
35 35  
36 -
37 37  (((
38 -From above screen shot, we can see most of the meaning except this** (% style="color:#4f81bd" %)"data":"QHxqASaAygwCXrumS1oFsgRq"(%%)**(% style="color:#4f81bd" %).(%%) This is the AES128 encryption data we mention above, it is base64 format. To decode this data, we need to have the** (% style="color:#4f81bd" %)APP Session Key(%%)**(% style="color:#4f81bd" %) (%%)and (% style="color:#4f81bd" %)**Network Session Key**(%%) of this end node. If we have these two keys, we are able to decode this packet by some LoRaWAN decode website like: [[LoRaWAN Decode Website>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]].
29 +From above screen shot, we can see most of the meaning except this** "data":"QHxqASaAygwCXrumS1oFsgRq"**. This is the AES128 encryption data we mention above, it is base64 format. To decode this data, we need to have the APP Session Key and Network Session Key of this end node. If we have these two keys, we are able to decode this packet by some LoRaWAN decode website like: [[LoRaWAN Decode Website>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]].
39 39  )))
40 40  
41 41  
42 42  (((
43 43  Below is an example, from
44 -
45 -
46 46  )))
47 47  
48 -[[image:image-20220527090122-4.png]]
37 +[[image:https://wiki.dragino.com/images/thumb/4/4c/None_Encryption_3.png/600px-None_Encryption_3.png||height="388" width="600"]]
49 49  
50 50  Decode the packet
51 51  
52 -
53 -
54 54  = 3. Difference between OTAA and ABP mode =
55 55  
56 -
57 57  There are two mode for End Node:
58 58  
59 59  * 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.
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
46 +* 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.
61 61  
62 -
63 63  = 4. Get and decode the packet =
64 64  
65 -
66 66  According to above, it is possible to get the payload from sensor without LoRaWAN server:
67 67  
68 68  1. Setting the end node to ABP mode
69 -1. Add decode program and add the keys of the sensor. So to get the payload. There is an example for such application, see [[Communication with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]]
53 +1. Add decode program and add the keys of the sensor. So to get the payload. There is an example for such application, see [[Communication with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]]
70 70  
71 -
72 72  = 5. Use an unencrypt firmware =
73 73  
74 -
75 75  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.
76 76  
77 77  (((
78 -The software will disable encryption, so the LoRaWAN payload raw** (% style="color:#4f81bd" %)"data":"QHxqASaAygwCXrumS1oFsgRq"(%%)** will looks like (% style="color:#4f81bd" %)**"data":"4068370126000000000c9e11223361898841"**(%%), and the meaning is as below:
60 +The software will disable encryption, so the LoRaWAN payload raw "data":"QHxqASaAygwCXrumS1oFsgRq" will looks like "data":"4068370126000000000c9e11223361898841", and the meaning is as below:
79 79  )))
80 80  
81 -[[image:image-20220527090341-5.png]]
63 +[[image:https://wiki.dragino.com/images/thumb/d/d6/None_Encryption_4.png/600px-None_Encryption_4.png||height="70" width="600"]]
82 82  
83 83  Unencrypt packet
66 +
84 84  
85 -
86 -Note: In the new firmware with 007 stack . There is a AT Command to Disable Encryption. See below:
87 -
88 -* AT+DECRYPT=1 The payload is uploaded without encryption
89 -* AT+DECRYPT=0 Encrypt when uploading payload (default)
90 -
91 -
92 92  = 6. limitation =
93 93  
94 -
95 95  * None standard LoRaWAN protocol, it is not compatible with LoRaWAN server.
96 96  * No device management / ADR management defined in LoRaWAN protocol
97 97  * No security.
98 98  * No Downlink
99 99  * Only use for ABP
100 -
101 -
image-20220527085838-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -146.1 KB
Content
image-20220527090005-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content
image-20220527090050-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -107.8 KB
Content
image-20220527090122-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -220.7 KB
Content
image-20220527090341-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.8 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0