Wiki source code of Remote Access Gateway

Last modified by Kilight Cao on 2022/07/25 10:47

version	line-number	content
19.15	1	Table of Contents:
1.2	2
1.1	3	{{toc/}}
	4
	5
19.2	6
19.17	7	= 1. Use Remote.it service =
1.1	8
19.15	9
22.1	10	Remote.it for remote access is available in the latest Dragino firmware for gateway. For security concerns, the remote.it only available base on end-user demand.
1.1	11
2.15	12	(% style="color:red" %)Important Notice:
1.1	13
25.1	14	* (% style="color:red" %)Remote.it access will give full control of your device to remote support.
27.1	15	* (% style="color:red" %)The Remote.it allow Dragino Support to remote access to the device, If user want to access himself, it need to sign up for an remote.it account.
1.1	16
28.1	17	For how to use remoteit, please see : [[Remoteit user instruction for Dragino Gateway>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=Dragino-Remoteit_User_Manual.pdf]].
	18
19.17	19	= 2. RSSH Introduction =
1.1	20
19.15	21
1.2	22	Reverse SSH for remote access is available in the latest Dragino firmware for gateway. For security concern, the RSSH only available base on end user demand.
1.1	23
2.15	24	(% style="color:red" %)Important Notice:
1.1	25
19.20	26	* (% style="color:red" %)RSSH access will give full control of your device to remote support. Please remove sensitivity info before perform this
	27	* (% style="color:red" %)This RSSH allow Dragino Support to remote access to the device, If user want to access himself, he need to set up the RSSH server himself.
