Difference between revisions of "Template:Networking rutos manual interfaces"

From Teltonika Networks Wiki
(38 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Template:Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.04.1
+
| fw_version = {{{series}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.07.01{{#ifeq:{{{series}}}|RUT9|.1|}}
 
| series    = {{{series}}}
 
| series    = {{{series}}}
 
}}
 
}}
Line 8: Line 8:
 
The <b>Interfaces</b> page is used to to set up network interfaces.  
 
The <b>Interfaces</b> page is used to to set up network interfaces.  
  
This manual page provides an overview of the Interfaces windows in {{{name}}} devices.
+
This manual page provides an overview of the Interfaces page in {{{name}}} devices.
  
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
Line 18: Line 18:
 
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.
  
{{#ifeq: {{{series}}} | RUTX
+
{{#ifeq: {{{series}}} | TCR1 | [[File:Networking_rutos_manual_tcr1_interfaces_network_interfaces.png|border|class=tlt-border]] |
| [[File:Networking_rutos_manual_interfaces_network_interfaces_modem_{{{modem}}}_v1.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]]|}}
| [[File:Networking_{{lc:{{{series}}}}}_manual_interfaces_network_interfaces_v1.png|border|class=tlt-border]]
 
}}
 
  
 
==Add Interface==
 
==Add Interface==
Line 27: Line 25:
 
The <b>Add Interface</b> section is used to create additional network interfaces. To create a new interface, simply enter a custom name for it and click the 'Add' button.
 
The <b>Add Interface</b> section is used to create additional network interfaces. To create a new interface, simply enter a custom name for it and click the 'Add' button.
  
[[File:Networking_rutos_manual_interfaces_add_interface_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_add_interface.png|border|class=tlt-border]]
  
 
==Interface configuration==
 
==Interface configuration==
  
This section provides information on <b>network interface configuration</b>. There are {{{no_of_if}}} major types of interfaces on the device:
+
This section provides information on <b>network interface configuration</b>. There are {{{no_of_if}}} main types of interfaces on the device:
  
 
<ul>
 
<ul>
 
     <li><b>Ethernet LAN</b></li>
 
     <li><b>Ethernet LAN</b></li>
{{#ifeq: {{{eth}}} | 1
+
{{#ifeq: {{{wired}}} | 1 | <li><b>Ethernet WAN</b></li>|}}
  |<li><b>Ethernet WAN</b></li>
+
{{#ifeq: {{{mobile}}} | 1 | <li><b>Mobile WAN</b></li>|}}
  |}}
 
{{#ifeq: {{{modem}}} | 1
 
  |<li><b>Mobile WAN</b></li>
 
  |}}
 
 
</ul>
 
</ul>
  
Each type utilizes generally utilizes these interface protocols:
+
Different types of interfaces can be configured under different protocols:
  
 
<table class="nd-othertables_3" style="width: 900px;">
 
<table class="nd-othertables_3" style="width: 900px;">
Line 52: Line 46:
 
       <th width="14%" style="text-align: center;">DHCPv6</th>
 
       <th width="14%" style="text-align: center;">DHCPv6</th>
 
       <th width="14%" style="text-align: center;">PPPoE</th>
 
       <th width="14%" style="text-align: center;">PPPoE</th>
      <th width="14%" style="text-align: center;">Mobile</th>
+
{{#ifeq:{{{mobile}}}|1|<th width="14%" style="text-align: center;">Mobile</th>|}}
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 60: Line 54:
 
       <td></td>
 
       <td></td>
 
       <td></td>
 
       <td></td>
      <td></td>
+
{{#ifeq:{{{mobile}}}|1|<td></td>|}}
 
     </tr>
 
     </tr>
{{#ifeq: {{{eth}}} | 1  
+
{{#ifeq: {{{wired}}} | 1  
 
  |  <tr>
 
  |  <tr>
 
         <td style="text-align: left; font-weight: bold;">Ethernet WAN</td>
 
         <td style="text-align: left; font-weight: bold;">Ethernet WAN</td>
Line 69: Line 63:
 
       <td>[[File:Blue_check_mark.png|center|15px]]</td>
 
       <td>[[File:Blue_check_mark.png|center|15px]]</td>
 
       <td>[[File:Blue_check_mark.png|center|15px]]</td>
 
       <td>[[File:Blue_check_mark.png|center|15px]]</td>
      <td></td>
+
{{#ifeq:{{{mobile}}}|1|<td></td>|}}
 
     </tr>
 
     </tr>
 
  |  
 
  |  
 
}}
 
}}
{{#ifeq: {{{modem}}} | 1  
+
{{#ifeq: {{{mobile}}} | 1  
 
  |  <tr>
 
  |  <tr>
 
         <td style="text-align: left; font-weight: bold;">Mobile WAN</td>
 
         <td style="text-align: left; font-weight: bold;">Mobile WAN</td>
Line 88: Line 82:
 
To begin configuring an interface, click the 'Edit' button on the right side of the interface:
 
To begin configuring an interface, click the 'Edit' button on the right side of the interface:
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_begin_to_edit_v1.png]]
+
[[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan}}}.png]]
 
 
===Interfaces: if_name===
 
----
 
This section covers all parameters directly related to a network <b>interface</b>.
 
  
====General Setup====
+
===General Setup===
 
----
 
----
The <b>General Setup</b> section is used to configure the protocol and all the different parameters that go along with each protocol. This section is different for each protocol.
+
The <b>General Setup</b> section is used to configure the protocol of an interface and all the different parameters that go along with each protocol. If <b>None</b> protocol is chosen, all other interface settings will be ignored. The following sections are different for each protocol.
  
=====General Setup: Static=====
+
====General Setup: Static====
 
----
 
----
 
The <b>static</b> protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease.  
 
The <b>static</b> protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease.  
  
{{#ifeq: {{{series}}} | TRB14X
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_static_ip_lan_{{{lan}}}.png|border|class=tlt-border]]
| [[File:Networking_trb14x_manual_interfaces_network_interfaces_lan_general_setup_static_ip_v1.png|border|class=tlt-border]]
 
| [[File:Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_static_ip_v1.png|border|class=tlt-border]]
 
}}
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 140: Line 127:
 
</table>
 
</table>
  
=====General Setup: DHCP=====
+
====General Setup: DHCP====
 
----
 
----
 
The <b>DHCP</b> protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease.
 
The <b>DHCP</b> protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_dhcp_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_dhcp.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 159: Line 146:
 
</table>
 
</table>
  
=====General Setup: DHCPv6=====
+
====General Setup: DHCPv6====
 
----
 
----
 
The <b>DHCPv6</b> protocol is used to set up an IPv6 interface which obtains its configuration parameters automatically via a DHCP lease.
 
The <b>DHCPv6</b> protocol is used to set up an IPv6 interface which obtains its configuration parameters automatically via a DHCP lease.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_dhcpv6_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_dhcpv6.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 183: Line 170:
 
</table>
 
</table>
  
=====General Setup: PPPoE=====
+
====General Setup: PPPoE====
 
----
 
----
The <b>PPPoE</b> protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port{{#ifeq:{{{series}}}|TRB14X| (in this case: an Ethernet connection simulated over the USB port)|}}.
+
The <b>PPPoE</b> protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port{{#ifeq:{{{series}}}|TRB1| (in this case: an Ethernet connection simulated over the USB port)|}}.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_general_setup_pppoe_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_pppoe.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 216: Line 203:
 
     </tr>
 
     </tr>
 
</table>
 
</table>
{{#ifeq: {{{modem}}} | 1 |
+
{{#ifeq: {{{mobile}}} | 1 |
=====General Setup: Mobile=====
+
====General Setup: Mobile====
 
----
 
----
 
The <b>Mobile</b> protocol is used to set up an interface which can establish a mobile WAN connection.
 
The <b>Mobile</b> protocol is used to set up an interface which can establish a mobile WAN connection.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_general_setup_mobile_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 231: Line 218:
 
     <tr>
 
     <tr>
 
       <td>Mode</td>
 
       <td>Mode</td>
       <td>NAT <nowiki>|</nowiki> Bridge {{!}} Passthrough; default: <b>NAT</b></td>
+
       <td>NAT <nowiki>|</nowiki> Bridge <nowiki>|</nowiki> Passthrough; default: <b>NAT</b></td>
 
       <td>Mobile connection operating mode.
 
       <td>Mobile connection operating mode.
 
             <ul>
 
             <ul>
 
                 <li><b>NAT</b> - the mobile connection uses NAT (network address translation).</li>
 
                 <li><b>NAT</b> - the mobile connection uses NAT (network address translation).</li>
                 <li><span style="color: red;"><b>Bridge</b></span> - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li>
+
                 <li><span style="color: #1550bf;"><b>Bridge</b></span> - bridges the LTE data connection with LAN. The device assigns its WAN IP address to another device (first connected to LAN or specified with MAC address). Using Bridge mode will disable most of the device’s capabilities.</li>
 
                 <li><span style="color: cornflowerblue;"><b>Passthrough</b></span> - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li>
 
                 <li><span style="color: cornflowerblue;"><b>Passthrough</b></span> - in this mode the {{{name}}} shares its WAN IP to a single LAN device (first connected to LAN or specified with MAC address). The LAN device will get WAN IP of {{{name}}} instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.</li>
 
             </ul>
 
             </ul>
 
         </td>
 
         </td>
     </tr>
+
     <tr>
{{#ifeq: {{{series}}} | TRB14X
 
|
 
<tr>
 
 
     <td>PDP Type</td>
 
     <td>PDP Type</td>
 
         <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4</b></td>
 
         <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4</b></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>Select which sim will be used for this interface.</td>
+
         <td>Selects which SIM slot will be used for this interface.</td>
     </tr>}}
+
     </tr>}}|}}{{#ifeq: {{{dualmodem}}} | 1 |
 +
    <tr>
 +
    <td>Modem</td>
 +
        <td>Primary modem <nowiki>|</nowiki> Secondary modem; default: <b>Primary modem</b></td>
 +
        <td>Selects which modem will be used for this interface.</td>
 +
    </tr>|}}
 
     <tr>
 
     <tr>
 
     <td>Auto APN</td>
 
     <td>Auto APN</td>
Line 279: Line 269:
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
     <td><span style="color: red;">Bridge</span> {{!}} <span style="color: cornflowerblue;">Passthrough</span>: MAC Address</td>
+
     <td><span style="color: #1550bf;">Bridge</span> <nowiki>|</nowiki> <span style="color: cornflowerblue;">Passthrough</span>: MAC Address</td>
 
         <td>mac; default: <b>none</b></td>
 
         <td>mac; default: <b>none</b></td>
 
         <td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode.<br><b>Note:</b> this field only becomes visible when using Bridge or Passthrough mode.</td>
 
         <td>Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode.<br><b>Note:</b> this field only becomes visible when using Bridge or Passthrough mode.</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]].
 +
}}
 
|}}
 
|}}
  
====Advanced Settings====
+
===Advanced Settings===
 
----
 
----
 
The <b>Advanced Settings</b> section is used to set up some of the more specific and less frequently used interface parameters. This section is different for each protocol.
 
The <b>Advanced Settings</b> section is used to set up some of the more specific and less frequently used interface parameters. This section is different for each protocol.
  
=====Advanced Settings: Static=====
+
====Advanced Settings: Static====
 
----
 
----
 
<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_network_interfaces_lan_advanced_settings_static_v1.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">
Line 316: Line 322:
 
         <td>off | on; default: <b>on</b></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use broadcast flag</td>
 +
        <td>off | on; default: <b>off</b></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>
 
         <td>Override MAC address</td>
 
         <td>Override MAC address</td>
 
         <td>mac; default: <b>none</b></td>
 
         <td>mac; default: <b>none</b></td>
         <td>When set, uses a user-defined MAC address for the interface.</td>
+
         <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 328: Line 364:
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Use gateway metric</td>
+
         <td>IP4table</td>
         <td>integer; default: <b>none</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>
+
<!--<tr>
 
         <td>IPv6 assignment length</td>
 
         <td>IPv6 assignment length</td>
         <td>integer [0..64] | <span style="color: red;">disabled</span>; default: <b>60</b></td>
+
         <td>integer [0..64] | <span style="color: #1550bf; font-weight: bold;">Disabled</span>; default: <b>Disabled</b></td>
 
         <td>Delegates a prefix of given length to the interface.</td>
 
         <td>Delegates a prefix of given length to the interface.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">IPv6 address</span></td>
+
         <td><span style="color: #1550bf;">IPv6 address</span></td>
 
         <td>ip6; default: <b>none</b></td>
 
         <td>ip6; default: <b>none</b></td>
         <td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices.<br><b>NOTE</b>: this field only becomes visible when IPv6 assignment length is set to disabled.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i></td>
+
         <td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i></td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">IPv6 gateway</span></td>
+
         <td><span style="color: #1550bf;">IPv6 gateway</span></td>
 
         <td>ip6; default: <b>none</b></td>
 
         <td>ip6; default: <b>none</b></td>
 
         <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td>
 
         <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">IPv6 routed prefix</span></td>
+
         <td><span style="color: #1550bf;">IPv6 routed prefix</span></td>
 
         <td>ip6; default: <b>none</b></td>
 
         <td>ip6; default: <b>none</b></td>
 
         <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td>
 
         <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td>
Line 355: Line 391:
 
         <td>IPv6 assignment hint</td>
 
         <td>IPv6 assignment hint</td>
 
         <td>string; default: <b>none</b></td>
 
         <td>string; default: <b>none</b></td>
         <td>The subprefix-ID that should be delegated as hexadecimal number.</td>
+
         <td>Subprefix ID to be used if available (e.g., the value <i>1234</i> with an IPv6 assignment length of 64 will assign prefixes of the form …:1234::/64 or given LAN ports, LAN & LAN2, and a prefix delegation of /56, use IPv6 assignment hint of 00 and 80 which would give prefixes of LAN …:xx00::/64 and LAN2 …:xx80::/64)</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 362: Line 398:
 
         <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>
  
=====Advanced Settings: DHCP=====
+
====Advanced Settings: DHCP====
 
----
 
----
 
<b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_dhcp_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcp_v2.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 390: Line 427:
 
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IP4table</td>
 +
        <td>integer [0..99999999]; default: <b>none</b></td>
 +
        <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 403: Line 445:
 
     <tr>
 
     <tr>
 
         <td>Use DNS servers advertised by peer</td>
 
         <td>Use DNS servers advertised by peer</td>
         <td><span style="color: red;">off</span> | on; default: <b>on</b></td>
+
         <td><span style="color: #1550bf; font-weight: bold;">off</span> | on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">Use custom DNS servers</span></td>
+
         <td><span style="color: #1550bf;">Use custom DNS servers</span></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
Line 429: Line 471:
 
         <td>Override MAC address</td>
 
         <td>Override MAC address</td>
 
         <td>mac; default: <b>none</b></td>
 
         <td>mac; default: <b>none</b></td>
         <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your device). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer.</td>
+
         <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 438: Line 480:
 
</table>
 
</table>
  
=====Advanced Settings: DHCPv6=====
+
====Advanced Settings: DHCPv6====
 
----
 
----
 
<b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_dhcpv6_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcpv6_v2.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 464: Line 506:
 
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IP4table</td>
 +
        <td>integer [0..99999999]; default: <b>none</b></td>
 +
        <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 472: Line 519:
 
     <tr>
 
     <tr>
 
         <td>Use DNS servers advertised by peer</td>
 
         <td>Use DNS servers advertised by peer</td>
         <td><span style="color: red;">off</span> | on; default: <b>on</b></td>
+
         <td><span style="color: #1550bf; font-weight: bold;">off</span> | on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">Use custom DNS servers</span></td>
+
         <td><span style="color: #1550bf;">Use custom DNS servers</span></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
Line 493: Line 540:
 
         <td>Override MAC address</td>
 
         <td>Override MAC address</td>
 
         <td>mac; default: <b>none</b></td>
 
         <td>mac; default: <b>none</b></td>
         <td>When set, uses a user-defined MAC address for the interface.</td>
+
         <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 502: Line 549:
 
</table>
 
</table>
  
=====Advanced Settings: PPPoE=====
+
====Advanced Settings: PPPoE====
 
----
 
----
 
<b>Advanced Settings</b> information for <i>PPPoE</i> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <i>PPPoE</i> protocol is provided in the table below.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_pppoe_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_pppoe_v2.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 528: Line 575:
 
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IP4table</td>
 +
        <td>integer [0..99999999]; default: <b>none</b></td>
 +
        <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 546: Line 598:
 
     <tr>
 
     <tr>
 
         <td>Use DNS servers advertised by peer</td>
 
         <td>Use DNS servers advertised by peer</td>
         <td><span style="color: red;">off</span> | on; default: <b>on</b></td>
+
         <td><span style="color: #1550bf; font-weight: bold;">off</span> | on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">Use custom DNS servers</span></td>
+
         <td><span style="color: #1550bf;">Use custom DNS servers</span></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
Line 580: Line 632:
 
     </tr>
 
     </tr>
 
</table>
 
</table>
{{#ifeq: {{{modem}}} | 1 |
+
{{#ifeq: {{{mobile}}} | 1 |
=====Advanced Settings: Mobile=====
+
====Advanced Settings: Mobile====
 
----
 
----
 
<b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_advanced_settings_mobile_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v2.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 607: Line 659:
 
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
 
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 
         <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IP4table</td>
 +
        <td>integer [0..99999999]; default: <b>none</b></td>
 +
        <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Use DNS servers advertised by peer</td>
 
         <td>Use DNS servers advertised by peer</td>
         <td><span style="color: red;">off</span> <nowiki>|</nowiki> on; default: <b>on</b></td>
+
         <td><span style="color: #1550bf; font-weight: bold;">off</span> <nowiki>|</nowiki> on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td><span style="color: red;">Use custom DNS servers</span></td>
+
         <td><span style="color: #1550bf;">Use custom DNS servers</span></td>
 
         <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 
         <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
 
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.<br><b>Note:</b> this field only becomes visible when Use DNS servers advertised by peer is set to <i>off</i></td>
Line 629: Line 686:
 
     </tr>
 
     </tr>
 
</table>|}}
 
</table>|}}
====Physical Settings====
+
===Physical Settings===
 
----
 
----
 
The <b>Physical Settings</b> section is used to create associations with physical interfaces and bridge network interfaces.
 
The <b>Physical Settings</b> section is used to create associations with physical interfaces and bridge network interfaces.
  
{{#ifeq: {{{series}}} | TRB14x
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_physical_settings.png|border|class=tlt-border]]
| [[File:Networking_trb14x_manual_interfaces_network_interfaces_lan_physical_settings_v1.png|border|class=tlt-border]]
+
 
| [[File:Networking_rutos_manual_interfaces_network_interfaces_lan_physical_settings_wifi_{{{wifi}}}_v1.png|border|class=tlt-border]]
 
}}
 
 
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
Line 645: Line 700:
 
     <tr>
 
     <tr>
 
         <td>Bridge interfaces</td>
 
         <td>Bridge interfaces</td>
         <td>off | on; default: <b>on</b></td>
+
         <td>off | <span style="color: #1550bf; font-weight: bold;">on</span>; default: <b>off</b></td>
 
         <td>Bridges physical interfaces specified in this configuration.</td>
 
         <td>Bridges physical interfaces specified in this configuration.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Enable STP</td>
+
         <td><span style="color: #1550bf;">Enable STP</span></td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
         <td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off.</td>
+
         <td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off.<br><b>Note:</b> this field becomes visible when 'Bridge interfaces' is set to <i>on</i>.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Interface</td>
 
         <td>Interface</td>
         <td>network interface(s); default: <b>{{#ifeq:{{{series}}}|TRB14X|rndis0|eth0}}{{#ifeq:{{{wifi}}}|1| wlan0 wlan1|}}</b></td>
+
         <td>network interface(s); default: <b>none</b></td>
         <td>Ties this network interface to physical device interfaces such as Ethernet {{#ifeq:{{{wifi}}}|1| or WiFi radios|}}.{{#ifeq:{{{name}}}|RUTXR1| If the <span style="color: red;">eth1</span> interface is selected, then port priority selection appears. </td>
+
         <td>Ties this network interface to physical device interfaces such as Ethernet {{#ifeq:{{{wifi}}}|1| or WiFi radios|}}.</td>
  </tr>
+
    </tr>{{#ifeq: {{{name}}}| RUTXR1 |  
<tr>
+
    <tr>
<td><span style="color: red;">Port priority</span></td>
+
        <td>Port priority</td>
<td>port; default: <b>SFP</b></td>
+
        <td>Ethernet<nowiki>|</nowiki>SFP default: <b>SFP</b></td>
<td>Port priority option allows to change physical port priority (SFP or Ethernet). This option is uniform between all eth1 interfaces.
+
        <td>Port priority option allows to change physical port priority (SFP or Ethernet). This option is uniform between all eth1 interfaces.<br><b>Note:</b> this field becomes visible when 'Interface' is set to <i>eth1</i>.</td>
</tr>
+
    </tr>|}}
|</td> </tr>}}
 
 
</table>
 
</table>
  
====Firewall Settings====
+
===Firewall Settings===
 
----
 
----
The <b>Firewall Settings</b> section is used to specify to which firewall zone if any this interface belongs.
+
The <b>Firewall Settings</b> section is used to specify to which firewall zone if any this interface belongs. Assigning an interface to a zone may provide easier configuration of firewall rules. For example, instead of configuring separate rules for each WAN interface, you can add all WAN interfaces into a single firewall zone and make the rule apply to that zone instead.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_firewall_settings_v1.png|border|class=tlt-border]]
+
More firewall zone settings can be configured from the Network → Firewall → General Settings → [[{{{name}}}_Firewall#Zones|Zones]] section.
 +
 
 +
[[File:Networking_rutos_manual_interfaces_interface_configuration_firewall_settings.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 691: Line 747:
 
[[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====
Line 697: Line 753:
 
The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
 
The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_general_setup_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 722: Line 778:
 
     <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>
Line 735: Line 796:
 
Refer to the table below for information on the <b>Advanced Settings</b> section.
 
Refer to the table below for information on the <b>Advanced Settings</b> section.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_advanced_settings_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_advanced_settings.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 769: Line 830:
 
Refer to the table below for information on the <b>IPv6 Settings</b> section.
 
Refer to the table below for information on the <b>IPv6 Settings</b> section.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_ipv6_settings_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_ipv6_settings.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 779: Line 840:
 
     <tr>
 
     <tr>
 
         <td>Router Advertisement Service</td>
 
         <td>Router Advertisement Service</td>
         <td>disabled | relay mode | server mode | hybrid mode; default: <b>Disabled</b></td>
+
         <td>Disabled | Relay mode | Server mode | Hybrid mode; default: <b>Disabled</b></td>
 
         <td>Specifies whether router advertisements should be enabled (server mode), relayed or disabled. </td>
 
         <td>Specifies whether router advertisements should be enabled (server mode), relayed or disabled. </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>DHCPv6 Service</td>
 
         <td>DHCPv6 Service</td>
         <td>disabled | relay mode | server mode | hybrid mode; default: <b>Disabled</b></td>
+
         <td>Disabled | Relay mode | Server mode | Hybrid mode; default: <b>Disabled</b></td>
 
         <td>Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled).</td>
 
         <td>Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>NDP Proxy</td>
 
         <td>NDP Proxy</td>
         <td>disabled | relay mode | hybrid mode; default: <b>Disabled</b></td>
+
         <td>Disabled | Relay mode | Hybrid mode; default: <b>Disabled</b></td>
 
         <td>Specifies whether NDP should be relayed or disabled.</td>
 
         <td>Specifies whether NDP should be relayed or disabled.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>DHCPv6 Mode</td>
 
         <td>DHCPv6 Mode</td>
         <td>stateless | stateful-only | stateless + stateful; default: <b>stateless + stateful</b></td>
+
         <td>Stateless | Stateful-only | Stateless + stateful; default: <b>Stateless + stateful</b></td>
 
         <td>Router announcement (RA) mode.</td>
 
         <td>Router announcement (RA) mode.</td>
 
     </tr>
 
     </tr>
Line 820: Line 881:
 
This section displays static IP leases currently existing on this device.
 
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>
+
<i>To make the Static Lease section visible, <b>set interface protocol to Static</b>.</i>
 
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_v1.png|border|class=tlt-border]]
 
 
 
====Static Lease: Settings====
 
 
----
 
----
To access a lease's <b>settings</b> page, click the 'Edit' button located to the right of the lease:
+
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.
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_edit_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_static_lease_add_button.png|border|class=tlt-border]]
  
You should be directed to a window that looks like this:
+
You should be redirected to the Settings page for that lease, which should look similar to this:
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_settings_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_static_lease_settings.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 843: Line 900:
 
       <td>MAC address</td>
 
       <td>MAC address</td>
 
       <td>mac; default: <b>none</b></td>
 
       <td>mac; default: <b>none</b></td>
       <td>MAC address of a device that is on this interface's network.</td>
+
       <td>MAC address of a device that will connect to this network interface.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 852: Line 909:
 
</table>
 
</table>
  
====Static Lease: Add Lease====
+
After you click 'Save & Apply' you will be redirected back to the [[#Network_Interfaces|Network Interfaces]] page. If you wish to modify the lease later, you can find in the Static Lease list. Simply click the 'Edit' button next to it in order to enter the Settings page for the Static Lease.
----
+
 
The <b>Add Lease</b> section is used to create new static leases. To create a new lease, simply enter a custom name for it and click the 'Add' button.
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_static_lease_edit_button.png|border|class=tlt-border]]
  
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_add_lease_v1.png|border|class=tlt-border]]
 
 
{{#ifeq: {{{wifi}}} | 1 |
 
{{#ifeq: {{{wifi}}} | 1 |
 
===Relay Configuration===
 
===Relay Configuration===
 
----
 
----
 
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_network_interfaces_lan_relay_configuration_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_relay_configuration.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 883: Line 944:
 
     </tr>
 
     </tr>
 
</table>|}}
 
</table>|}}
{{#ifeq: {{{modem}}} | 1 |
+
 
 +
===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 |
 
===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_network_interfaces_lan_general_setup_mobile_mobile_data_limit_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_mobile_mobile_data_limit.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 934: Line 1,026:
 
</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]]

Revision as of 17:02, 22 November 2021

Template:Networking rutos manual fw disclosure

Summary

The Interfaces page is used to to set up network interfaces.

This manual page provides an overview of the Interfaces page in {{{name}}} devices.

If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.

Networking rutos manual webui basic advanced mode 75.gif

Network Interfaces

The Network Interfaces 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]]

