Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,4 +1,4 @@
1		- **Table of** **Contents： **
	1	+ **Contents： **
2	2
3	3	{{toc/}}
4	4
...	...	@@ -6,10 +6,8 @@
6	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
12		-
13	13	[[image:image-20220527085838-1.png]]
14	14
15	15	Unencrypt Network modified from LoRaWAN
...	...	@@ -17,10 +17,8 @@
17	17
18	18	= 2. Analyze the LoRaWAN packet =
19	19
20		-
21	21	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.
22	22
23		-
24	24	[[image:image-20220527090005-2.png]]
25	25
26	26	UDP Server
...	...	@@ -40,8 +40,6 @@
40	40
41	41	(((
42	42	Below is an example, from
43		-
44		-
45	45	)))
46	46
47	47	[[image:image-20220527090122-4.png]]
...	...	@@ -51,29 +51,22 @@
51	51
52	52	= 3. Difference between OTAA and ABP mode =
53	53
54		-
55	55	There are two mode for End Node:
56	56
57		-* (% style="color:blue" %)**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.
	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.
58	58
59		-* (% style="color:blue" %)**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	60
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		-* Setting the end node to ABP mode
	58	+1. Setting the end node to ABP mode
	59	+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]]
69	69
70		-* 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]].
71	71
72		-
73		-
74	74	= 5. Use an unencrypt firmware =
75	75
76		-
77	77	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.
78	78
79	79	(((
...	...	@@ -83,27 +83,12 @@
83	83	[[image:image-20220527090341-5.png]]
84	84
85	85	Unencrypt packet
	73	+
86	86
87		-
88		-(% style="color:red" %)**Note: In some device's firmware . There is a AT Command to Disable Encryption. See below:**
89		-
90		-* (% style="color:blue" %)**AT+DECRYPT=1**(%%)  The payload is uploaded without encryption
91		-
92		-* (% style="color:blue" %)**AT+DECRYPT=0  **(%%) Encrypt when uploading payload (default)
93		-
94		-
95		-
96	96	= 6. limitation =
97	97
98		-
99	99	* None standard LoRaWAN protocol, it is not compatible with LoRaWAN server.
100		-
101	101	* No device management / ADR management defined in LoRaWAN protocol
102		-
103	103	* No security.
104		-
105	105	* No Downlink
106		-
107	107	* Only use for ABP
108		-
109		-