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. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -7,14 +7,17 @@ 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 s, the remote.it only available base on end-user demand.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. 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.** 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 + 16 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]]. 17 17 19 + 20 + 18 18 = **2. RSSH Introduction** = 19 19 20 20 ... ... @@ -35,6 +35,9 @@ 35 35 * LIG16 36 36 * MS14 series if installed with the same firmware. 37 37 41 + 42 + 43 + 38 38 == **2.1 For Firmware Version lower than lgw~-~-build-v5.4.1616478814-20210323-1355** == 39 39 40 40 ... ... @@ -87,9 +87,8 @@ 87 87 88 88 89 89 90 -==== (% style="color:blue" %)**Note for set up RSSH server**(%%)====96 +==== **2.1.2.1 Note for set up RSSH server** ==== 91 91 92 - 93 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. 94 94 95 95 (% class="box" %) ... ... @@ -103,7 +103,6 @@ 103 103 ))) 104 104 105 105 106 - 107 107 == **2.2 For Firmware Version higher than lgw~-~-build-v5.4.1618196981-20210412-1111** == 108 108 109 109 ... ... @@ -234,8 +234,8 @@ 234 234 235 235 (% class="box" %) 236 236 ((( 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**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 &** (%%) again 239 239 ))) 240 240 241 241 ... ... @@ -243,13 +243,13 @@ 243 243 ===== (% style="color:blue" %)**Step 3 : Create a minimal SSH user (reverse SSH proxy for the gateway)**(%%) ===== 244 244 245 245 246 -**1): (% style="color:#4f81bd" %)sudo useradd XXXXX(%%)** **(custom user name)**250 +**1): (% style="color:#4f81bd" %)sudo useradd XXXXX(%%)** (custom user name) 247 247 248 248 **2):** (% style="color:#4f81bd" %)**sudo passwd xxxxxx** 249 249 250 250 **3):** (% style="color:#4f81bd" %)**cp /bin/bash /bin/rbash** 251 251 252 -**4):** (% style="color:#4f81bd" %)**sudo nano /etc/passwd**(%%) **~-~-> Change /bin/bash to /bin/rbash**256 +**4):** (% style="color:#4f81bd" %)**sudo nano /etc/passwd**(%%) ~-~-> Change /bin/bash to /bin/rbash 253 253 254 254 **5):** (% style="color:#4f81bd" %)**sudo nano /home/xxxxx/.bashrc**(%%) **empty it,and input export PATH=$HOME/bin** 255 255 ... ... @@ -266,7 +266,7 @@ 266 266 ===== (% style="color:blue" %)**Step 1 : Come bace the gateway web UI for get the gateway Public key**(%%) ===== 267 267 268 268 269 -**1) **(% style="color:#4f81bd" %)**Remote Mgmt**273 +**1) **in the system ~-~-> (% style="color:#4f81bd" %)**Remote Mgmt** 270 270 271 271 [[image:image-20220527110531-7.png]] 272 272 ... ... @@ -297,12 +297,12 @@ 297 297 298 298 (% class="box" %) 299 299 ((( 300 -(% style="color:#4f81bd" %)**Connection Type **(%%) : **If user's least privileged user with private server uses a password, select**(% style="color:#4f81bd" %)**Public Key**(%%)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 301 (% style="color:red" %)**Note: if user's least privileged user no uses a password,choose from both is fine**(%%) 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**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 306 306 ))) 307 307 308 308 ... ... @@ -328,9 +328,8 @@ 328 328 ===== (% style="color:blue" %)**Step 5 : Create an authorization key file**(%%) ===== 329 329 330 330 331 -**1):** **sudo mkdir /home/xxxxx/.ssh; sudo touch /home/xxxxx/.ssh/authorizedkey**335 +**1):** sudo mkdir /home/xxxxx/.ssh; sudo touch /home/xxxxx/.ssh/authorizedkey 332 332 333 - 334 334 **Debug:** 335 335 336 336 (% class="box" %) ... ... @@ -339,7 +339,6 @@ 339 339 ))) 340 340 341 341 342 - 343 343 === **2.2.3 How to Ser up a Reverse SSH access** === 344 344 345 345