Add Interface

The Add Interface section is used to create additional network interfaces. To create a new interface, simply enter a custom name for it and click the 'Add' button.

Networking rutos manual interfaces add interface.png

Interface configuration

This section provides information on network interface configuration. There are {{{no_of_if}}} main types of interfaces on the device:

  • Ethernet LAN

Different types of interfaces can be configured under different protocols:

Static DHCP DHCPv6 PPPoE
Ethernet LAN
Blue check mark.png

To begin configuring an interface, click the 'Edit' button on the right side of the interface:

[[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan}}}.png]]

General Setup


The General Setup section is used to configure the protocol of an interface and all the different parameters that go along with each protocol. If None protocol is chosen, all other interface settings will be ignored. The following sections are different for each protocol.

General Setup: Static


The static protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease.

[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_static_ip_lan_{{{lan}}}.png|border|class=tlt-border]]

Field Value Description
IPv4 address ip4; default[for LAN]: 192.168.1.1 The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.
IPv4 netmask netmask; default[for LAN]: 255.255.255.0 The IPv4 netmask of this interface. A netmask is used to define how "large" a network is by specifying which part of the IP address denotes the network and which part denotes a device.
IPv4 gateway ip4; default: none The IPv4 gateway address used by this interface. An interface's default gateway is the default address through which all outgoing traffic is directed.
IPv4 broadcast ip4; default: none The IPv4 broadcast address used by this interface. IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers.
DNS servers ip4; default: none DNS server addresses that this interface will use. If left empty, DNS servers are assigned automatically. To see what DNS servers are currently used, you can check the contents of the /tmp/resolv.conf.auto file.