1.1	28
1.2	29	Below gateway support reverse SSH access:
1.1	30
1.2	31	* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
	32	* LG01N, OLG01N (Note: LG01-P LG01-S doesn't support)
	33	* LG02, OLG02
	34	* LG308, DLOS8
	35	* LPS8
	36	* LIG16
	37	* MS14 series if installed with the same firmware.
1.1	38
19.17	39	== 2.1 For Firmware Version lower than lgw~-~-build-v5.4.1616478814-20210323-1355 ==
19.13	40
19.15	41
19.17	42	=== 2.1.1 End User Guide to use SSH access ===
1.2	43
19.16	44
1.2	45	Go to this the Reverse SSH page as below:
	46
3.2	47	[[image:image-20220527102348-1.png]]
1.2	48
	49	Get the RSSH configure page
	50
	51
4.2	52	[[image:image-20220527103251-2.png]]
1.2	53
	54	Connection OK.
	55
19.21	56
19.16	57	* (% style="color:#4f81bd" %)Login ID(%%): Input (% style="color:#4f81bd" %)sshuser
	58	* (% style="color:#4f81bd" %)Host Address(%%): Input (% style="color:#4f81bd" %)support.dragino.com(%%)
	59	* (% style="color:#4f81bd" %)Host Port(%%): Please email to support @ dragino.com to get a valid host port.
4.3	60	* (% style="color:#4f81bd" %)Connect at Startupt(%%): Choose to enable connect once device is powered.
19.17	61	* (% style="color:#4f81bd" %)Network Keys: (%%)Click the Generate keys to generate the keys and download / mail it to Dragino support so Dragino can prepare the remote access to
1.2	62
2.2	63	(((
1.2	64	After doing above, please download and mail the public keys to Dragino support and wait for our mail for the valid host port. Input the valid host port got from our support and click connect so we can remote access to your gateway.
2.2	65	)))
1.2	66
	67
	68
19.17	69	=== 2.1.2 How to Ser up a Reverse SSH access ===
	70
	71
1.2	72	Advance administrator can config a SSH server to provide support their end user themselves. Instruction is as below:
	73
	74	1. Prepare a Linux server with public IP. The gateways need to be able to create SSH connection to this server. We recommend to use a server that performs no other function than to support the RSSH access, and to have no additional accounts active, and no access from the Internet that uses ID/password authentication.
4.3	75	1. In the gateway settings, The (% style="color:#4f81bd" %)Login ID(%%) will be the SSH user for this server and the (% style="color:#4f81bd" %)Host Address(%%) is the server address.
1.2	76	1. Ask your end user to send you the key generate in the gateway and put them in /home/<Login ID>/.ssh/authorized_key file.
	77	1. Give a free port to the user and ask them to configure RSSH page in the gateway.
	78	1. In your server or other machine, you will able to access to the end user device by below command:
	79
2.5	80	(% class="box" %)
	81	(((
19.21	82	$ ssh -p <End User Host Port> root@<Host Address>
2.5	83	)))
1.2	84
2.5	85	(((
4.4	86	(% style="color:red" %)Remote RSSH Access allow the gateway to connect to SSH server as well. This will create risk to the RSSH server. Please make sure the account use for Gateway Access has the lowest access right.
2.5	87	)))
1.2	88
2.3	89
1.2	90
20.2	91	==== (% style="color:blue" %)Note for set up RSSH server(%%) ====
19.17	92
20.2	93
2.9	94	If gateway reboot or the connection is incidentely close by end node. The port in SSH server will still be occupy for a long time. Administrator can use below commands to release the port.
1.2	95
2.4	96	(% class="box" %)
	97	(((
19.21	98	**[root@iZt4n22vqvm7ajogrfiif6Z ~~]# lsof -i :9102 ~-~-> check the port 9102 process status (change 9102 to the actually port for your gateway.
2.4	99	COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
	100	sshd 21430 sshuser 15u IPv4 47567059 0t0 TCP localhost:bacula-fd (LISTEN)
	101	[root@iZt4n22vqvm7ajogrfiif6Z ~~]# kill 21430 ~-~-> Kill PID of this process.
	102	[root@iZt4n22vqvm7ajogrfiif6Z ~~]# lsof -i :9102
19.21	103	[root@iZt4n22vqvm7ajogrfiif6Z ~~]#**
2.4	104	)))
1.2	105
2.11	106
20.2	107
19.17	108	== 2.2 For Firmware Version higher than lgw~-~-build-v5.4.1618196981-20210412-1111 ==
1.2	109
19.21	110
1.2	111	Below gateway support reverse SSH access:
	112
2.5	113	(% class="box" %)
	114	(((
19.21	115	**Firmware Version >lgw~-~-build-v5.4.1618196981-20210412-1111 Firmware Download
2.11	116	LG01N, OLG01N (Note: LG01-P LG01-S doesn't support)
	117	LG02, OLG02
	118	LG308, DLOS8
	119	LPS8
19.21	120	LIG16**
2.5	121	)))
1.2	122
2.11	123
19.21	124
19.17	125	=== 2.2.1 End User Guide to use SSH access ===
1.2	126
	127
19.17	128	==== 2.2.1.1 Install the SSH service for server ====
1.2	129
	130
19.17	131	===== (% style="color:blue" %)Step 1 : Download the SSH service code(%%) =====
	132
	133
	134	1). git clone [[https:~~/~~/github.com/dragino/rssh-server.git>>url:https://github.com/dragino/rssh-server.git]] rssh-server
	135
6.2	136	[[image:image-20220527105447-1.png]]
1.2	137
	138	git clone rssh-server
	139
2.5	140
19.17	141	2). cd rssh-server; sudo make ~-~--> to Generate the execute file：rssh_serv
1.2	142
6.2	143	[[image:image-20220527105511-2.png]]
1.2	144
	145	Generate the execute file
	146
6.2	147
1.2	148	Debug :
	149
2.5	150	(% class="box" %)
	151	(((
19.21	152	if you git fail. ~-~-> (% style="color:#4f81bd" %)sudo: git: command not found.(%%)
	153	please install git. ~-~-> (% style="color:#4f81bd" %)yum install git -y or apt-get install git -y.
2.5	154	)))
1.2	155
2.5	156	(% class="box" %)
	157	(((
19.21	158	if you make error 127,it (% style="color:#4f81bd" %)lack of gcc.(%%)
	159	please install gcc. ~-~-> (% style="color:#4f81bd" %)yum install gcc.(%%)
2.5	160	)))
1.2	161
8.2	162	[[image:image-20220527105856-3.png]]
1.2	163
	164	lack of gcc
	165
19.21	166
2.5	167	(% class="box" %)
	168	(((
19.21	169	if you make a fatal error : sqlite3.h,it (% style="color:#4f81bd" %)lack of sqlite3.(%%)
	170	please insatell (% style="color:#4f81bd" %)sqlite3(%%)(% style="color:#4f81bd" %).
2.5	171	)))
1.2	172
8.2	173	[[image:image-20220527105918-4.png]]
1.2	174
	175	lack of sqlite3
	176
8.2	177
19.17	178	(% style="color:blue" %)How to install Sqlit3:
1.2	179
2.5	180	(% class="box" %)
	181	(((
19.18	182	(% style="color:#037691" %)Step1:(%%) Download the SQLit3 installation package
2.5	183	sudo wget [[https:~~/~~/www.sqlite.org/2021/sqlite-autoconf-3350400.tar.gz>>url:https://www.sqlite.org/2021/sqlite-autoconf-3350400.tar.gz]]
19.17	184
19.18	185	(% style="color:#037691" %)Step2:(%%) tar the SQLit3 installation package
1.2	186	sudo tar -zxvf sqlite-autoconf-3350300.tar.gz
19.17	187
19.18	188	(% style="color:#037691" %)Step3:(%%) Generate the makefile
1.2	189	cd sqlite-autoconf-3350300/;./configure
19.17	190
19.18	191	(% style="color:#037691" %)Step4:(%%) Compile makefile
1.2	192	sudo make
19.17	193
19.18	194	(% style="color:#037691" %)Step5: (%%)Install makefile
1.2	195	sudo make install
19.17	196
19.18	197	(% style="color:#037691" %)Check:(%%)
	198	cd /usr/local/bin;ls -al ~-~-> Check to see if there is a file for sqlite3
	199	cd sqlite-autoconf-3350300/;./sqlite3 test.db ~-~-> Test whether the sqlite3 was installed successfully
19.17	200
19.18	201	(% style="color:#037691" %)debug:(%%)
1.2	202	If you get the imformation that is SQLite header and source version mismatch, when you execute./sqlite3 test.db.
	203	Please execute the command /sbin/ldconfig.
	204	After that execute the command ./sqlite3 test.db again.
2.5	205	)))
1.2	206
2.5	207
1.2	208
19.17	209	===== (% style="color:blue" %)Step 2 : Install and run the RSS service(%%) =====
1.2	210
19.17	211
	212	1): intall database for /var/rsshdb.sqlite3 and Server development port for 3721(The default is 3721)
	213
1.2	214	user must enter the root account and run the following commands
	215
2.5	216	(% class="box" %)
	217	(((
19.18	218	**~ $ ./create_sqlite3_db.sh
2.13	219	$ ./rssh_serv -p 3721 2>&1 &
19.18	220	$ ps -ef \| grep rssh_serv check 3721 port**
2.5	221	)))
1.2	222
10.2	223	[[image:image-20220527110436-6.png]]
1.2	224
	225	intall database and server development port
	226
19.17	227
1.2	228	Debug:
	229
2.5	230	(% class="box" %)
	231	(((
19.18	232	Check /var/rsshdb.sqlite3 ~-~->(% style="color:#4f81bd" %) ls /var/rsshdb.sqlite3(%%)
	233	Check ls /var/rsshdb.sqlite3 ~-~-> (% style="color:#4f81bd" %)sudo chmod 777 rssh_serv
2.5	234	)))
1.2	235
2.5	236	(% class="box" %)
	237	(((
19.22	238	if fail to open dpvlry or to bind to it
	239	please kill rssh_serv,and run (% style="color:#4f81bd" %) ./rssh_serv -p 3721 2>&1 &(%%)(% style="color:#4f81bd" %) (%%) again
2.5	240	)))
1.2	241
2.5	242
1.2	243
19.17	244	===== (% style="color:blue" %)Step 3 : Create a minimal SSH user (reverse SSH proxy for the gateway)(%%) =====
	245
	246
19.22	247	1): (% style="color:#4f81bd" %)sudo useradd XXXXX(%%) (custom user name)
1.2	248
9.2	249	2): (% style="color:#4f81bd" %)sudo passwd xxxxxx
1.2	250
9.2	251	3): (% style="color:#4f81bd" %)cp /bin/bash /bin/rbash
1.2	252
19.22	253	4): (% style="color:#4f81bd" %)sudo nano /etc/passwd(%%) ~-~-> Change /bin/bash to /bin/rbash
1.2	254
9.2	255	5): (% style="color:#4f81bd" %)sudo nano /home/xxxxx/.bashrc(%%) empty it,and input export PATH=$HOME/bin
1.2	256
9.2	257	6): (% style="color:#4f81bd" %)sudo nano /home/xxxxx/.bash_profile(%%) empty it,and input export PATH=$HOME/bin
1.2	258
	259
