9,312
edits
Changes
Template:Networking rutos manual interfaces (view source)
Revision as of 18:02, 22 November 2021
, 18:02, 22 November 2021no edit summary
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.06.1
| fw_version = {{{series}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.07.01{{#ifeq:{{{series}}}|RUT9|.1|}}
| series = {{{series}}}
| series = {{{series}}}
}}
}}
The <b>Network Interfaces</b> section displays interfaces currently existing on this device.
The <b>Network Interfaces</b> section displays interfaces currently existing on this device.
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}.png|border|class=tlt-border]]
{{#ifeq: {{{series}}} | TCR1 | [[File:Networking_rutos_manual_tcr1_interfaces_network_interfaces.png|border|class=tlt-border]] |
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}.png|border|class=tlt-border]]|}}
==Add Interface==
==Add Interface==
</ul>
</ul>
</td>
</td>
<tr>
<tr>
<td>PDP Type</td>
<td>PDP Type</td>
<td>Specifies what of address will be requested from the operator.</td>
<td>Specifies what of address will be requested from the operator.</td>
</tr>
</tr>
</tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||
<tr>
<tr>
<td>SIM</td>
<td>SIM</td>
<td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td>
<td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td>
<td>Selects which SIM slot will be used for this interface.</td>
<td>Selects which SIM slot will be used for this interface.</td>
</tr>|}}{{#ifeq: {{{dualmodem}}} | 1 |
</tr>}}|}}{{#ifeq: {{{dualmodem}}} | 1 |
<tr>
<tr>
<td>Modem</td>
<td>Modem</td>
</tr>
</tr>
</table>
</table>
{{#switch: {{{series}}}
| TRB1 =
| RUT30X =
| RUT36X =
| TRB2 =
{{#ifeq: {{{name}}} | TRB245 |
=====Multi-APN=====
----
{{{name}}} supports Multiple PDN feature in order to establish connections to multiple mobile networks using a single SIM card. You can find a configuration example [[Multi-APN|here]].}}
| #default =
=====Multi-APN=====
----
{{{name}}} supports Multiple PDN feature in order to establish connections to multiple mobile networks using a single SIM card. You can find a configuration example [[Multi-APN|here]].
}}
|}}
|}}
<b>Advanced Settings</b> information for <b>Static</b> protocol is provided in the table below.
<b>Advanced Settings</b> information for <b>Static</b> protocol is provided in the table below.
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_static_v2.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_static.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
</tr>
</tr>
<tr>
<tr>
<td>IP4table</td>
<td>Use broadcast flag</td>
<td>integer [0..99999999]; default: <b>none</b></td>
<td>off | on; default: <b>off</b></td>
<td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
<td>Required for certain ISPs. For example, Charter with DOCSIS 3.</td>
</tr>
<tr>
<td>Use default gateway</td>
<td>off | on; default: <b>on</b></td>
<td>When checked, creates a default route for the interface.</td>
</tr>
<tr>
<td>Use gateway metric</td>
<td>integer; default: <b>3</b></td>
<td>A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).</td>
</tr>
<tr>
<td>Use custom DNS servers</td>
<td>off | on; default: <b>on</b></td>
<td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
</tr>
<tr>
<td>Client ID to send when requesting DHCP</td>
<td>string; default: <b>none</b></td>
<td>Client ID which will be sent when requesting a DHCP lease.</td>
</tr>
<tr>
<td>Vendor Class to send when requesting DHCP</td>
<td>string; default: <b>none</b></td>
<td>Vendor class which will be sent when requesting a DHCP lease.</td>
</tr>
</tr>
<tr>
<tr>
</tr>
</tr>
<tr>
<tr>
<td>Use gateway metric</td>
<td>IP4table</td>
<td>integer; default: <b>3</b></td>
<td>integer [0..99999999]; default: <b>none</b></td>
<td>A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).</td>
<td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
</tr>
</tr>
<!--<tr>
<td>IPv6 assignment length</td>
<td>IPv6 assignment length</td>
<td>integer [0..64] | <span style="color: #1550bf; font-weight: bold;">Disabled</span>; default: <b>Disabled</b></td>
<td>integer [0..64] | <span style="color: #1550bf; font-weight: bold;">Disabled</span>; default: <b>Disabled</b></td>
<td>When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix.</td>
<td>When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix.</td>
</tr>
</tr>
-->
</table>
</table>
[[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]
[[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]
<u>In order to view the DHCP server configuration, the interface <b>protocol must be set to <i>Static</i></b></i>.</u>
<i>To make the DHCP Server section visible, <b>set interface protocol to Static</b>.</i>
====DHCP Server: General Setup====
====DHCP Server: General Setup====
<tr>
<tr>
<td>Lease time</td>
<td>Lease time</td>
<td>integer [2..999999]m/h; default: <b>12h</b></td>
<td>integer [1..999999]; default: <b>12</b></br>integer [2..999999]<span class="asterisk">*</span></br>integer [120..999999]<span class="asterisk">**</span></td>
<td>A DHCP lease will expire after the amount of time specified in this field and the device that was using the lease will have to request a new one. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes (e.g., if lease time is 12 hours, then every 6 hours the device will ask the DHCP server to renew its lease).<br>The minimal amount of time that can be specified is 2 minutes.</td>
<td>A DHCP lease will expire after the amount of time specified in this field and the device that was using the lease will have to request a new one. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes (e.g., if lease time is 12 hours, then every 6 hours the device will ask the DHCP server to renew its lease).<br>The minimal amount of time that can be specified is 2 minutes.</br><span class="asterisk">*</span>If selected Units is Minutes.</br><span class="asterisk">**</span>If selected Units is seconds.</td>
</tr>
<tr>
<td>Units</td>
<td>Hours | Minutes | Seconds; default: <b>Hours</b></td>
<td>Lease time units.</td>
</tr>
</tr>
</table>
</table>
<b>Static IP leases</b> are used to reserve specific IP addresses for specific devices by binding them to their MAC address. This is useful when you have a stationary device connected to your network that you need to reach frequently, e.g., printer, IP phone, etc.
<b>Static IP leases</b> are used to reserve specific IP addresses for specific devices by binding them to their MAC address. This is useful when you have a stationary device connected to your network that you need to reach frequently, e.g., printer, IP phone, etc.
This section displays static IP leases currently existing on this device. <u>In order to view the Static Lease section, the interface <b>protocol must be set to <i>Static</i></b></i>.</u>
This section displays static IP leases currently existing on this device.
<i>To make the Static Lease section visible, <b>set interface protocol to Static</b>.</i>
----
----
The Static Lease list is empty by default. To add a new Static Lease look to the Add Lease section; enter a custom name for the lease and click the 'Add' button.
The Static Lease list is empty by default. To add a new Static Lease look to the Add Lease section; enter a custom name for the lease and click the 'Add' button.
----
----
The <b>Relay Configuration</b> section is used to relay and dynamically redirect incoming connections to a target host. Its main purpose is extending the wireless network. For example, when the device is in Wireless Station (client) mode, it can be used to bridge WAN and LAN interfaces to create a larger wireless network.<br>You can find a detailed usage example <b>[[Relayd|here]]</b>.
The <b>Relay Configuration</b> section is used to relay and dynamically redirect incoming connections to a target host. Its main purpose is extending the wireless network. For example, when the device is in Wireless Station (client) mode, it can be used to bridge WAN and LAN interfaces to create a larger wireless network.<br>You can find a detailed usage example <b>[[Relayd|here]]</b>.
{{#switch: {{{series}}}
| #default =
| RUT36X|RUT9|TCR1 =
<u><b>
<u>In order to view the Relay Configuration section, the interface <b>protocol must be set to <i>Static</i></b></i>.</u>
Note:</b> Relay is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
[[File:Networking_rutos_manual_interfaces_interface_configuration_relay_configuration.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_interfaces_interface_configuration_relay_configuration.png|border|class=tlt-border]]
</tr>
</tr>
</table>|}}
</table>|}}
===UDP Broadcast Relay===
----
The <b>UDP Broadcast Relay</b> will listen for broadcast traffic on the specified port and relay that traffic to the specified interface(s).
<i><b>Note:</b> UDP Broadcast Relay is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</i>
[[File:Networking_rutos_manual_interfaces_interface_configuration_udp_broadcast_relay.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 <nowiki>|</nowiki> on; default: <b>off</b></td>
<td>Turns UDP Broadcast Relay on or off.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..655353]; default: <b>none</b></td>
<td>UDP port to listen for broadcast traffic.</td>
</tr>
<tr>
<td>Interfaces</td>
<td>network interface(s); default: <b>none</b></td>
<td>The interface(s) to which the traffic will be redirected to.</td>
</tr>
</table>
{{#ifeq: {{{mobile}}} | 1 |
{{#ifeq: {{{mobile}}} | 1 |
===Mobile Data Limit===
===Mobile Data Limit===
The <b>Mobile Data Limit</b> section provides you with the possibility to set data usage limits for your mobile network interfaces and data usage warnings via SMS message in order to protect yourself from unwanted data charges.
The <b>Mobile Data Limit</b> section provides you with the possibility to set data usage limits for your mobile network interfaces and data usage warnings via SMS message in order to protect yourself from unwanted data charges.
<u>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to <i>Mobile</i></b></i>.</u>
<i>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to Mobile</b>.</i>
[[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit.png|border|class=tlt-border]]
</table>
</table>
<font size="-1"><span class="asterisk">*</span>Your carrier's data usage accounting may differ. Teltonika is not liable should any accounting discrepancies occur.</font>|}}
<font size="-1"><i><span class="asterisk">*</span>Your carrier's data usage accounting may differ. Teltonika is not liable should any accounting discrepancies occur.</i></font>|}}
[[Category:{{{name}}} Network section]]
[[Category:{{{name}}} Network section]]