General Setup: DHCP


The DHCP protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease.

Networking rutos manual interfaces interface configuration general setup dhcp.png

Field Value Description
Hostname to send when requesting DHCP string; default: none A hostname for this interface used to identify this machine on the DHCP server.

General Setup: DHCPv6


The DHCPv6 protocol is used to set up an IPv6 interface which obtains its configuration parameters automatically via a DHCP lease.

Networking rutos manual interfaces interface configuration general setup dhcpv6.png

Field Value Description
Request IPv6-address try | force | disabled; default: try Defines the behaviour for requesting an address.
Request IPv6-prefix of length integer [0..64] | Automatic | disabled ; default: Automatic Defines how this will request a IPv6 ULA-Prefix length. If set to 'disabled' the interface will obtain a single IPv6 address without a subnet for routing.

General Setup: PPPoE


The PPPoE protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port.

Networking rutos manual interfaces interface configuration general setup pppoe.png

Field Value Description
PAP/CHAP username string; default: none Username used in PAP/CHAP authentication.
PAP/CHAP password string; default: none Password used in PAP/CHAP authentication.
Access Concentrator string; default: none The Access Concentrator to connect to. ISPs used Access Concentrators to route their PPPoE connections. Usually, the settings are received automatically, however in some cases it is required to specify the name for an Access Concentrator. Leave empty to detect Access Concentrators automatically.
Service name string; default: none The Service Name to connect to. Leave empty to detect Service name automatically.


