Changes for page Remote Access Gateway
Last modified by Kilight Cao on 2022/07/25 10:47
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -7,17 +7,15 @@ 7 7 = **1. Use Remote.it service** = 8 8 9 9 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 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. 11 11 12 12 (% style="color:red" %)**Important Notice:** 13 13 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 - 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. 17 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 18 19 19 20 - 21 21 = **2. RSSH Introduction** = 22 22 23 23 ... ... @@ -38,9 +38,6 @@ 38 38 * LIG16 39 39 * MS14 series if installed with the same firmware. 40 40 41 - 42 - 43 - 44 44 == **2.1 For Firmware Version lower than lgw~-~-build-v5.4.1616478814-20210323-1355** == 45 45 46 46 ... ... @@ -93,8 +93,9 @@ 93 93 94 94 95 95 96 -==== ** 2.1.2.1Note for set up RSSH server** ====91 +==== (% style="color:blue" %)**Note for set up RSSH server**(%%) ==== 97 97 93 + 98 98 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. 99 99 100 100 (% class="box" %) ... ... @@ -108,6 +108,7 @@ 108 108 ))) 109 109 110 110 107 + 111 111 == **2.2 For Firmware Version higher than lgw~-~-build-v5.4.1618196981-20210412-1111** == 112 112 113 113 ... ... @@ -238,8 +238,8 @@ 238 238 239 239 (% class="box" %) 240 240 ((( 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 &** (%%) again238 +**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** 243 243 ))) 244 244 245 245 ... ... @@ -247,13 +247,13 @@ 247 247 ===== (% style="color:blue" %)**Step 3 : Create a minimal SSH user (reverse SSH proxy for the gateway)**(%%) ===== 248 248 249 249 250 -**1): (% style="color:#4f81bd" %)sudo useradd XXXXX(%%)** (custom user name) 247 +**1): (% style="color:#4f81bd" %)sudo useradd XXXXX(%%)** **(custom user name)** 251 251 252 252 **2):** (% style="color:#4f81bd" %)**sudo passwd xxxxxx** 253 253 254 254 **3):** (% style="color:#4f81bd" %)**cp /bin/bash /bin/rbash** 255 255 256 -**4):** (% style="color:#4f81bd" %)**sudo nano /etc/passwd**(%%) ~-~-> Change /bin/bash to /bin/rbash 253 +**4):** (% style="color:#4f81bd" %)**sudo nano /etc/passwd**(%%) ** ~-~-> Change /bin/bash to /bin/rbash** 257 257 258 258 **5):** (% style="color:#4f81bd" %)**sudo nano /home/xxxxx/.bashrc**(%%) **empty it,and input export PATH=$HOME/bin** 259 259 ... ... @@ -270,7 +270,7 @@ 270 270 ===== (% style="color:blue" %)**Step 1 : Come bace the gateway web UI for get the gateway Public key**(%%) ===== 271 271 272 272 273 -**1) **in the system ~-~-> (% style="color:#4f81bd" %)**Remote Mgmt**270 +**1) in the system ~-~->** (% style="color:#4f81bd" %)**Remote Mgmt** 274 274 275 275 [[image:image-20220527110531-7.png]] 276 276 ... ... @@ -301,12 +301,12 @@ 301 301 302 302 (% class="box" %) 303 303 ((( 304 -(% style="color:#4f81bd" %)**Connection Type **(%%) : If user's least privileged user with private server uses a password, select (% style="color:#4f81bd" %)**Public Key**(%%) 301 +(% style="color:#4f81bd" %)**Connection Type **(%%) : **If user's least privileged user with private server uses a password, select** (% style="color:#4f81bd" %)**Public Key**(%%) 305 305 (% style="color:red" %)**Note: if user's least privileged user no uses a password,choose from both is fine**(%%) 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 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** 310 310 ))) 311 311 312 312 ... ... @@ -332,8 +332,9 @@ 332 332 ===== (% style="color:blue" %)**Step 5 : Create an authorization key file**(%%) ===== 333 333 334 334 335 -**1):** sudo mkdir /home/xxxxx/.ssh; sudo touch /home/xxxxx/.ssh/authorizedkey 332 +**1):** **sudo mkdir /home/xxxxx/.ssh; sudo touch /home/xxxxx/.ssh/authorizedkey** 336 336 334 + 337 337 **Debug:** 338 338 339 339 (% class="box" %) ... ... @@ -342,6 +342,7 @@ 342 342 ))) 343 343 344 344 343 + 345 345 === **2.2.3 How to Ser up a Reverse SSH access** === 346 346 347 347