Changes

Template:Networking rutos manual interfaces (view source)

Revision as of 09:55, 14 March 2023

10,398 bytes added ,  09:55, 14 March 2023
→‎DHCP Server: General Setup: updated DHCP server information and pictures.
Line 1: Line 1: −
{{Template:Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
−
| fw_version = {{{series}}}_R_00.02.05.1
+
| fw_version ={{Template: Networking_rutos_manual_latest_fw
−
| series    = {{{series}}}
+
| series = {{{series}}}
 +
| name  = {{{name}}}
 +
}}
 
}}
 
}}
   Line 18: Line 20:  
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_v1.png|border|class=tlt-border]] |
 +
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_{{{lan}}}_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}_v1{{#ifeq:{{{series}}}|TRB5|_trb5|}}.png|border|class=tlt-border]]|}}
 +
 
 
==Add Interface==
 
==Add Interface==
   Line 80: Line 84:  
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_edit_button_lan_{{{lan}}}.png]]
+
[[File:Networking_rutos_manual_interfaces_network_interfaces_edit_button_lan_{{{lan}}}{{#ifeq:{{{series}}}|TRB5|_trb5|}}.png]]
    
===General Setup===
 
===General Setup===
Line 100: Line 104:  
     <tr>
 
     <tr>
 
       <td>IPv4 address</td>
 
       <td>IPv4 address</td>
−
       <td>ip4; default[for LAN]: <b>192.168.1.1</b></td>
+
       <td>ip4; default[for LAN]: <b>{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.1|#default=192.168.1.1}}</b></td>
 
       <td>The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.</td>
 
       <td>The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.</td>
 
     </tr>
 
     </tr>
Line 206: Line 210:  
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.
    +
=====Mode: NAT=====
 +
----
 
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
   Line 220: Line 226:  
             <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><b>Bridge</b> - 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><b>Passthrough</b> - 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>{{#ifeq: {{{dualsim}}} | 1 |
   
     <tr>
 
     <tr>
 
     <td>PDP Type</td>
 
     <td>PDP Type</td>
Line 230: Line 235:  
         <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>
Line 265: Line 271:  
         <td>NONE <nowiki>|</nowiki> PAP <nowiki>|</nowiki> CHAP; default: <b>NONE</b></td>
 
         <td>NONE <nowiki>|</nowiki> PAP <nowiki>|</nowiki> CHAP; default: <b>NONE</b></td>
 
         <td>Authentication method that your GSM carrier uses to authenticate new connections on its network. If you select PAP or CHAP, you will also be required to enter a username and password.</td>
 
         <td>Authentication method that your GSM carrier uses to authenticate new connections on its network. If you select PAP or CHAP, you will also be required to enter a username and password.</td>
 +
    </tr>
 +
</table>
 +
 +
=====Mode: Passthrough=====
 +
----
 +
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_mobile_passthrough_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Mode</td>
 +
      <td>NAT <nowiki>|</nowiki> Bridge <nowiki>|</nowiki> Passthrough; default: <b>NAT</b></td>
 +
      <td>Mobile connection operating mode.
 +
            <ul>
 +
                <li><b>NAT</b> - the mobile connection uses NAT (network address translation).</li>
 +
                <li><b>Bridge</b> - 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><b>Passthrough</b> - 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>
 +
        </td>
 +
    <tr>
 +
    <td>Subnet selection</td>
 +
        <td>Auto {{!}} P2P; default: <b>Auto</b></td>
 +
        <td>Subnet selection method.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
     <td><span style="color: red;">Bridge</span> <nowiki>|</nowiki> <span style="color: cornflowerblue;">Passthrough</span>: MAC Address</td>
+
     <td>PDP Type</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>
 +
    </tr>
 +
    </tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||
 +
    <tr>
 +
    <td>SIM</td>
 +
        <td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td>
 +
        <td>Selects which SIM slot will be used for this interface.</td>
 +
    </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>
 +
    <td>Auto APN</td>
 +
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 +
        <td>The Auto APN feature scans an internal Android APN database and selects an APN based on the SIM card's operator and country. If the first automatically selected APN doesn't work, it attempts to use the next existing APN from the database.
 +
        </td>
 +
    </tr>
 +
    <tr>
 +
    <td>APN / Custom APN</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>An Access Point Name (APN) is a gateway between a GSM, GPRS, 3G or 4G mobile network and another computer network. Depending on the contract, some operators may require you to use an APN just to complete the registration on a network. In other cases, APN is used to get special parameters from the operator (e.g., a [[Private_and_Public_IP_Addresses#Public_IP_address|public IP address]]) depending on the contract.<br>An APN Network Identifier cannot start with any of the following strings:
 +
            <ul>
 +
                <li>rac;</li>
 +
                <li>lac;</li>
 +
                <li>sgsn;</li>
 +
                <li>rnc;</li>
 +
            </ul>it cannot end in:
 +
            <ul>
 +
                <li>.gprs;</li>
 +
            </ul>and it cannot contain the asterisk symbol (<b>*</b>).
 +
        </td>
 +
    </tr>
 +
    <tr>
 +
    <td>Authentication Type</td>
 +
        <td>NONE <nowiki>|</nowiki> PAP <nowiki>|</nowiki> CHAP; default: <b>NONE</b></td>
 +
        <td>Authentication method that your GSM carrier uses to authenticate new connections on its network. If you select PAP or CHAP, you will also be required to enter a username and password.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Disable DHCP</td>
 +
        <td>on <nowiki>|</nowiki> off; default: <b>on</b></td>
 +
        <td>Disables dynamic allocation of client addresses when toggled off</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Lease Time</td>
 +
        <td>integer; default: <b>1</b></td>
 +
        <td>Expiry time of leased address. The minimum value for hours is 1, the minimum value for minutes is 2 and the minimum value for seconds is 120</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Units</td>
 +
        <td>Hours <nowiki>|</nowiki> Minutes <nowiki>|</nowiki> Second; default: <b>Hours</b></td>
 +
        <td>Specifies the time measurement unit</td>
 +
    </tr>
 +
    <tr>
 +
    <td>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>
 +
 +
=====Mode: Bridge=====
 +
----
 +
[[File:Networking_rutos_manual_interfaces_interface_configuration_general_mobile_bridge_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Mode</td>
 +
      <td>NAT {{!}} Bridge {{!}} Passthrough; default: <b>NAT</b></td>
 +
      <td>Mobile connection operating mode.
 +
            <ul>
 +
                <li><b>NAT</b> - the mobile connection uses NAT (network address translation).</li>
 +
                <li><b>Bridge</b> - 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><b>Passthrough</b> - 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>
 +
        </td>
 +
    <tr>
 +
    <td>Subnet selection</td>
 +
        <td>Auto {{!}} P2P; default: <b>Auto</b></td>
 +
        <td>Subnet selection method.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>PDP Type</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>
 +
    </tr>{{#ifeq: {{{dualsim}}} | 1 | {{#ifeq: {{{dualmodem}}} | 1 ||
 +
    <tr>
 +
    <td>SIM</td>
 +
        <td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td>
 +
        <td>Selects which SIM slot will be used for this interface.</td>
 +
    </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>
 +
    <td>Auto APN</td>
 +
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 +
        <td>The Auto APN feature scans an internal Android APN database and selects an APN based on the SIM card's operator and country. If the first automatically selected APN doesn't work, it attempts to use the next existing APN from the database.
 +
        </td>
 +
    </tr>
 +
    <tr>
 +
    <td>APN / Custom APN</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>An Access Point Name (APN) is a gateway between a GSM, GPRS, 3G or 4G mobile network and another computer network. Depending on the contract, some operators may require you to use an APN just to complete the registration on a network. In other cases, APN is used to get special parameters from the operator (e.g., a [[Private_and_Public_IP_Addresses#Public_IP_address|public IP address]]) depending on the contract.<br>An APN Network Identifier cannot start with any of the following strings:
 +
            <ul>
 +
                <li>rac;</li>
 +
                <li>lac;</li>
 +
                <li>sgsn;</li>
 +
                <li>rnc;</li>
 +
            </ul>it cannot end in:
 +
            <ul>
 +
                <li>.gprs;</li>
 +
            </ul>and it cannot contain the asterisk symbol (<b>*</b>).
 +
        </td>
 +
    </tr>
 +
    <tr>
 +
    <td>Authentication Type</td>
 +
        <td>NONE <nowiki>|</nowiki> PAP <nowiki>|</nowiki> CHAP; default: <b>NONE</b></td>
 +
        <td>Authentication method that your GSM carrier uses to authenticate new connections on its network. If you select PAP or CHAP, you will also be required to enter a username and password.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>MAC Address</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>
 +
    </tr>
 +
</table>
 +
 +
{{#switch: {{{series}}}
 +
| TRB1|TRB5|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]].
 +
}}
 
|}}
 
|}}
   Line 282: Line 460:  
<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.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_static_v3.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 289: Line 467:  
         <th>Value</th>
 
         <th>Value</th>
 
         <th>Description</th>
 
         <th>Description</th>
−
    </tr>
  −
    <tr>
  −
        <td>Bring up on boot</td>
  −
        <td>off | on; default: <b>on</b></td>
  −
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 304: Line 477:  
         <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 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>
 
     <tr>
 
     <tr>
Line 316: Line 494:  
     </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><span style="color: red;">integer [0..64]</span> | Disabled; default: <b>Disabled</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>IPv6 address</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 <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>IPv6 routed prefix</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>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td><span style="color: red;">IPv6 assignment hint</span></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 350: Line 528:  
         <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>
   Line 356: Line 535:  
<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_interface_configuration_advanced_settings_dhcp.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcp_v4.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 363: Line 542:  
         <th>Value</th>
 
         <th>Value</th>
 
         <th>Description</th>
 
         <th>Description</th>
−
    </tr>
  −
    <tr>
  −
        <td>Bring up on boot</td>
  −
        <td>off | on; default: <b>on</b></td>
  −
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 388: Line 562:  
         <td>off | on; default: <b>on</b></td>
 
         <td>off | on; default: <b>on</b></td>
 
         <td>When checked, creates a default route for the interface.</td>
 
         <td>When checked, creates a default route for the interface.</td>
−
    </tr>
  −
    <tr>
  −
        <td>Use DNS servers advertised by peer</td>
  −
        <td><span style="color: red;">off</span> | on; default: <b>on</b></td>
  −
        <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
  −
    </tr>
  −
    <tr>
  −
        <td><span style="color: red;">Use custom DNS servers</span></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>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 403: Line 567:  
         <td>integer; default: <b>none</b></td>
 
         <td>integer; 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>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>ip4; default: <b>none</b></td>
 +
        <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 423: Line 592:  
         <td>integer [1..9200]; default: <b>none</b></td>
 
         <td>integer [1..9200]; default: <b>none</b></td>
 
         <td>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.</td>
 
         <td>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.</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>
 
</table>
 
</table>
Line 430: Line 604:  
<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_interface_configuration_advanced_settings_dhcpv6.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_dhcpv6_v4.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 437: Line 611:  
         <th>Value</th>
 
         <th>Value</th>
 
         <th>Description</th>
 
         <th>Description</th>
−
    </tr>
  −
    <tr>
  −
        <td>Bring up on boot</td>
  −
        <td>off | on; default: <b>on</b></td>
  −
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 459: Line 628:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>Use DNS servers advertised by peer</td>
+
         <td>Use custom DNS servers</td>
−
         <td><span style="color: red;">off</span> | on; default: <b>on</b></td>
+
         <td>ip4; default: <b>none</b></td>
−
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
+
         <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
−
    </tr>
  −
    <tr>
  −
        <td><span style="color: red;">Use custom DNS servers</span></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>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 488: Line 652:  
         <td>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.</td>
 
         <td>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.</td>
 
     <tr>
 
     <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>
 
</table>
 
</table>
   Line 494: Line 663:  
<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_interface_configuration_advanced_settings_pppoe.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_pppoe_v5.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 501: Line 670:  
         <th>Value</th>
 
         <th>Value</th>
 
         <th>Description</th>
 
         <th>Description</th>
−
    </tr>
  −
    <tr>
  −
        <td>Bring up on boot</td>
  −
        <td>off | on; default: <b>on</b></td>
  −
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 533: Line 697:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>Use DNS servers advertised by peer</td>
+
         <td>Use custom DNS servers</td>
−
         <td><span style="color: red;">off</span> | on; default: <b>on</b></td>
+
        <td>ip4; default: <b>none</b></td>
−
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
+
        <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
 +
    </tr>
 +
    <tr>
 +
         <td>VLAN tag value</td>
 +
        <td>integer [0..7]; default: <b>none</b></td>
 +
         <td>VLAN tag value.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td><span style="color: red;">Use custom DNS servers</span></td>
+
         <td>VLAN priority</td>
−
         <td>off | on; default: <b>on</b></td>
+
         <td>integer [0..4095]; default: <b>none</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>VLAN priority.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 566: Line 735:  
         <td>integer [1..1500]; default: <b>none</b></td>
 
         <td>integer [1..1500]; default: <b>none</b></td>
 
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</td>
 
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</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>
 
</table>
 
</table>
Line 573: Line 747:  
<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_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 580: Line 754:  
         <th>Value</th>
 
         <th>Value</th>
 
         <th>Description</th>
 
         <th>Description</th>
−
    </tr>
  −
    <tr>
  −
        <td>Bring up on boot</td>
  −
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
  −
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 597: Line 766:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>Use DNS servers advertised by peer</td>
+
         <td>Use custom DNS servers</td>
−
         <td><span style="color: red;">off</span> <nowiki>|</nowiki> on; default: <b>on</b></td>
+
         <td>ip4; default: <b>none</b></td>
−
         <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
+
         <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
−
    </tr>
  −
    <tr>
  −
        <td><span style="color: red;">Use custom DNS servers</span></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>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 615: Line 779:  
         <td>integer [1..9200]; default: <b>none</b></td>
 
         <td>integer [1..9200]; default: <b>none</b></td>
 
         <td>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.</td>
 
         <td>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.</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>
 
</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.
   −
[[File:Networking_rutos_manual_interfaces_interface_configuration_physical_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_physical_settings_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 631: Line 801:  
     <tr>
 
     <tr>
 
         <td>Bridge interfaces</td>
 
         <td>Bridge interfaces</td>
−
         <td>off | <span style="color: red;">on</span>; default: <b>off</b></td>
+
         <td>off | <span style="color: #1550bf; font-weight: bold;">on</span>; default: <b>on</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><span style="color: red;">Enable STP</span></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.<br><b>Note:</b> this field becomes visible when 'Bridge interfaces' is set to <i>on</i></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>
 +
        <td><span style="color: red;">Enable IGMP</span></td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Enabless IGMP snooping on this bridge.<br><b>Note:</b> this field becomes visible when 'Bridge interfaces' is set to <i>on</i> and 'Protocol' is set to <i>PPPoE</i>.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 678: Line 853:  
[[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 684: Line 859:  
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_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_general_setup_lan_{{{lan}}}_v1.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 698: Line 873:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>Start</td>
+
         <td>Start IP</td>
−
         <td>integer [1..255]; default: <b>100</b></td>
+
         <td>ip4; default: <b>{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.100|#default=192.168.1.100}}</b></td>
−
         <td>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.<b>100</b>.</td>
+
         <td>The starting IP address of the DHCP server IP address range. E.g., if your device’s LAN IP is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.1|#default=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 [{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.0|#default=192.168.1.0}}..{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.254|#default=192.168.1.254}}] ({{#switch:{{{series}}}|TRB1|TRB5=192.168.2.255|#default=192.168.1.255}} is a special unavailable address). If the subnet of your LAN IP address changes, this value needs to be changed accordingly.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>Limit</td>
+
         <td>End IP</td>
−
         <td>integer [1..255]; default: <b>150</b></td>
+
         <td>ip4; default: <b>{{#switch:{{{series}}}|TRB1|TRB5=192.168.2.249|#default=192.168.1.249}}</b></td>
−
         <td>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.<b>100</b> to 192.168.1.<b>249</b> (<i>100 + 150 – 1 = 249</i>; this is because the first address is inclusive).</td>
+
         <td>The ending IP address of the DHCP server IP address range. Continuing from the example above: if the start address is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.<b>100</b>|#default=192.168.1.<b>100</b>}} and the end address is {{#switch:{{{series}}}|TRB1|TRB5=192.168.2.<b>249</b>|#default=192.168.1.<b>249</b>}}, available addresses will be distributed from that range. If the subnet of your LAN IP address changes, this value needs to be changed accordingly.</td>
 
     </tr>
 
     </tr>
 
     <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 722: Line 902:  
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_interface_configuration_dhcp_server_advanced_settings.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_dhcp_server_advanced_settings_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 749: Line 929:  
         <td>dhcp options; default: <b>none</b></td>
 
         <td>dhcp options; default: <b>none</b></td>
 
         <td>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 [https://technet.microsoft.com/en-us/library/cc958941.aspx here].</td>
 
         <td>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 [https://technet.microsoft.com/en-us/library/cc958941.aspx here].</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force DHCP options</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>If enabled, DHCP options will be sent even if it's not requested.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 805: Line 990:  
<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.
Line 841: Line 1,028:  
----
 
----
 
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]]
Line 863: Line 1,055:  
     </tr>
 
     </tr>
 
</table>|}}
 
</table>|}}
−
{{#ifeq: {{{mobile}}} | 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:{{{series}}}|TRB5||{{#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_v2.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 911: Line 1,134:  
         <td>phone number; default: <b>none</b></td>
 
         <td>phone number; default: <b>none</b></td>
 
         <td>Recipient's phone numbers.</td>
 
         <td>Recipient's phone numbers.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Data limit clear due</td>
 +
        <td><b>none</b></td>
 +
        <td>Display the date of the next automatic data limit clear.</td>
 
     </tr>
 
     </tr>
 
</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]]
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/72819...105187"

Navigation menu