19.17	260	(% style="color:red" %)Now user "XXXXX" is the user with limited permissions of the current system
2.5	261
1.2	262
	263
19.17	264	=== 2.2.2 How does user get the gateway to connect to a user's private server ===
1.2	265
19.17	266
	267	===== (% style="color:blue" %)Step 1 : Come bace the gateway web UI for get the gateway Public key(%%) =====
	268
	269
19.22	270	1) in the system ~-~-> (% style="color:#4f81bd" %)Remote Mgmt
19.17	271
12.2	272	[[image:image-20220527110531-7.png]]
1.2	273
	274	Remote Mgmt
	275
2.6	276
1.2	277
19.17	278	===== (% style="color:blue" %)Step 2 : Authorization server(%%) =====
	279
	280
1.2	281	copy the Gateway Publickey into user's private server "/home/XXXXX/.ssh/authorized_keys" file.
	282
12.2	283	[[image:image-20220527110625-8.png]]
1.2	284
	285	Publickey
	286
2.6	287
1.2	288
19.17	289	===== (% style="color:blue" %)Step 3 : connecte private server(%%) =====
	290
	291
1.2	292	in the gateway web UI
	293
13.2	294	[[image:image-20220527110700-9.png]]
1.2	295
	296	gateway web UI
	297
19.17	298
2.6	299	(% class="box" %)
	300	(((
19.22	301	(% style="color:#4f81bd" %)Connection Type (%%) : If user's least privileged user with private server uses a password, select (% style="color:#4f81bd" %)Public Key(%%)
19.17	302	(% style="color:red" %)Note: if user's least privileged user no uses a password,choose from both is fine(%%)
19.22	303	(% style="color:#4f81bd" %)Login ID(%%) : Input user name "eg : "XXXXX"
	304	(% style="color:#4f81bd" %)Host Address(%%) : Input user's private server address
	305	(% style="color:#4f81bd" %)Connect at Startupt (%%): Choose to enable connect once device is powered.
	306	Click Save and then Connect
2.6	307	)))
1.2	308
2.7	309
1.2	310
19.17	311	===== (% style="color:blue" %)Step 4 : Cheak is fine(%%) =====
	312
	313
