31,703
edits
Changes
Template:Networking rut manual usb tools (view source)
Revision as of 16:10, 16 November 2020
, 16:10, 16 November 2020Created page with "{{Template: Networking_rutxxx_manual_fw_disclosure | fw_version = {{{series}}}_R_00.06.07 }} ==Summary== This chapter is an overview of the <b>USB Tools</b> service in RUT955..."
{{Template: Networking_rutxxx_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.06.07
}}
==Summary==
This chapter is an overview of the <b>USB Tools</b> service in RUT955 routers.
{{Template:Networking_rutos_manual_package_disclosure
| name = {{{name}}}
| series = {{{series}}}
| package = USB Tools
}}
==Network Shares==
The <b>Network Shares</b> section is used to manage Network-attached storage (NAS) such as USB drives, SD cards and hard drives. The router supports the following file system architectures:
<ul>
<li><b>FAT32</b><span class="asterisk">*</span></li>
<li><b>NTFS</b><span class="asterisk">**</span></li>
</ul>
<span class="asterisk">*</span> supports SD cards with a capacity of up to <b>32 GB</b><br>
<span class="asterisk">**</span> NTFS support available from FW version <b>RUT9XX_R_00.05.02</b> and newer
===Mounted File Systems===
----
The <b>Mounted File Systems</b> tab displays information on mounted USB drives and SD cards. To view an attached drive, connect it to the router and click the Refresh button:
[[File:Rut955 webui services usb tools network shares mounted file systems v2.png]]
<table class="nd-othertables">
<tr>
<th style="width: 250px">field name</th>
<th style="width: 1450px">description</th>
</tr>
<tr>
<td>Filesystem</td>
<td>Name of the Linux filesystem. For better clarity, lets take a closer look at the filesystem name from the example above:
<ul>
<li><b>/dev</b> - the directory of device files. Everything in the Linux filesystem is either a file or a directory; /dev is the location of device files. Every device is represented by a file in the /dev directory</li>
<li><b>sd</b> - identifies block devices<span class="asterisk">*</span> (capable of carrying data)</li>
<li><b>a</b> - the letter immediately after sd signifies the order in which the device was first found (a, b, c, ...)</li>
<li><b>1</b> - signifies the partition on the device</li>
</ul>So the full string <b>/dev/sda1</b> denotes the first partition of the first block device<br><span class="asterisk">*</span> SD cards will be identified as MultiMediaCard (MMC) devices and the identifier will begin with the <b>mmcblk</b> string instead of sd
</td>
</tr>
<tr>
<td>Mount Point</td>
<td>A mount point is a directory in the currently accessible filesystem on which an additional filesystem is mounted (i.e., logically attached). The <b>/mnt</b> directory and its subdirectories are intended for use as the temporary mount points for mounting storage devices. The mount point becomes the root directory of the newly added filesystem, and that filesystem becomes accessible from that directory</td>
</tr>
<tr>
<td>Available</td>
<td>Amount of available memory in the mounted drive. This column also displays the total capacity of the drive</td>
</tr>
<tr>
<td>Used</td>
<td>Amount of used memory in the mounted drive</td>
</tr>
<tr>
<td>Safely Remove Disk</td>
<td>Unmounts the drive so that it becomes safe to disconnect from the router</td>
</tr>
</table>
====SSH commands====
----
Devices can be mounted or unmounted manually by using SSH commands.
=====Mounting=====
----
The <b>mount</b> command attaches a filesystem to the file hierarchy. The basic syntax for the command is:
mount -t type device dir
Where:
<ul>
<li><b>-t</b> - the filesystem type. If this value is omitted, the command will try to determine the type automatically</li>
<li><b>device</b> - file name of the device. Refer to section [[RUT955_USB_Tools#Mounted_File_Systems|2.1]] for examples</li>
<li><b>dir</b> - directory that will be used as the mount point for the device. Refer to section [[RUT955_USB_Tools#Mounted_File_Systems|2.1]] for examples</li>
</ul>
<b>Example command</b>:
mount -t ntfs /dev/sda1 /mnt/sda1
=====Unmounting=====
----
The <b>umount</b> command detaches filesystem from the file hierarchy. The basic syntax for the command is:
umount device
<b>Example command</b>:
umount /dev/sda1
Using the umount command is analogous to clicking the "Safely Remove Disk" button. Therefore, the attached drive can be safely disconnected after using umount to detach it.
===Samba===
----
<b>Samba</b> is a software solution for using the Server Message Block (SMB) networking protocol, which provides shared file access between nodes on a computer network. The Samba tab in RUT955's WebUI is used to configure network access (look to section [[RUT955_USB_Tools#Shared_Directories|2.2.1]] for details) to storage devices connected to the router's MicroSD slot or USB connector.
[[File:Rut955 webui services usb tools network shares samba v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns Samba on or off.</td>
</tr>
<tr>
<td>Hostname</td>
<td>string; default: <b>Router_share</b></td>
<td>Name of the Samba server.</td>
</tr>
<tr>
<td>Description</td>
<td>string; default: <b>Router_share</b></td>
<td>Short description about the Same server.</td>
</tr>
<tr>
<td>Workgroup</td>
<td>string; default: <b>WORKGROUP</b></td>
<td>Name of the server's workgroup.</td>
</tr>
</table>
====Shared Directories====
----
The <b>Shared Directories</b> section is used to configure access to connected storage drives or individual directories contained in those drives. A shared directory must be added before it can be configured:
[[File:Rut955 webui services usb tools network shares samba shared directories v2.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>none</b></td>
<td>Name of a shared directory.</td>
</tr>
<tr>
<td>Path</td>
<td>filepath; default: <b>/mnt/</b></td>
<td>Path to a shared directory. To share an entire drive, choose an automatically generated path from this drop-down box (for example, /mnt/sda1). To share a specific directory on the drive, specify the full path to that directory (for example, /mnt/sda1/shared/video).</td>
</tr>
<tr>
<td>Allow guests</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns guest access on or off. Guest access allows anonymous connections to a Shared Directory.</td>
</tr>
<tr>
<td>Allowed users</td>
<td>samba user(s); default: <b>none</b></td>
<td>Samba user(s) that are permitted to access a Shared Directory. Users can be created from the Samba Users section.</td>
</tr>
<tr>
<td>Read-only</td>
<td>yes | no; default: <b>no</b></td>
<td>Makes a Shared Directory read-only, which means the directory can only be accessed to view and read files (not write).</td>
</tr>
<tr>
<td>Delete</td>
<td>-(interactive button)</td>
<td>Deletes a Shared Directory configuration.</td>
</tr>
</table>
===Samba Users===
----
<b>Samba users</b> are users that can be granted access to shared directories (as described in section [[#Shared_Directories|2.2.1]]. To add a new user, enter a custom username and password and click the 'Add' button:
[[File:Rut955 webui services usb tools network shares samba users v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Username</td>
<td>string; default: <b>none</b></td>
<td>Custom name for a new Samba user.</td>
</tr>
<tr>
<td>Password</td>
<td>string; default: <b>none</b></td>
<td>Password for a new Samba user.</td>
</tr>
</table>
==Printer Server==
The <b>Printer Server</b> provides the possibility to configure access to a printer that is connected to the USB port of the RUT955 device. The Add button lets you add and manage additional printers. To configure a printer instance, click the Edit button located next to it:
[[File:Rut955 webui services usb tools printer server v2.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns USB printer support on or off.</td>
</tr>
<tr>
<td>Device</td>
<td>filepath; default: <b>/dev/usb/lp0</b></td>
<td>Printer's device file.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [9100..9109]; default: <b>9100</b></td>
<td>Printer's TCP port.</td>
</tr>
<tr>
<td>Bidirectional mode</td>
<td>off | on; default: <b>on</b></td>
<td>Turns bidirectional mode on or off.</td>
</tr>
</table>
For step-by-step instructions on how to use a printer with RUT955, <b>[[How to set up a printer (Windows)|click here]]</b>
==USB to Serial==
The router's USB connector can also be used as a serial port. The only type of serial connection available via USB is Over IP.
{{Template: webui_services_rs232_rs232_configuration_over_ip}}
[[File:Rut955 webui services usb tools usb tools configuration serial type over ip v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns the USB to Serial service on or off.</td>
</tr>
<tr>
<td>Baud rate</td>
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: <b>115200</b></td>
<td>Data rate for serial data transmission (in bits per second).</td>
</tr>
<tr>
<td>Data bits</td>
<td>5 | 6 | 7 | 8; default: <b>8</b></td>
<td>Number of data bits for each character</td>
</tr>
<tr>
<td>Parity</td>
<td>None | Odd | Even; default: <b>None</b></td>
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<ul>
<li><b>None</b> (<b>N</b>) - no parity method is used</li>
<li><b>Odd</b> (<b>O</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.</li>
<li><b>Even</b> (<b>E</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li>
</ul>
</td>
</tr>
<tr>
<td>Stop bits</td>
<td>1 | 2; default: <b>1</b></td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
</tr>
<tr>
<td>Flow control</td>
<td>None | RTS/CTS | Xon/Xoff; default: <b>None</b></td>
<td>In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking.
<ul>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.
</ul>
</td>
</tr>
<tr>
<td>Serial type</td>
<td>Over IP; default: <b>Over IP</b></td>
<td>Specifies the serial connection type.</td>
</tr>
<tr>
<td>Protocol</td>
<td>TCP; default: <b>TCP</b></td>
<td>Protocol used in the communication process</td>
</tr>
<tr>
<td>Mode</td>
<td><span style="color: purple;">Server</span> | <span style="color: red;">Client</span> | <span style="color: blue;">Bidirect</span<; default: <b>Server</b></td>
<td>Device's role in the connection:
<ul>
<li><b>Server</b> - the device waits for incoming connections</li>
<li><b>Client</b> - the device initiates the connection</li>
<li><b>Bidirect</b> - acts as client by default but waits for incoming connections at the same time</li>
</ul>
</td>
</tr>
<tr>
<td>No leading zeros</td>
<td>yes | no; default: <b>no</b></td>
<td>When checked, indicates that the first hex zeros should be skipped</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: Server address</td>
<td>ip | host; default: <b>none</b></td>
<td>IP address or hostname of the server that the client will connect to</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: TCP port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Server's port number</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: Reconnect interval (s)</td>
<td>integer; default: <b>none</b></td>
<td>Time period (in seconds) between reconnection attempts in case a connection fails</td>
</tr>
<tr>
<td><span style="color: purple;">Server settings</span>: TCP port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Internal TCP port number used to listen for incoming connections </td>
</tr>
<tr>
<td><span style="color: purple;">Server settings</span>: Timeout (s)</td>
<td>integer; default: <b>none</b></td>
<td>Disconnects clients after they remain inactive for an amount time (in seconds) specified in this field</td>
</tr>
<tr>
<td><span style="color: blue;">Output</span></td>
<td>OC Output | Relay Output; default: <b>OC Output</b></td>
<td>Output to indicate that the application switched from client (default) to server state (this field becomes visible only in Bidirect mode)</td>
</tr>
<tr>
<td><span style="color: blue;">Output state</span></td>
<td>1 | 0; default: <b>0</b></td>
<td>Output state value during which the application reverts to server mode (this field becomes visible only in Bidirect mode)</td>
</tr>
</table>
==USB Modem==
<b>[[How to set up a USB modem|Click here]]</b> for step-by-step USB modem set up instructions.
{{{name}}} devices are compatible with the following USB modems:
<ul>
<li>Huawei MS2131i-8</li>
</ul>
[[Category:RUT955 Services section]]
| fw_version = {{{series}}}_R_00.06.07
}}
==Summary==
This chapter is an overview of the <b>USB Tools</b> service in RUT955 routers.
{{Template:Networking_rutos_manual_package_disclosure
| name = {{{name}}}
| series = {{{series}}}
| package = USB Tools
}}
==Network Shares==
The <b>Network Shares</b> section is used to manage Network-attached storage (NAS) such as USB drives, SD cards and hard drives. The router supports the following file system architectures:
<ul>
<li><b>FAT32</b><span class="asterisk">*</span></li>
<li><b>NTFS</b><span class="asterisk">**</span></li>
</ul>
<span class="asterisk">*</span> supports SD cards with a capacity of up to <b>32 GB</b><br>
<span class="asterisk">**</span> NTFS support available from FW version <b>RUT9XX_R_00.05.02</b> and newer
===Mounted File Systems===
----
The <b>Mounted File Systems</b> tab displays information on mounted USB drives and SD cards. To view an attached drive, connect it to the router and click the Refresh button:
[[File:Rut955 webui services usb tools network shares mounted file systems v2.png]]
<table class="nd-othertables">
<tr>
<th style="width: 250px">field name</th>
<th style="width: 1450px">description</th>
</tr>
<tr>
<td>Filesystem</td>
<td>Name of the Linux filesystem. For better clarity, lets take a closer look at the filesystem name from the example above:
<ul>
<li><b>/dev</b> - the directory of device files. Everything in the Linux filesystem is either a file or a directory; /dev is the location of device files. Every device is represented by a file in the /dev directory</li>
<li><b>sd</b> - identifies block devices<span class="asterisk">*</span> (capable of carrying data)</li>
<li><b>a</b> - the letter immediately after sd signifies the order in which the device was first found (a, b, c, ...)</li>
<li><b>1</b> - signifies the partition on the device</li>
</ul>So the full string <b>/dev/sda1</b> denotes the first partition of the first block device<br><span class="asterisk">*</span> SD cards will be identified as MultiMediaCard (MMC) devices and the identifier will begin with the <b>mmcblk</b> string instead of sd
</td>
</tr>
<tr>
<td>Mount Point</td>
<td>A mount point is a directory in the currently accessible filesystem on which an additional filesystem is mounted (i.e., logically attached). The <b>/mnt</b> directory and its subdirectories are intended for use as the temporary mount points for mounting storage devices. The mount point becomes the root directory of the newly added filesystem, and that filesystem becomes accessible from that directory</td>
</tr>
<tr>
<td>Available</td>
<td>Amount of available memory in the mounted drive. This column also displays the total capacity of the drive</td>
</tr>
<tr>
<td>Used</td>
<td>Amount of used memory in the mounted drive</td>
</tr>
<tr>
<td>Safely Remove Disk</td>
<td>Unmounts the drive so that it becomes safe to disconnect from the router</td>
</tr>
</table>
====SSH commands====
----
Devices can be mounted or unmounted manually by using SSH commands.
=====Mounting=====
----
The <b>mount</b> command attaches a filesystem to the file hierarchy. The basic syntax for the command is:
mount -t type device dir
Where:
<ul>
<li><b>-t</b> - the filesystem type. If this value is omitted, the command will try to determine the type automatically</li>
<li><b>device</b> - file name of the device. Refer to section [[RUT955_USB_Tools#Mounted_File_Systems|2.1]] for examples</li>
<li><b>dir</b> - directory that will be used as the mount point for the device. Refer to section [[RUT955_USB_Tools#Mounted_File_Systems|2.1]] for examples</li>
</ul>
<b>Example command</b>:
mount -t ntfs /dev/sda1 /mnt/sda1
=====Unmounting=====
----
The <b>umount</b> command detaches filesystem from the file hierarchy. The basic syntax for the command is:
umount device
<b>Example command</b>:
umount /dev/sda1
Using the umount command is analogous to clicking the "Safely Remove Disk" button. Therefore, the attached drive can be safely disconnected after using umount to detach it.
===Samba===
----
<b>Samba</b> is a software solution for using the Server Message Block (SMB) networking protocol, which provides shared file access between nodes on a computer network. The Samba tab in RUT955's WebUI is used to configure network access (look to section [[RUT955_USB_Tools#Shared_Directories|2.2.1]] for details) to storage devices connected to the router's MicroSD slot or USB connector.
[[File:Rut955 webui services usb tools network shares samba v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns Samba on or off.</td>
</tr>
<tr>
<td>Hostname</td>
<td>string; default: <b>Router_share</b></td>
<td>Name of the Samba server.</td>
</tr>
<tr>
<td>Description</td>
<td>string; default: <b>Router_share</b></td>
<td>Short description about the Same server.</td>
</tr>
<tr>
<td>Workgroup</td>
<td>string; default: <b>WORKGROUP</b></td>
<td>Name of the server's workgroup.</td>
</tr>
</table>
====Shared Directories====
----
The <b>Shared Directories</b> section is used to configure access to connected storage drives or individual directories contained in those drives. A shared directory must be added before it can be configured:
[[File:Rut955 webui services usb tools network shares samba shared directories v2.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>none</b></td>
<td>Name of a shared directory.</td>
</tr>
<tr>
<td>Path</td>
<td>filepath; default: <b>/mnt/</b></td>
<td>Path to a shared directory. To share an entire drive, choose an automatically generated path from this drop-down box (for example, /mnt/sda1). To share a specific directory on the drive, specify the full path to that directory (for example, /mnt/sda1/shared/video).</td>
</tr>
<tr>
<td>Allow guests</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns guest access on or off. Guest access allows anonymous connections to a Shared Directory.</td>
</tr>
<tr>
<td>Allowed users</td>
<td>samba user(s); default: <b>none</b></td>
<td>Samba user(s) that are permitted to access a Shared Directory. Users can be created from the Samba Users section.</td>
</tr>
<tr>
<td>Read-only</td>
<td>yes | no; default: <b>no</b></td>
<td>Makes a Shared Directory read-only, which means the directory can only be accessed to view and read files (not write).</td>
</tr>
<tr>
<td>Delete</td>
<td>-(interactive button)</td>
<td>Deletes a Shared Directory configuration.</td>
</tr>
</table>
===Samba Users===
----
<b>Samba users</b> are users that can be granted access to shared directories (as described in section [[#Shared_Directories|2.2.1]]. To add a new user, enter a custom username and password and click the 'Add' button:
[[File:Rut955 webui services usb tools network shares samba users v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Username</td>
<td>string; default: <b>none</b></td>
<td>Custom name for a new Samba user.</td>
</tr>
<tr>
<td>Password</td>
<td>string; default: <b>none</b></td>
<td>Password for a new Samba user.</td>
</tr>
</table>
==Printer Server==
The <b>Printer Server</b> provides the possibility to configure access to a printer that is connected to the USB port of the RUT955 device. The Add button lets you add and manage additional printers. To configure a printer instance, click the Edit button located next to it:
[[File:Rut955 webui services usb tools printer server v2.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns USB printer support on or off.</td>
</tr>
<tr>
<td>Device</td>
<td>filepath; default: <b>/dev/usb/lp0</b></td>
<td>Printer's device file.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [9100..9109]; default: <b>9100</b></td>
<td>Printer's TCP port.</td>
</tr>
<tr>
<td>Bidirectional mode</td>
<td>off | on; default: <b>on</b></td>
<td>Turns bidirectional mode on or off.</td>
</tr>
</table>
For step-by-step instructions on how to use a printer with RUT955, <b>[[How to set up a printer (Windows)|click here]]</b>
==USB to Serial==
The router's USB connector can also be used as a serial port. The only type of serial connection available via USB is Over IP.
{{Template: webui_services_rs232_rs232_configuration_over_ip}}
[[File:Rut955 webui services usb tools usb tools configuration serial type over ip v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; default: <b>no</b></td>
<td>Turns the USB to Serial service on or off.</td>
</tr>
<tr>
<td>Baud rate</td>
<td>300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | 57600 | 115200; default: <b>115200</b></td>
<td>Data rate for serial data transmission (in bits per second).</td>
</tr>
<tr>
<td>Data bits</td>
<td>5 | 6 | 7 | 8; default: <b>8</b></td>
<td>Number of data bits for each character</td>
</tr>
<tr>
<td>Parity</td>
<td>None | Odd | Even; default: <b>None</b></td>
<td>In serial transmission, parity is a method of detecting errors. An extra data bit is sent with each data character, arranged so that the number of 1 bits in each character, including the parity bit, is always odd or always even. If a byte is received with the wrong number of 1s, then it must have been corrupted. However, an even number of errors can pass the parity check.
<ul>
<li><b>None</b> (<b>N</b>) - no parity method is used</li>
<li><b>Odd</b> (<b>O</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be odd.</li>
<li><b>Even</b> (<b>E</b>) - the parity bit is set so that the number of "logical ones (1s)" has to be even.</li>
</ul>
</td>
</tr>
<tr>
<td>Stop bits</td>
<td>1 | 2; default: <b>1</b></td>
<td>Stop bits sent at the end of every character allow the receiving signal hardware to detect the end of a character and to resynchronise with the character stream. Electronic devices usually use one stop bit. Two stop bits are required if slow electromechanical devices are used.</td>
</tr>
<tr>
<td>Flow control</td>
<td>None | RTS/CTS | Xon/Xoff; default: <b>None</b></td>
<td>In many circumstances a transmitter might be able to send data faster than the receiver is able to process it. To cope with this, serial lines often incorporate a "handshaking" method, usually distinguished between hardware and software handshaking.
<ul>
<li><b>RTS/CTS</b> - hardware handshaking. RTS and CTS are turned OFF and ON from alternate ends to control data flow, for instance when a buffer is almost full.</li>
<li><b>Xon/Xoff</b> - software handshaking. The Xon and Xoff characters are sent by the receiver to the sender to control when the sender will send data, i.e., these characters go in the opposite direction to the data being sent. The circuit starts in the "sending allowed" state. When the receiver's buffers approach capacity, the receiver sends the Xoff character to tell the sender to stop sending data. Later, after the receiver has emptied its buffers, it sends an Xon character to tell the sender to resume transmission.
</ul>
</td>
</tr>
<tr>
<td>Serial type</td>
<td>Over IP; default: <b>Over IP</b></td>
<td>Specifies the serial connection type.</td>
</tr>
<tr>
<td>Protocol</td>
<td>TCP; default: <b>TCP</b></td>
<td>Protocol used in the communication process</td>
</tr>
<tr>
<td>Mode</td>
<td><span style="color: purple;">Server</span> | <span style="color: red;">Client</span> | <span style="color: blue;">Bidirect</span<; default: <b>Server</b></td>
<td>Device's role in the connection:
<ul>
<li><b>Server</b> - the device waits for incoming connections</li>
<li><b>Client</b> - the device initiates the connection</li>
<li><b>Bidirect</b> - acts as client by default but waits for incoming connections at the same time</li>
</ul>
</td>
</tr>
<tr>
<td>No leading zeros</td>
<td>yes | no; default: <b>no</b></td>
<td>When checked, indicates that the first hex zeros should be skipped</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: Server address</td>
<td>ip | host; default: <b>none</b></td>
<td>IP address or hostname of the server that the client will connect to</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: TCP port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Server's port number</td>
</tr>
<tr>
<td><span style="color: red;">Client settings</span>: Reconnect interval (s)</td>
<td>integer; default: <b>none</b></td>
<td>Time period (in seconds) between reconnection attempts in case a connection fails</td>
</tr>
<tr>
<td><span style="color: purple;">Server settings</span>: TCP port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>Internal TCP port number used to listen for incoming connections </td>
</tr>
<tr>
<td><span style="color: purple;">Server settings</span>: Timeout (s)</td>
<td>integer; default: <b>none</b></td>
<td>Disconnects clients after they remain inactive for an amount time (in seconds) specified in this field</td>
</tr>
<tr>
<td><span style="color: blue;">Output</span></td>
<td>OC Output | Relay Output; default: <b>OC Output</b></td>
<td>Output to indicate that the application switched from client (default) to server state (this field becomes visible only in Bidirect mode)</td>
</tr>
<tr>
<td><span style="color: blue;">Output state</span></td>
<td>1 | 0; default: <b>0</b></td>
<td>Output state value during which the application reverts to server mode (this field becomes visible only in Bidirect mode)</td>
</tr>
</table>
==USB Modem==
<b>[[How to set up a USB modem|Click here]]</b> for step-by-step USB modem set up instructions.
{{{name}}} devices are compatible with the following USB modems:
<ul>
<li>Huawei MS2131i-8</li>
</ul>
[[Category:RUT955 Services section]]
