Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Kilight
	1	+XWiki.Xiaoling

Content

...	...	@@ -220,12 +220,14 @@
220	220
221	221	The following example does not have configuration certificates:
222	222
	223	+
223	223	== 4.1  Configure Packet Forwarder ==
224	224
225	225
226	226	In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
227	227
228		-* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
	229	+* In the (% style="color:blue" %)**LoRaWAN** (%%)menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP**
	230	+
229	229	* Make sure the following settings are set:
230	230	** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
231	231	** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
...	...	@@ -232,7 +232,7 @@
232	232	** **Server port for upstream:** //1700//
233	233	** **Server port for downstream:** //1700//
234	234
235		- Click **Save & Apply**.
	237	+ Click (% style="color:blue" %)**Save & Apply**.
236	236
237	237	[[image:image-20221222114220-2.png||height="748" width="931"]]
238	238
...	...	@@ -256,7 +256,7 @@
256	256
257	257	(% class="box infomessage" %)
258	258	(((
259		-/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
	261	+**/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml **
260	260	)))
261	261
262	262
...	...	@@ -266,7 +266,7 @@
266	266
267	267	(% class="box infomessage" %)
268	268	(((
269		-vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
	271	+**vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml **
270	270	)))
271	271
272	272	[[image:image-20230415165254-1.png||height="583" width="956"]]
...	...	@@ -279,7 +279,7 @@
279	279
280	280	(% class="box infomessage" %)
281	281	(((
282		-/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
	284	+**/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml**
283	283	)))
284	284
285	285	If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**.
...	...	@@ -339,7 +339,8 @@
339	339
340	340	In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
341	341
342		-* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
	344	+* In the (% style="color:blue" %)**LoRaWAN**(%%) menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP**
	345	+
343	343	* Make sure the following settings are set:
344	344	** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
345	345	** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
...	...	@@ -346,7 +346,7 @@
346	346	** **Server port for upstream:** //1700//
347	347	** **Server port for downstream:** //1700//
348	348
349		- Click **Save & Apply**.
	352	+ Click (% style="color:blue" %)**Save & Apply**.
350	350
351	351	[[image:image-20221222114220-2.png||height="748" width="931"]]
352	352
...	...	@@ -366,7 +366,7 @@
366	366
367	367	(% class="box infomessage" %)
368	368	(((
369		-root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
	372	+**root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml **
370	370	)))
371	371
372	372	[[image:image-20221222113302-1.png]]
...	...	@@ -754,7 +754,7 @@
754	754
755	755	This example will be shown how to store/get all the data in two ways:
756	756
757		-**//1). Chirpstack ~-~-> Node-red//**
	760	+(% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//**
758	758
759	759
760	760	[[image:image-20221012184501-1.png]]
...	...	@@ -773,7 +773,7 @@
773	773	[[image:image-20221012174352-3.png]]
774	774
775	775
776		-**//2). MQTT  Sub//**
	779	+(% style="color:blue" %)**//2). MQTT  Sub//**
777	777
778	778	If you don't want to store the information via node-red, you can get the output via the subscribe command.
779	779
...	...	@@ -782,15 +782,15 @@
782	782
783	783	(% class="box infomessage" %)
784	784	(((
785		-mosquitto_sub -h localhost -t "application/#" -v
	788	+**mosquitto_sub -h localhost -t "application/#" -v**
786	786	)))
787	787
788	788
789		-**Different host**
	792	+(% style="color:blue" %)**Different host**
790	790
791	791	(% class="box infomessage" %)
792	792	(((
793		-mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
	796	+**mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v**
794	794	)))
795	795
796	796	[[image:image-20221012173639-1.png]]
...	...	@@ -808,7 +808,5 @@
808	808	(((
809	809	Under normal circumstances, users need to change the APPKEY to solve this problem.
810	810
811		-
812		-
813	813
814	814	)))