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]]
...	...	@@ -45,6 +45,7 @@
45	45
46	46	= 3. Difference between OTAA and ABP mode =
47	47
	55	+
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.
...	...	@@ -54,15 +54,17 @@
54	54
55	55	= 4. Get and decode the packet =
56	56
	65	+
57	57	According to above, it is possible to get the payload from sensor without LoRaWAN server:
58	58
59	59	1. Setting the end node to ABP mode
60		-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	+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]].
61	61
62	62
63	63
64	64	= 5. Use an unencrypt firmware =
65	65
	75	+
66	66	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.
67	67
68	68	(((
...	...	@@ -72,12 +72,22 @@
72	72	[[image:image-20220527090341-5.png]]
73	73
74	74	Unencrypt packet
75		-
76	76
	86	+
	87	+Note: In some device's firmware . There is a AT Command to Disable Encryption. See below:
	88	+
	89	+* AT+DECRYPT=1 The payload is uploaded without encryption
	90	+* AT+DECRYPT=0 Encrypt when uploading payload (default)
	91	+
	92	+
	93	+
77	77	= 6. limitation =
78	78
	96	+
79	79	* None standard LoRaWAN protocol, it is not compatible with LoRaWAN server.
80	80	* No device management / ADR management defined in LoRaWAN protocol
81	81	* No security.
82	82	* No Downlink
83	83	* Only use for ABP
	102	+
	103	+