Advanced Settings


The Advanced Settings section is used to set up some of the more specific and less frequently used interface parameters. This section is different for each protocol.

Advanced Settings: Static


Advanced Settings information for Static protocol is provided in the table below.

Networking rutos manual interfaces interface configuration advanced settings static.png

Field Value Description
Bring up on boot off | on; default: on Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.
Use built in IPv6-management off | on; default: on Specifies whether to enable prefix delegation.
Force link off | on; default: on Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.
Use broadcast flag off | on; default: off Required for certain ISPs. For example, Charter with DOCSIS 3.
Use default gateway off | on; default: on When checked, creates a default route for the interface.
Use gateway metric integer; default: 3 A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).
Use custom DNS servers off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Client ID to send when requesting DHCP string; default: none Client ID which will be sent when requesting a DHCP lease.
Vendor Class to send when requesting DHCP string; default: none Vendor class which will be sent when requesting a DHCP lease.
Override MAC address mac; default: none When set, uses a user-defined MAC address for the interface instead of the default one.
Override MTU integer [1..9200]; default: none Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.

Advanced Settings: DHCP


Advanced Settings information for DHCP protocol is provided in the table below.

Networking rutos manual interfaces interface configuration advanced settings dhcp v2.png

Field Value Description
Bring up on boot off | on; default: on Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.
Use built-in IPv6 management off | on; default: on Specifies whether to enable prefix delegation.
Force link off | on; default: off Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.
Use broadcast flag off | on; default: off Required for certain ISPs. For example, Charter with DOCSIS 3.
Use default gateway off | on; default: on When checked, creates a default route for the interface.
Use DNS servers advertised by peer off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Use custom DNS servers off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Note: this field only becomes visible when Use DNS servers advertised by peer is set to off
Use gateway metric integer; default: none A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).
Client ID to send when requesting DHCP string; default: none Client ID which will be sent when requesting a DHCP lease.
Vendor Class to send when requesting DHCP string; default: none Vendor class which will be sent when requesting a DHCP lease.
Override MAC address mac; default: none When set, uses a user-defined MAC address for the interface instead of the default one.
Override MTU integer [1..9200]; default: none Changes the interfaces allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.

