Changes

no edit summary
Line 113: Line 113:  
===Console===
 
===Console===
 
----
 
----
<b>Console</b> requires no further configuration than the settings above and is used as a direct-access method to the device's shell interface. For this purpose you may use such applications as PuTTY on Windows and microcom, minicom, picocom or similar applications on Linux.
+
<b>Console</b> mode requires no further configuration than the settings above and is used as a direct-access method to the device's shell interface. For this purpose you may want use such applications as PuTTY on Windows and microcom, minicom, picocom or similar applications on Linux.
    
[[File:Networking_rutos_manual_usb_tools_usb_to_serial_console_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_usb_tools_usb_to_serial_console_v1.png|border|class=tlt-border]]
Line 137: Line 137:  
     <td>Mode</td>
 
     <td>Mode</td>
 
         <td><span style="color: red;">Server</span> | <span style="color: purple;">Client</span> | Bidirect; default: <b>Server</b></td>
 
         <td><span style="color: red;">Server</span> | <span style="color: purple;">Client</span> | Bidirect; default: <b>Server</b></td>
         <td>Device's role in the connection:
+
         <td>This device's role in the connection:
 
             <ul>
 
             <ul>
 
                 <li><b>Server</b> - the device waits for incoming connections.</li>
 
                 <li><b>Server</b> - the device waits for incoming connections.</li>
Line 159: Line 159:  
         <td>integer; default: <b>none</b></td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>Specifies an inactivity time limit (in second) after which an inactive clients is disconnected.</td>
 
         <td>Specifies an inactivity time limit (in second) after which an inactive clients is disconnected.</td>
 +
    </tr>
 +
    <tr>
 +
    <td><span style="color: red;">Server settings</span>: Open port automatically</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Automatically adds a traffic rule in the firewall configuration to open the required port for NTRIP communication.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td><span style="color: purple;">Client settings</span>: Server Address</td>
 
       <td><span style="color: purple;">Client settings</span>: Server Address</td>
 
       <td>ip | host; default: <b>none</b></td>
 
       <td>ip | host; default: <b>none</b></td>
       <td>IP address or hostname of the server that the client will connect to.</td>
+
       <td>IP address or hostname of the server that this client will connect to.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 174: Line 179:  
         <td>integer; default: <b>none</b></td>
 
         <td>integer; default: <b>none</b></td>
 
         <td>Time period (in seconds) between reconnection attempts in case a connection fails.</td>
 
         <td>Time period (in seconds) between reconnection attempts in case a connection fails.</td>
    </tr>
  −
    <tr>
  −
    <td>Open port automatically</td>
  −
        <td>off | on; default: <b>on</b></td>
  −
        <td>Automatically adds a traffic rule in the firewall configuration to open the required port for serial communication.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 190: Line 190:  
===Modbus gateway===
 
===Modbus gateway===
 
----
 
----
The <b>Modbus gateway</b> serial type allows redirecting TCP data coming to a specified port to RTU specified by the Slave ID. The Slave ID can be specified by the user or be obtained directly from the Modbus header.
+
The <b>Modbus gateway</b> serial type allows redirecting TCP data coming to a specified port to an RTU specified by the Slave ID. The Slave ID can be specified by the user or be obtained directly from the Modbus header.
    
[[File:Networking_rutos_manual_usb_tools_usb_to_serial_modbus_gateway_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_usb_tools_usb_to_serial_modbus_gateway_v1.png|border|class=tlt-border]]
Line 203: Line 203:  
       <td>Listening IP</td>
 
       <td>Listening IP</td>
 
       <td>ip; default: <b>0.0.0.0</b></td>
 
       <td>ip; default: <b>0.0.0.0</b></td>
       <td>IP address to listen for incoming connections.</td>
+
       <td>IP address to listen for incoming connections. The default value (<i>0.0.0.0</i>) means that this device will listen for incoming connections on any interface or IP address.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Port</td>
 
       <td>Port</td>
       <td>integer [0..65535]; default: <b>none</b></td>
+
       <td>integer [0..65535]; default: <b>502</b></td>
 
       <td>Port number to listen for incoming connections.</td>
 
       <td>Port number to listen for incoming connections.</td>
 
     </tr>
 
     </tr>
Line 223: Line 223:  
     <td>Open port automatically</td>
 
     <td>Open port automatically</td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>off | on; default: <b>on</b></td>
         <td>Automatically adds a traffic rule in the firewall configuration to open the required port for serial communication.</td>
+
         <td>Automatically adds a traffic rule in the firewall configuration to open the required port for serial communication.<br><b><u>Caution:</u></b> use with care if listening IP is left as the default value (<i>0.0.0.0</i>). Leaving it as such will leave the device open for remote connections on the specified port.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>

Navigation menu