1.2	314	Rssh Host connection Ok
	315
15.2	316	[[image:image-20220527111009-10.png]]
1.2	317
	318	Rssh Host connection Ok
	319
2.7	320
1.2	321	user can use common ps \| grep ssh to check it in the gateway.
	322
15.2	323	[[image:image-20220527111041-11.png]]
1.2	324
	325	Check the gateway
	326
	327
	328
19.17	329	===== (% style="color:blue" %)Step 5 : Create an authorization key file(%%) =====
1.2	330
19.17	331
19.23	332	1): sudo mkdir /home/xxxxx/.ssh; sudo touch /home/xxxxx/.ssh/authorizedkey
19.17	333
19.23	334
1.2	335	Debug:
	336
2.7	337	(% class="box" %)
	338	(((
19.17	339	~ check: sudo ls /home/xxxxx/.ssh/authorizedkey
2.7	340	)))
1.2	341
	342
19.23	343
19.17	344	=== 2.2.3 How to Ser up a Reverse SSH access ===
1.2	345
	346
19.17	347	==== (% style="color:blue" %)Step 1 : Log into the server system(%%) ====
	348
	349
17.2	350	[[image:image-20220527111145-12.png]]
	351
1.2	352	Loging server
	353
2.8	354
1.2	355
19.17	356	==== (% style="color:blue" %)Step 2 : access the gateway(%%) ====
	357
	358
18.2	359	(% class="box" %)
	360	(((
19.17	361	$ cd rssh-server/
18.2	362	)))
1.2	363
	364	Check the gateway linking to the server $ ./connect-gw.sh -l
	365
17.2	366	[[image:image-20220527111219-13.png]]
1.2	367
	368	Check the gateway linking to the server
	369
	370
19.17	371
1.2	372	access the gateway $ ./connect-gw.sh <GWID>
	373
18.2	374	[[image:image-20220527111300-14.png]]
1.2	375
	376	reverse ssh access the gateway
19.17	377
	378

Wiki source code of Remote Access Gateway

Applications

Navigation