Advanced Settings: DHCPv6


Advanced Settings information for DHCPv6 protocol is provided in the table below.

Networking rutos manual interfaces interface configuration advanced settings dhcpv6 v2.png

Field Value Description
Bring up on boot off | on; default: on Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.
Use built in IPv6-management off | on; default: on Specifies whether to enable prefix delegation.
Force link off | on; default: off Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.
Use default gateway off | on; default: on When checked, creates a default route for the interface.
Use DNS servers advertised by peer off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Use custom DNS servers off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Note: this field only becomes visible when Use DNS servers advertised by peer is set to off
Custom delegated IPv6-prefix ip6 prefix; default: none Uses an (additional) user-provided IPv6 prefix for distribution to clients.
Client ID to send when requesting DHCP string; default: none Client ID which will be sent when requesting a DHCP lease.
Override MAC address mac; default: none When set, uses a user-defined MAC address for the interface instead of the default one.
Override MTU integer [1..9200]; default: none Changes the interface's allowed maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.

Advanced Settings: PPPoE


Advanced Settings information for PPPoE protocol is provided in the table below.

Networking rutos manual interfaces interface configuration advanced settings pppoe v2.png

Field Value Description
Bring up on boot off | on; default: on Specifies whether the interface should be launched during the boot process. If set to off, the interface would have to be brought up manually after each boot.
Use built-in IPv6 management off | on; default: on Specifies whether to enable prefix delegation.
Force link off | on; default: off Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.
Obtain IPv6 address Automatic | Disabled | Manual; default: Automatic Defines behaviour for obtaining an IPv6 address.
Use default gateway off | on; default: on When checked, creates a default route for the interface.
Use gateway metric integer; default: none A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).
Use DNS servers advertised by peer off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Use custom DNS servers off | on; default: on Specifies whether to use DNS servers obtained automatically or specified manually.
Note: this field only becomes visible when Use DNS servers advertised by peer is set to off
LCP echo failure threshold integer; default: none Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures.
LCP echo interval integer; default: none Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold.
Host-Uniq tag content raw hex-encoded bytes; default: none Leave empty unless your ISP require this.
Inactivity timeout mac; default: none Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection.
Override MTU integer [1..1500]; default: none Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.

