Changes

138 bytes removed ,  10:19, 3 September 2020
Line 8: Line 8:  
|-
 
|-
 
| style="text-align: left; background: white;" |Change type
 
| style="text-align: left; background: white;" |Change type
| colspan="2" style="text-align: left; background: white;" |1. WebUI and CLI access functionality additional IP and Ports.<br>2. RMS Proxy (access to HTTP(s) devices behind router) will be moved to RMS Connect secion.<br>3. RMS UI layout streamlining.
+
| colspan="2" style="text-align: left; background: white;" |1. WebUI and CLI access functionality additional IP and Ports.<br>2. RMS Proxy (access to HTTP(s) devices behind router) will be moved to RMS Connect secion.<br>
 
|-
 
|-
 
| style="width: 221px; text-align: left; background: white;" |Detailed description
 
| style="width: 221px; text-align: left; background: white;" |Detailed description
| style="width: 908px; text-align: left; background: white;" |1. In order to continue using WebUI access and CLI access functionality following IP address and ports must be made accessible for the router:<br>IP: 18.192.27.240<br>Ports: 20022, 20080, 23389.<br>If you are using Private network, these must be whitelisted by the Internet Service Provider.<br>This change comes in order to greatly enhance and speed up the functionality by utilizing reverse SSH tunneling.<br>2. RMS Proxy functionality becomes a part of RMS Connect package, which allows RDP, VNC or SSH access to devices behind routers via RMS. It will be monetized based on traffic usage.<br>3. General changes to RMS layout reflecting these changes and improving browsing speed.<br>
+
| style="width: 908px; text-align: left; background: white;" |1. In order to continue using WebUI access and CLI access functionality following IP address and ports must be made accessible for the router:<br>IP: 18.192.27.240<br>Ports: 20022, 20080, 23389.<br>If you are using Private network, these must be whitelisted by the Internet Service Provider.<br>This change comes in order to greatly enhance and speed up the functionality by utilizing reverse SSH tunneling.<br>2. RMS Proxy functionality becomes a part of RMS Connect package, which allows RDP, VNC or SSH access to devices behind routers via RMS. It will be monetized based on traffic usage.
 
|-
 
|-
 
| style="text-align: left; background: white;" |Change reasons
 
| style="text-align: left; background: white;" |Change reasons
 
| colspan="2" style="text-align: left; background: white;" |
 
| colspan="2" style="text-align: left; background: white;" |
Major functionality and Utility improvement: RMS Connect, an API, UI changes
+
Major functionality and Utility improvement: RMS Connect, an API
 
|-
 
|-
 
| style="text-align: left; background: white;" |Change implementation date
 
| style="text-align: left; background: white;" |Change implementation date

Navigation menu