|
|
| (2 intermediate revisions by the same user not shown) |
| Line 446: |
Line 446: |
| </table> | | </table> |
|
| |
|
| <b>IP Block Settings</b>
| | ====IP Block Settings==== |
| ---- | | ---- |
| <b>IP Block Settings</b> can be found by pressing 'Settings' button under security tab:
| |
|
| |
| [[File:Networking rutos manual administration access control security settings ipblock button.png|border|class=tlt-border]]
| |
|
| |
|
| [[File:Networking rutos manual administration access control security settings ipblock.png|border|class=tlt-border]] | | [[File:Networking rutos manual administration access control security settings ipblock.png|border|class=tlt-border]] |
| Line 481: |
Line 478: |
| </table> | | </table> |
|
| |
|
| {{#switch:{{{series}}}|TAP100|TAP200= ===Device Pairing===
| |
| ----
| |
| [[File:Networking_rutos_manual_administration_access_control_pairing_v3.png|border|class=tlt-border]]
| |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Enable</td>
| |
| <td>off {{!}} on; default: <b>on</b></td>
| |
| <td>Enable or disable device pairing.</td>
| |
| </tr>
| |
| </table>|#default=}}
| |
|
| |
| {{#switch:{{{series}}}|TAP100|TAP200=|#default=
| |
| ==Recipients==
| |
|
| |
| The <b>Recipients</b> section is used to configure{{#ifeq:{{{mobile}}}|0| | phone groups and }}email
| |
| users, which can later be used along with{{#ifeq:{{{mobile}}}|0| | SMS or }}email related
| |
| services{{#ifeq:{{{events_reporting}}}|0|.|, such as [[{{{name}}} Events Reporting|Events Reporting]].}}
| |
|
| |
| {{#ifeq:{{{mobile}}}|0||
| |
| ===Phone Groups===
| |
| ----
| |
| A <b>Phone Group</b> is a collection of phone numbers that can be used as the recipient in SMS & call related services instead of specifying every number individually. The phone group list is empty by default thus, you must first add at least one new group before you can add phone numbers to it. To create and begin editing a phone group, follow these steps:
| |
|
| |
| <ol>
| |
| <li>Enter a custom name for the phone group into the 'Name' field.</li>
| |
| <li>Click the 'Add' button.</li>
| |
| </ol>
| |
|
| |
| [[File:Networking_rutos_manual_administration_recipients_phone_groups_add_button.png|border|class=tlt-border]]
| |
|
| |
| After clicking 'Edit' you should be redirected to that phone group's configuration page where you can start adding phone numbers to it.
| |
|
| |
| [[File:Networking_rutos_manual_administration_recipients_phone_groups_modify_phone_group_v2.png|border|class=tlt-border]]
| |
|
| |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Group name</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Name of this phone numbers group.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Phone number</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>A phone number entry for this group. Numbers that consist of <i>0-9*+#</i> characters are accepted. Click the plus symbol to add more entries.</td>
| |
| </tr>
| |
| </table>
| |
|
| |
| ===Email Users===
| |
| ----
| |
| When email related services{{#ifeq:{{{events_reporting}}}|0| | (such as [[{{{name}}} Events Reporting|Events Reporting]]) }}are used, the device logs in to the specified email account and reads the inbox (e.g., Email to SMS) or sends out a message (e.g., SMS to Email) depending on the configured service. In this context, an <b>Email Account</b> is an configuration instance that contains the necessary data required in order to log into an email account.
| |
|
| |
| The email accounts list is empty by default thus, you must first add at least one new account before you can configure it. To create and begin editing an email account, follow these steps:
| |
|
| |
| <ol>
| |
| <li>Enter a custom name for the email account into the 'Name' field.</li>
| |
| <li>Click the 'Add' button.</li>
| |
| </ol>
| |
|
| |
| [[File:Networking_rutos_manual_administration_recipients_email_accounts_groups_add_button_v1.png|border|class=tlt-border]]
| |
|
| |
| After clicking 'Add' you should be redirected to that email account's settings page where you can start configuring the account.
| |
|
| |
| [[File:Networking_rutos_manual_administration_recipients_email_accounts_modify_email_account_v3.png|border|class=tlt-border]]
| |
|
| |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Secure connection</td>
| |
| <td>off {{!}} on; default: <b>off</b></td>
| |
| <td>Use if your SMTP server supports TLS or SSL encryption.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>SMTP server</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Name of the email service provider's SMTP server.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>SMTP server port</td>
| |
| <td>integer [0..65535]; default: <b>none</b></td>
| |
| <td>Port of the email service provider's SMTP server.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Credentials</td>
| |
| <td>off {{!}} <span style="color: blue;">on</span>; default: <b>off</b></td>
| |
| <td>This options allows you to set username and password of email account.</td>
| |
| </tr>
| |
| <tr>
| |
| <td><span style="color: blue;">Username</span></td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Username for authentication on SMTP (Simple Mail Transfer Protocol) server. All characters are allowed except `' and space.</td>
| |
| </tr>
| |
| <tr>
| |
| <td><span style="color: blue;">Password</span></td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Password for authentication on SMTP (Simple Mail Transfer Protocol) server. All characters are allowed except `' and space.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Sender's email address</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>An address that will be used to send your email from. Allowed characters (a-zA-Z0-9._%+-@).</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Do not verify authenticity</td>
| |
| <td><span style="color: red;">off</span> {{!}} on; default: <b>off</b></td>
| |
| <td>When enabled peer's certificate authenticity will not be verified.</td>
| |
| </tr>
| |
| <tr>
| |
| <td><span style="color: red;">Server's CA file</span></td>
| |
| <td> - (interactive button)</td>
| |
| <td>Upload server's CA file.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Send test email</td>
| |
| <td> - (interactive button)</td>
| |
| <td> Sends an email based on the current configuration. This is used to test whether the configuration works as intended.</td>
| |
| </tr>
| |
| </table>}}}}
| |
|
| |
| {{#switch:{{{series}}}|TAP100|TAP200=|#default=
| |
| ==Certificates== | | ==Certificates== |
|
| |
|
| The <b>Certificates</b> page is used for convenient TLS certificate and key generation and management. Generated files can be exported and used on other machines or locally on this device with functions that use TLS/SSL, such as {{#ifeq:{{{mqtt}}}|0||[[{{{name}}} MQTT|MQTT]], }}[[{{{name}}} VPN#OpenVPN|OpenVPN]], [[{{{name}}} VPN#IPsec|IPsec]] and others. | | The <b>Certificates</b> page is used for convenient TLS certificate and key generation and management. Generated files can be exported and used on other machines or locally on this device with functions that use TLS/SSL. |
|
| |
|
| ===Certificate Generation=== | | ===Certificate Generation=== |
| Line 871: |
Line 735: |
| The <b>Root CA</b> section is used to add a root CA certificate file to the device. There is a default file already preloaded on the device which will be overwritten by any uploaded file. The certificates must be in .pem format, maximum file size is 10 KB. These certificates are only needed if you want to use HTTPS for your services and the default file should be sufficient in most cases. | | The <b>Root CA</b> section is used to add a root CA certificate file to the device. There is a default file already preloaded on the device which will be overwritten by any uploaded file. The certificates must be in .pem format, maximum file size is 10 KB. These certificates are only needed if you want to use HTTPS for your services and the default file should be sufficient in most cases. |
|
| |
|
| [[File:Networking_rutos_manual_administration_access_control_root_ca_v2.png|border|class=tlt-border]]}} | | [[File:Networking_rutos_manual_administration_access_control_root_ca_v2.png|border|class=tlt-border]] |
|
| |
|
| ==Profiles== | | ==Profiles== |
|
| |
|
| {{Template: Networking_rutos_manual_profiles | series = {{{series}}} | name = {{{name}}}}} | | {{Template: Networking_rutos_manual_profiles | series = {{{series}}} | name = {{{name}}}}} |
|
| |
| {{#switch:{{{series}}}|TAP100|TAP200=|#default=
| |
| ==Storage Memory Expansion==
| |
|
| |
| {{#ifeq:{{{usb}}}| 1 |
| |
| ===USB===
| |
| ----
| |
| The <b>Storage Memory Expansion</b> function provides the possibility to expand the device's flash memory with a USB mass storage device.
| |
|
| |
| ====Memory Expansion====
| |
| ----
| |
| You can <b>expand the flash memory</b> of this device with a USB Mass Storage Device (MSD) and use the extra memory to install additional software packages. This section provides instruction on how to do just that. However, there are a few prerequisites and warnings to take note of before using memory expansion.
| |
|
| |
| To be eligible for memory expansion, the USB MSD must meet the following restrictions.
| |
|
| |
| <ul>
| |
| <li>The MSD must be the last one (chronologically) inserted.</li>
| |
| <li>If you are using a USB hub, the target MSD must be the last one attached to the hub.</li>
| |
| <li><b>No important data on the MSD as it will be wiped during expansion setup!</b></li>
| |
| </ul>
| |
|
| |
| When expansion is enabled, <b>do not detach the USB device as this will delete the data stored on it</b>. Changes made to the device configuration while expansion was enabled will disappear after it is disabled.
| |
|
| |
| ====Enabling memory expansion====
| |
| ----
| |
| To successfully expand the flash memory of your device follow the steps described below.
| |
|
| |
| <ol>
| |
| <li>Attach a USB Mass Storage Device (MSD) to the USB connector on the device and go to the Services → Storage Memory Expansion page.</li>
| |
| <li>Set the 'Enable storage expansion' slider to 'on' and click 'Save & Apply'.<br>[[File:Networking_rutos_manual_storage_memory_expansion_enable_1.png|border|class=tlt-border]]</li>
| |
| <li>You will see a pop-up asking for confirmation. Take note that <u>if you continue from this point on:</u>
| |
| <ul>
| |
| <li>your <b>USB device's memory will be wiped</b> and formatted to ext2 format;</li>
| |
| <li>your device's <b>current configuration will be backed up</b> and restored to this point if the USB drive is removed or memory expansion is disabled;</li>
| |
| <li>the entire procedure <b>may take a very long time</b> and includes a reboot at the end; exact time will vary depending on the size of the MSD (larger size will take longer; for example, using a 128 GB drive will take about 2 hours to fully set up, while a 16 GB will only take about 5 minutes).</li>
| |
| </ul>Click 'Continue' to proceed.<br>[[File:Networking_rutos_manual_storage_memory_expansion_enable_2.png|border|class=tlt-border]]
| |
| </li>
| |
| <li>If all is in order you should see a 'Formatting MSD...' message on the screen. This indicates that the MSD is being formatted and integrated with the system. This procedure can take a long time and ends with a reboot of the device.<br>[[File:Networking_rutos_manual_storage_memory_expansion_enable_3.png]]</li>
| |
| <li>Your device's flash memory will be expanded once the reboot has finished. In order to check, log in to the WebUI and look to the 'System' widget in the 'Overview' page. Hover your mouse cursor over the 'FLASH' memory indicator; you should see an increase to the device's flash memory.<br>[[File:Networking_rutos_manual_storage_memory_expansion_enable_4.png|border|class=tlt-border]]</li>
| |
| </ol>
| |
|
| |
| ====Disabling memory expansion====
| |
| ----
| |
| To successfully disable memory expansion follow the steps described below.
| |
|
| |
| <ol>
| |
| <li>Go to the Services → Storage Memory Expansion page.</li>
| |
| <li>Set the 'Enable storage expansion' slider to 'off' and click 'Save & Apply'.<br>[[File:Networking_rutos_manual_storage_memory_expansion_disable_1.png|border|class=tlt-border]]</li>
| |
| <li>You will see a pop-up asking for confirmation. Take note that <u>if you continue from this point on:</u>
| |
| <ul>
| |
| <li>your <b>USB device's memory will be wiped</b> and formatted to NTFS format;</li>
| |
| <li>your <b>device's configuration will be restored</b> to the point it was before memory expansion;</li>
| |
| <li>the entire procedure <b>will take up to 2 minutes</b> including a reboot.</li>
| |
| </ul>Click 'Continue' to proceed.<br>[[File:Networking_rutos_manual_storage_memory_expansion_disable_2.png|border|class=tlt-border]]
| |
| </li>
| |
| <li>If all is in order you should see a 'Formatting MSD...' message on the screen. This indicates that the MSD is being formatted and detached from the system. This procedure can take up to a couple of minutes and ends with a reboot of the device.<br>[[File:Networking_rutos_manual_storage_memory_expansion_disable_3.png]]</li>
| |
| <li>Your device's flash memory will be restored to normal once the reboot has finished. In order to check, log in to the WebUI and look to the 'System' widget in the 'Overview' page. Hover your mouse cursor over the 'FLASH' memory indicator; you should see your device's flash memory return to its regular size.<br>[[File:Networking_rutos_manual_storage_memory_expansion_disable_4.png|border|class=tlt-border]]</li>
| |
| </ol>|}}
| |
|
| |
| ===SSHFS===
| |
| ----
| |
| <b>SSHFS</b> is a tool, which allows you to mount a remote filesystem (in remote SSH server) to your {{{name}}} device using SSH.
| |
| This service is safe to use as it authenticates connections and encrypts them.
| |
|
| |
| <b>SSHFS</b> configuration consists of setting up authentication, port and mount information parameters. Below is an example oh the SSHFS configuration page.
| |
|
| |
| [[File:Networking_rutos_manual_sshfs_v3.png|border|class=tlt-border]]
| |
|
| |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Enable</td>
| |
| <td>off {{!}} on; default: <b>off</b></td>
| |
| <td>Turns the SSHFS service on or off.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Hostname</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Hostname of the remote SSH server.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Port</td>
| |
| <td>integer [0..65535]; default: <b>none</b></td>
| |
| <td>Port of the remote SSH server.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Username</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Username of the remote SSH server.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Password</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>Password of the remote SSH server.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Mount Point</td>
| |
| <td>filepath; default: <b>/sshmount</b></td>
| |
| <td>Mount point of remote file system <b>in the {{{name}}}</b>. Remote file system has to be mounted at root <b>/</b> level.
| |
| By default the remote file system will be mounted on <b>/sshmount</b>, directory will be automatically created if does not exist yet.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Mount Path</td>
| |
| <td>filepath; default: <b>/home/</b></td>
| |
| <td>Mount path <b>in the remote SSH server</b>. For example, if SSH server is hosted on Ubuntu operating system, the Mount Path could look like this (depending on your needs): <b>/home/username/</b></td>
| |
| </tr>
| |
| </table>}}
| |
|
| |
|
| [[Category:{{{name}}} System section]] | | [[Category:{{{name}}} System section]] |