Physical Settings


The Physical Settings section is used to create associations with physical interfaces and bridge network interfaces.

Networking rutos manual interfaces interface configuration physical settings.png

Field Value Description
Bridge interfaces off | on; default: off Bridges physical interfaces specified in this configuration.
Enable STP off | on; default: off Turns the use of Spanning Tree Protocol (STP) for this interface on or off.
Note: this field becomes visible when 'Bridge interfaces' is set to on.
Interface network interface(s); default: none Ties this network interface to physical device interfaces such as Ethernet .

Firewall Settings


The Firewall Settings section is used to specify to which firewall zone if any this interface belongs. Assigning an interface to a zone may provide easier configuration of firewall rules. For example, instead of configuring separate rules for each WAN interface, you can add all WAN interfaces into a single firewall zone and make the rule apply to that zone instead.

More firewall zone settings can be configured from the Network → Firewall → General Settings → [[{{{name}}}_Firewall#Zones|Zones]] section.

Networking rutos manual interfaces interface configuration firewall settings.png

Field Value Description
Create / Assign firewall-zone firewall zone; default: none Assigns this interface to the specified firewall zone.

DHCP Server


A DHCP (Dynamic Host Configuration Protocol) server is a service that can automatically configure the TCP/IP settings of any device that requests such a service. If you connect a device that has been configured to obtain an IP address automatically, the DHCP server will lease out an IP address from the available IP pool and the device will be able to communicate within the private network.

Networking rutx manual lan static dhcp server scheme v1.png

To make the DHCP Server section visible, set interface protocol to Static.

DHCP Server: General Setup


The General Setup section is used to set up the main operating parameters of the DHCP server.

[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}.png|border|class=tlt-border]]

