Wiki source code of Remote Access Gateway

Version 25.1 by Kilight Cao on 2022/07/25 10:42

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

Wiki source code of Remote Access Gateway

Applications

Navigation