Wiki source code of Remote Access Gateway

Version 20.2 by Xiaoling on 2022/07/14 15:16

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

Wiki source code of Remote Access Gateway

Applications

Navigation