Field Value Description
Enable DHCP Enable | Disable | DHCP Relay*; default: Enable Turns the DHCP server on or off or enables DHCP relay*.
If DHCP Relay* is selected, you will be prompted to enter an IP address of another DHCP server in your LAN. In this case, whenever a new machine connects to this device, it will redirect any DHCP requests to the specified DHCP Server.
Start integer [1..255]; default: 100 The starting IP address value. e.g., if your device’s LAN IP is 192.168.1.1 and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [192.168.1.0..192.168.1.254] (192.168.1.255 is a special unavailable address). If the Start value is set to 100 then the DHCP server will only lease out addresses starting from 192.168.1.100.
Limit integer [1..255]; default: 150 How many addresses the DHCP server can lease out. Continuing from the example above: if the start address is 192.168.1.100 and the server can lease out 150 addresses, available addresses will be from 192.168.1.100 to 192.168.1.249 (100 + 150 – 1 = 249; this is because the first address is inclusive).
Lease time integer [1..999999]; default: 12
integer [2..999999]*
integer [120..999999]**
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).
The minimal amount of time that can be specified is 2 minutes.
*If selected Units is Minutes.
**If selected Units is seconds.
Units Hours | Minutes | Seconds; default: Hours Lease time units.

* When an interface is set to act as a DHCP Relay, it redirects all received DHCP request messages to another specified DHCP server:

