Wiki source code of Monitor & Remote Access Gateway
Last modified by Kilight Cao on 2025/03/28 09:44
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | **Table of Contents:** | ||
2 | |||
3 | {{toc/}} | ||
4 | |||
5 | |||
6 | |||
7 | |||
8 | = 1. Dragino Platform Monitor = | ||
9 | |||
10 | |||
11 | **Below list the support products and Requirements:** | ||
12 | |||
13 | 1. LoRaWAN Gateway model: **[[LG308N>>doc:Main.User Manual for All Gateway models.LG308N - LoRaWAN Gateway User Manual.WebHome]]**, **[[DLOS8N>>doc:Main.User Manual for All Gateway models.DLOS8N.WebHome]]**,**[[LPS8N>>doc:Main.User Manual for All Gateway models.LPS8N - LoRaWAN Gateway User Manual.WebHome]]**,**[[LPS8v2>>doc:Main.User Manual for All Gateway models.HP0C.WebHome]]**,**[[MS48-LR>>doc:Main.User Manual for All Gateway models.MS48-LR_LoRaWAN_To_Modbus_Gateway.WebHome]]** | ||
14 | |||
15 | The LG308,DLOS8N,LPS8N supports remote platform monitor functionality ,Since firmware: **[[lgw~~-~~-build-v5.4.1735869581>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/lgw--build-v5.4.1735869581-20250103-1003/]]** | ||
16 | |||
17 | The LPS8v2,MS48-LR supports remote platform monitor functionality,Since software version **dragino-ui : 2024-12-15 ** | ||
18 | |||
19 | |||
20 | Once you have received your gateway and want to manage your gateway, you need to perform the following steps: | ||
21 | |||
22 | |||
23 | == 1.1 Create an account == | ||
24 | |||
25 | Contact: (% style="color:blue" %)**support@dragino.cc** | ||
26 | |||
27 | We will create a gateway management platform for you.Once created we will give you a platform and you will need to enter a password and then your gateway management platform will be created. | ||
28 | |||
29 | [[image:image-20250109152734-1.png||height="530" width="1331"]] | ||
30 | |||
31 | == 1.2 Configure gateway == | ||
32 | |||
33 | |||
34 | To access the (% style="color:blue" %)**System~-~->Remote Mgmt**(%%) interface of the gateway, you can select "(% style="color:blue" %)**Enable**(%%)" and customize the owner,then click on "(% style="color:blue" %)**Save&Apply**(%%)". | ||
35 | |||
36 | ~1. Click "(% style="color:blue" %)**Enable**(%%)" ~-~-~-~--> If this option is checked, the gateway will enable Remote Platform Monitor | ||
37 | |||
38 | 2. Configure the (% style="color:blue" %)**Owner**(%%) ~-~-~-~--> Fill in the Owne given by the manufacturer, that's the only one.The default is: registered email | ||
39 | |||
40 | 3. Click "(% style="color:blue" %)**Save&Apply**(%%)" | ||
41 | |||
42 | (% style="color:red" %)Note: If the Owner parameter is set to Dragino, the device will be registered with the Dragino account | ||
43 | |||
44 | [[image:image-20250107151805-1.png]] | ||
45 | |||
46 | |||
47 | Check the remote platform connection status | ||
48 | |||
49 | [[image:image-20241216162640-2.png]] | ||
50 | |||
51 | After the above configuration is complete, wait for 2-3 minutes, the gateway will be displayed on the dashboard | ||
52 | |||
53 | |||
54 | == 1.3 Check the dashboard. == | ||
55 | |||
56 | Check if you can see your gateway information in the dashboard | ||
57 | |||
58 | [[image:image-20241216163331-3.png||height="578" width="1258"]] | ||
59 | |||
60 | |||
61 | And click on your device to go to the next level to see if the gateway specific information is displayed properly | ||
62 | |||
63 | |||
64 | **Chart function introduction:** | ||
65 | |||
66 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__1.Gateway information: __**(%%) Will show Gateway time, uptime, mac address, lorawan status, model and other gateway information | ||
67 | |||
68 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__2. Line chart: __**(%%) Record free RAM, used Disk, and CPU load of the current gateway | ||
69 | |||
70 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__3. Auto-Update: __**(%%) After clicking, the gateway will be updated | ||
71 | |||
72 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__4. Refresh: __**(%%) After clicking, the gateway will immediately update the data information and displays the current package version on the dashboard | ||
73 | |||
74 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__5. Reboot gateway: __**(%%) After clicking, the gateway will reboot. | ||
75 | |||
76 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__6. Get Latest Log File: __**(%%) After clicking, the gateway records a log for 5 minutes and uploads it to the dashboard | ||
77 | |||
78 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__7. Change Server Address: __**(%%) Add the lorawan server address and the gateway will be configured and modified | ||
79 | |||
80 | The format is as follows: | ||
81 | |||
82 | **{"action":"set_server1_address","server_address":"10.130.2.123"}** | ||
83 | |||
84 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__8. Download Dragino Gateway log: __**(%%) After you complete "Get Latest Log File", Click "Click me" to download gateway logs | ||
85 | |||
86 | |||
87 | [[image:image-20241216170144-6.png||height="596" width="1258"]] | ||
88 | |||
89 | |||
90 | [[image:image-20241216170119-5.png||height="249" width="1259"]] | ||
91 | |||
92 | |||
93 | |||
94 | |||
95 | = 2. Remote Access via Remote.it. = | ||
96 | |||
97 | |||
98 | 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. | ||
99 | |||
100 | |||
101 | (% style="color:red" %)**Important Notice:** | ||
102 | |||
103 | * Remote.it access will give full control of your device to remote support. | ||
104 | |||
105 | * The Remote.it allows Dragino Support to remote access to the device, If user want to access himself, it need to sign up for an remote.it account. | ||
106 | |||
107 | * For how to use remote.it for (% style="color:blue" %)**general remote control**(%%), please see : [[Remoteit user instruction for Dragino Gateway>>https://www.remote.it/getting-started/dragino]]. | ||
108 | |||
109 | * For Quick add remote.it to (% style="color:blue" %)**Dragino for remote debug**(%%), please see below: | ||
110 | |||
111 | (% style="color:blue" %)**1. Install the Remote.it software** | ||
112 | |||
113 | Users can directly click** "Install"** on the Web UI to install Remote. it. | ||
114 | |||
115 | |||
116 | [[image:image-20220725134300-1.png||height="438" width="905"]] | ||
117 | |||
118 | |||
119 | |||
120 | (% style="color:blue" %)**2. Enter the license key** | ||
121 | |||
122 | Users need to enter the license key in the box under **"2. Register"** section and click the **"Save"** button and** "Register"** button. | ||
123 | |||
124 | (% style="color:red" %)**When the user enters this license key, Dragino support will have access to your gateway.** | ||
125 | |||
126 | |||
127 | (% class="box infomessage" %) | ||
128 | ((( | ||
129 | **fd173d1d-faed-493e-a868-c511a38aba45** | ||
130 | ))) | ||
131 | |||
132 | [[image:image-20230607085305-1.png||height="555" width="993"]] | ||
133 | |||
134 | |||
135 | |||
136 | (% style="color:blue" %)**3. Connect and tell us your device ID or Hostname** | ||
137 | |||
138 | Users can view the device ID or Hostname of the gateway on** (% style="color:red" %)System ~-~-> System Overview(%%)** interface.Such as : dragino-1ef9ac | ||
139 | |||
140 | |||
141 | [[image:image-20220725115720-2.png||height="658" width="900"]] | ||
142 | |||
143 | |||
144 | == 2.1 How to save the registered remote after the gateway's firmware update. == | ||
145 | |||
146 | |||
147 | Before version [[lgw~~-~~-build-v5.4.1668240318-20221112-1606>>http://repo.dragino.com/release/miscellaneous/remoteit/dragino-lgw--v5.4.1668240318-squashfs-sysupgrade.bin]], once the gateway firmware is upgraded the remote configuration is gone. | ||
148 | |||
149 | This issue is now corrected: | ||
150 | |||
151 | |||
152 | |||
153 | === **The gateway version is lower than** **lgw~-~-build-v5.4.1668240318-20221112-1606:** === | ||
154 | |||
155 | |||
156 | **~1. upload the [[backup file>>http://repo.dragino.com/release/miscellaneous/remoteit/backup.tar.gz]] to update the configuration.** | ||
157 | |||
158 | [[image:image-20221112162644-4.png]] | ||
159 | |||
160 | |||
161 | |||
162 | **2. Check the 'Preserver Settings' check box when you upgrade the gateway with the firmware. ** | ||
163 | |||
164 | [[image:image-20221112162543-2.png]] | ||
165 | |||
166 | |||
167 | |||
168 | === **The gateway version is greater or equal to** **lgw~-~-build-v5.4.1668240318-20221112-1606:** === | ||
169 | |||
170 | |||
171 | |||
172 | **~1. Only to do: Check the 'Preserver Settings' check box when you upgrade the gateway with the firmware. ** | ||
173 | |||
174 | [[image:image-20221112162547-3.png]] | ||
175 | |||
176 | |||
177 | == 2.2 How to register hp0d with Remote.it == | ||
178 | |||
179 | |||
180 | (% style="color:blue" %)**Prerequisites:** | ||
181 | |||
182 | Users must have an account and APP for remote.it | ||
183 | |||
184 | **[[https:~~/~~/app.remote.it>>https://app.remote.it]]** | ||
185 | |||
186 | |||
187 | === (% style="color:blue" %)**1. Click "+" in the APP to add a device**(%%) === | ||
188 | |||
189 | |||
190 | Then click Add "Linux & Raspberry Pi" and the APP will generate a command to register the device. | ||
191 | |||
192 | |||
193 | [[image:image-20220815173938-1.jpeg||height="574" width="919"]] | ||
194 | |||
195 | |||
196 | |||
197 | === (% style="color:blue" %)**2. Copy the register device command**(%%) === | ||
198 | |||
199 | |||
200 | [[image:image-20220815173944-2.jpeg||height="556" width="923"]] | ||
201 | |||
202 | |||
203 | |||
204 | === (% style="color:blue" %)**3. Enter the command copied from the previous step on the HP0D Linux command line**(%%) === | ||
205 | |||
206 | |||
207 | [[image:image-20220815173951-3.jpeg||height="424" width="1147"]] | ||
208 | |||
209 | |||
210 | |||
211 | === (% style="color:blue" %)**4. Check whether the device is successfully registered on the Remote.it APP**(%%) === | ||
212 | |||
213 | |||
214 | [[image:image-20220815173958-4.jpeg||height="580" width="964"]] | ||
215 | |||
216 | |||
217 | == 2.3 How to register the gateway with Remote.it via SSH Access for Linux console == | ||
218 | |||
219 | |||
220 | (% style="color:blue" %)**Prerequisites:** | ||
221 | |||
222 | Users must have an account and APP for remote.it | ||
223 | |||
224 | **[[https:~~/~~/app.remote.it>>https://app.remote.it]]** | ||
225 | |||
226 | For detailed examples, please see: **[[OpenWrt How to Connect Guide (remote.it)>>url:https://www.remote.it/getting-started/openwrt]]** | ||
227 | |||
228 | |||
229 | === (% style="color:blue" %)**1. Click "+" in the APP to add a device**(%%) === | ||
230 | |||
231 | |||
232 | Then click Add "OpenWrt" and the APP will generate a command to register the device. | ||
233 | |||
234 | [[image:image-20230320110123-4.png||height="657" width="1191"]] | ||
235 | |||
236 | |||
237 | |||
238 | === (% style="color:blue" %)**2. Copy the register device command**(%%) === | ||
239 | |||
240 | |||
241 | [[image:image-20230320110309-5.png||height="635" width="1197"]] | ||
242 | |||
243 | |||
244 | |||
245 | === (% style="color:blue" %)**3. Enter the command copied from the previous step on the gateway Linux command line**(%%) === | ||
246 | |||
247 | |||
248 | (% class="wikigeneratedid" id="H" %) | ||
249 | [[image:image-20230320105212-1.png||height="758" width="820"]] | ||
250 | |||
251 | |||
252 | |||
253 | === (% style="color:blue" %)**4. Check whether the device is successfully registered on the Remote.it APP**(%%) === | ||
254 | |||
255 | |||
256 | [[image:image-20230320112057-6.png||height="603" width="1135"]] | ||
257 | |||
258 | |||
259 | == 2.4 Trouble Shooting == | ||
260 | |||
261 | |||
262 | === **1. What should users do when gateway Remote.it installation fails** === | ||
263 | |||
264 | |||
265 | [[image:image-20220907162028-4.png||height="564" width="1148"]] | ||
266 | |||
267 | |||
268 | (% style="color:blue" %)**Step 1: **(%%)Users can download the archive and upload it to the gateway:** [[attach:backup.tar.gz||target="_blank"]]** | ||
269 | |||
270 | [[image:image-20220907161050-2.png]] | ||
271 | |||
272 | |||
273 | |||
274 | (% style="color:blue" %)**Step 2: **(%%)Back to the Remote.it screen, and click **"Install"** again. | ||
275 | |||
276 | [[image:image-20220907161352-3.png]] | ||
277 | |||
278 | |||
279 | (% style="color:blue" %)**Step 3:**(%%) Follow the [[Remoteit user instruction for Dragino Gateway>>https://www.remote.it/getting-started/dragino]] steps to reconfigure | ||
280 | |||
281 | |||
282 | = 3. RSSH Introduction = | ||
283 | |||
284 | |||
285 | 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. | ||
286 | |||
287 | (% style="color:red" %)**Important Notice:** | ||
288 | |||
289 | (% class="box warningmessage" %) | ||
290 | ((( | ||
291 | RSSH access will give full control of your device to remote support. Please remove sensitivity info before perform this | ||
292 | This RSSH allow Dragino Support Team to remote access to customer's device. Customer is not able to remote access it via Dragino Server. | ||
293 | |||
294 | If user want to access himself, he need to set up the RSSH server himself. | ||
295 | ))) | ||
296 | |||
297 | |||
298 | **Below gateway support reverse SSH access:** | ||
299 | |||
300 | * Firmware Version > lgw~-~-build-v5.4.1618196981-20210412-1111 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] | ||
301 | * LG01N, OLG01N (Note: LG01-P LG01-S doesn't support) | ||
302 | * LG02, OLG02 | ||
303 | * LG308, DLOS8 | ||
304 | * LPS8 | ||
305 | * LIG16 | ||
306 | * MS14 series if installed with the same firmware. | ||
307 | |||
308 | == 3.1 End User Guide to use SSH access == | ||
309 | |||
310 | |||
311 | Go to this the Reverse SSH page as below: | ||
312 | |||
313 | [[image:image-20231107200442-2.png||height="684" width="973"]] | ||
314 | |||
315 | |||
316 | Get the RSSH configure page | ||
317 | |||
318 | [[image:image-20220531152815-14.png]] | ||
319 | |||
320 | Connection OK. | ||
321 | |||
322 | * (% style="color:#037691" %)**ConnectionType**(%%): Select a type | ||
323 | * (% style="color:#037691" %)**Login ID**(%%): Input the rssh server minimal ssh user | ||
324 | * (% style="color:#037691" %)**Host Address**(%%): Input rssh server public IP address/domain name | ||
325 | * (% style="color:#037691" %)**Connect at Startup**(%%) : Choose to enable connect once the device is powered. | ||
326 | * (% style="color:#037691" %)**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 | ||
327 | |||
328 | 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. | ||
329 | |||
330 | |||
331 | == 3.2 Set Up RSSH Server == | ||
332 | |||
333 | |||
334 | Advance administrator can config a SSH server to provide support their end user themselves., Steps as below | ||
335 | |||
336 | |||
337 | |||
338 | === (% style="color:blue" %)**Step 1 : Download the SSH service code**(%%) === | ||
339 | |||
340 | |||
341 | **1).** git clone [[https:~~/~~/github.com/dragino/rssh-server.git>>url:https://github.com/dragino/rssh-server.git]] rssh-server | ||
342 | |||
343 | [[image:image-20220531150750-5.png]] | ||
344 | |||
345 | |||
346 | **2).** cd rssh-server; sudo make ~-~--> to Generate the execute file:rssh_serv | ||
347 | |||
348 | [[image:image-20220531150811-6.png]] | ||
349 | |||
350 | |||
351 | **Debug** : | ||
352 | |||
353 | ((( | ||
354 | (% class="box" %) | ||
355 | ((( | ||
356 | if you git fail. ~-~-> (% style="color:#037691" %)**sudo: git: command not found**(%%). | ||
357 | please install git. ~-~-> (% style="color:#037691" %)**yum install git -y or apt-get install git -y**(%%). | ||
358 | if you make error 127,it** (% style="color:#037691" %)lack of gcc(%%)**. | ||
359 | please install gcc. ~-~-> (% style="color:#037691" %)**yum install gcc**(%%). | ||
360 | ))) | ||
361 | ))) | ||
362 | |||
363 | [[image:image-20220531151516-7.png]] | ||
364 | |||
365 | |||
366 | ((( | ||
367 | (% class="box" %) | ||
368 | ((( | ||
369 | if you make a fatal error : sqlite3.h,it (% style="color:#037691" %)**lack of sqlite3**(%%). | ||
370 | please insatell sqlite3. | ||
371 | ))) | ||
372 | ))) | ||
373 | |||
374 | [[image:image-20220531151628-8.png]] | ||
375 | |||
376 | |||
377 | (% style="color:blue" %)**How to install Sqlit3:** | ||
378 | |||
379 | (% class="box infomessage" %) | ||
380 | ((( | ||
381 | **~ Step 1:** Download the SQLit3 installation package | ||
382 | sudo wget **[[https:~~/~~/www.sqlite.org/2021/sqlite-autoconf-3350400.tar.gz>>url:https://www.sqlite.org/2021/sqlite-autoconf-3350400.tar.gz]]** | ||
383 | |||
384 | **Step 2: **tar the SQLit3 installation package | ||
385 | sudo tar -zxvf sqlite-autoconf-3350300.tar.gz | ||
386 | |||
387 | **Step 3:** Generate the makefile | ||
388 | cd sqlite-autoconf-3350300/;./configure | ||
389 | |||
390 | **Step 4:** Compile makefile | ||
391 | sudo make | ||
392 | |||
393 | **Step 5:** Install makefile | ||
394 | sudo make install | ||
395 | |||
396 | **Check:** | ||
397 | cd /usr/local/bin;ls -al ~-~-> Check to see if there is a file for sqlite3 | ||
398 | cd sqlite-autoconf-3350300/;./sqlite3 test.db ~-~-> Test whether the sqlite3 was installed successfully | ||
399 | |||
400 | **debug:** | ||
401 | If you get the imformation that is SQLite header and source version mismatch, when you execute./sqlite3 test.db. | ||
402 | Please execute the command /sbin/ldconfig. | ||
403 | After that execute the command ./sqlite3 test.db again. | ||
404 | ))) | ||
405 | |||
406 | |||
407 | |||
408 | === (% style="color:blue" %)**Step 2 : Install and run the RSS service**(%%) === | ||
409 | |||
410 | |||
411 | **1). ** install database for /var/rsshdb.sqlite3 and Server development port for 3721(The default is 3721) | ||
412 | |||
413 | user must enter the root account and run the following commands | ||
414 | |||
415 | (% class="box infomessage" %) | ||
416 | ((( | ||
417 | **$ ./create_sqlite3_db.sh | ||
418 | $ ./rssh_serv -p 3721 2>&1 & | ||
419 | $ ps -ef | grep rssh_serv check 3721 port** | ||
420 | ))) | ||
421 | |||
422 | [[image:image-20220531151958-10.png]] | ||
423 | |||
424 | |||
425 | **Debug:** | ||
426 | |||
427 | {{{ Check /var/rsshdb.sqlite3 --> ls /var/rsshdb.sqlite3 | ||
428 | Check ls /var/rsshdb.sqlite3 --> sudo chmod 777 rssh_serv | ||
429 | }}} | ||
430 | |||
431 | {{{ if fail to open dpvlry or to bind to it | ||
432 | please kill rssh_serv,and run ./rssh_serv -p 3721 2>&1 & again | ||
433 | }}} | ||
434 | |||
435 | |||
436 | |||
437 | === (% style="color:blue" %)**Step 3 : Create a minimal SSH user (reverse SSH proxy for the gateway)**(%%) === | ||
438 | |||
439 | |||
440 | (% class="box infomessage" %) | ||
441 | ((( | ||
442 | **1):** sudo useradd XXXXX (custom user name) | ||
443 | **2):** sudo passwd xxxxxx | ||
444 | **3):** cp /bin/bash /bin/rbash | ||
445 | **4):** sudo nano /etc/passwd ~-~-> Change /bin/bash to /bin/rbash | ||
446 | **5):** sudo nano /home/xxxxx/.bashrc **empty it,and input export PATH=$HOME/bin** | ||
447 | **6):** sudo nano /home/xxxxx/.bash_profile **empty it,and input export PATH=$HOME/bin** | ||
448 | ))) | ||
449 | |||
450 | (% style="color:red" %)**Now user "XXXXX" is the user with limited permissions of the current system** | ||
451 | |||
452 | |||
453 | |||
454 | === (% style="color:blue" %)**Step 4 : Create an authorization key file**(%%) === | ||
455 | |||
456 | |||
457 | **1):** sudo mkdir /home/xxxxx/.ssh; sudo touch /home/xxxxx/.ssh/authorizedkey | ||
458 | |||
459 | |||
460 | **Debug:** | ||
461 | |||
462 | {{{ check: sudo ls /home/xxxxx/.ssh/authorizedkey}}} | ||
463 | |||
464 | |||
465 | == 3.3 How does user get the gateway to connect to a user's private server == | ||
466 | |||
467 | |||
468 | |||
469 | === (% style="color:blue" %)**Step 1 : Come back the gateway web UI to get the gateway Public key**(%%) === | ||
470 | |||
471 | |||
472 | **1)** in the system ~-~-> (% style="color:#037691" %)**Remote Mgmt/span** | ||
473 | |||
474 | [[image:image-20220531152419-11.png]] | ||
475 | |||
476 | |||
477 | |||
478 | === (% style="color:blue" %)**Step 2 : Authorization server**(%%) === | ||
479 | |||
480 | |||
481 | Input the Gateway Publickey into user's private server "/home/XXXXX/.ssh/authorized_keys" file. | ||
482 | |||
483 | [[image:image-20220531152549-12.png]] | ||
484 | |||
485 | |||
486 | |||
487 | === (% style="color:blue" %)**Step 3 : Connect private server**(%%) === | ||
488 | |||
489 | |||
490 | This is same as connect Dragino Support Server but just change the server address to customize server address. | ||
491 | |||
492 | [[image:image-20220531152633-13.png]] | ||
493 | |||
494 | |||
495 | |||
496 | === (% style="color:blue" %)**Step 4 : Check Connection**(%%) === | ||
497 | |||
498 | |||
499 | Rssh Host connection Ok | ||
500 | |||
501 | [[image:image-20220531152815-14.png]] | ||
502 | |||
503 | |||
504 | User can use common ps | grep ssh to check it in the gateway. | ||
505 | |||
506 | [[image:image-20220531152840-15.png]] | ||
507 | |||
508 | |||
509 | |||
510 | === (% style="color:blue" %)**Step 5 : Access the gateway from customized server**(%%) === | ||
511 | |||
512 | |||
513 | Check what gateways link to server. | ||
514 | |||
515 | (% class="box infomessage" %) | ||
516 | ((( | ||
517 | **$ ./connect-gw.sh -l** | ||
518 | ))) | ||
519 | |||
520 | [[image:image-20220531153016-16.png]] | ||
521 | |||
522 | |||
523 | |||
524 | Access the gateway | ||
525 | |||
526 | (% class="box infomessage" %) | ||
527 | ((( | ||
528 | **$ ./connect-gw.sh <GWID>** | ||
529 | ))) | ||
530 | |||
531 | [[image:image-20220531153219-17.png]] |