Networking rutx manual lan static dhcp server relay scheme v2.png

DHCP Server: Advanced Settings


Refer to the table below for information on the Advanced Settings section.

Networking rutos manual interfaces interface configuration dhcp server advanced settings.png

Field Value Description
Dynamic DHCP off | on; default: on Enables dynamic allocation of client addresses. If this is disabled, only clients that have static IP leases will be served.
Force off | on; default: off The DHCP force function ensures that the device will always start it’s DHCP server, even if there is another DHCP server already running in the its network. By default the device’s DHCP server will not start when it is connected to a network segment that already has a working DHCP server.
IPv4 Netmask netmask; default: none Sends a different netmask than the LAN netmask to DHCP clients.
DHCP Options dhcp options; default: none Additional options to be added to the DHCP server. For example with '26,1470' or 'option:mtu, 1470' you can assign an MTU value per DHCP. You can find more information on DHCP Options here.

DHCP Server: IPv6 Settings


Refer to the table below for information on the IPv6 Settings section.

Networking rutos manual interfaces interface configuration dhcp server ipv6 settings.png

Field Value Description
Router Advertisement Service Disabled | Relay mode | Server mode | Hybrid mode; default: Disabled Specifies whether router advertisements should be enabled (server mode), relayed or disabled.
DHCPv6 Service Disabled | Relay mode | Server mode | Hybrid mode; default: Disabled Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled).
NDP Proxy Disabled | Relay mode | Hybrid mode; default: Disabled Specifies whether NDP should be relayed or disabled.
DHCPv6 Mode Stateless | Stateful-only | Stateless + stateful; default: Stateless + stateful Router announcement (RA) mode.
Always announce default router off | on; default: off Default router lifetime in the the router announcement (RA) message will be set if default route is present and a global IPv6 address or if default route is present but no global IPv6 address or neither of both conditions.
Announced DNS server ip; default: none Supplements DHCP-assigned DNS server entries with ones specified in this field.
Announced DNS domains ip; default: none DNS domain handed out to DHCP clients.

Static Lease


Static IP leases 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.

To make the Static Lease section visible, set interface protocol to Static.


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.

Networking rutos manual interfaces interface configuration static lease add button.png

You should be redirected to the Settings page for that lease, which should look similar to this:

Networking rutos manual interfaces interface configuration static lease settings.png

Field Value Description
MAC address mac; default: none MAC address of a device that will connect to this network interface.
IP address ip; default: none The IP address that will be reserved for the specified device.

After you click 'Save & Apply' you will be redirected back to the Network Interfaces page. If you wish to modify the lease later, you can find in the Static Lease list. Simply click the 'Edit' button next to it in order to enter the Settings page for the Static Lease.

Networking rutos manual interfaces interface configuration static lease edit button.png


UDP Broadcast Relay


The UDP Broadcast Relay will listen for broadcast traffic on the specified port and relay that traffic to the specified interface(s).

Note: UDP Broadcast Relay is additional software that can be installed from the Services → [[{{{name}}} Package Manager|Package Manager]] page.

Networking rutos manual interfaces interface configuration udp broadcast relay.png

Field Value Description
Enable off | on; default: off Turns UDP Broadcast Relay on or off.
Port integer [0..655353]; default: none UDP port to listen for broadcast traffic.
Interfaces network interface(s); default: none The interface(s) to which the traffic will be redirected to.


[[Category:{{{name}}} Network section]]