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

From Teltonika Networks Wiki
(38 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
{{Template: Networking_device_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
−
| series = {{{series}}}
+
| fw_version ={{Template: Networking_rutos_manual_latest_fw
−
| name  = {{{name}}}
 
−
| fw_version ={{Template: Networking_device_manual_latest_fw
 
 
  | series = {{{series}}}
 
  | series = {{{series}}}
 
  | name  = {{{name}}}
 
  | name  = {{{name}}}
 
  }}
 
  }}
 
}}
 
}}
−
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
+
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
−
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
+
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
 
==Summary==
 
==Summary==
  
Line 14: Line 12:
  
 
This manual page provides an overview of the WAN windows in {{{name}}} devices.
 
This manual page provides an overview of the WAN windows in {{{name}}} devices.
−
 
−
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 
−
| series = {{{series}}}
 
−
}}
 
  
 
==WAN==
 
==WAN==
Line 23: Line 17:
 
The <b>WAN</b> section displays WAN network interfaces currently existing on this device.
 
The <b>WAN</b> section displays WAN network interfaces currently existing on this device.
  
−
[[File:Networking_rutos_manual_wan_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}_v3.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}{{#ifeq:{{{series}}}|TRB5|_trb5|}}.png|border|class=tlt-border]]
  
−
From here you can turn the interfaces, enable/disable interface's failover, create interfaces, change their priority<span class="asterisk">*</span> or enter an interface's configuration page.
+
From here you can turn the interfaces on or off, create interfaces, change their priority<span class="asterisk">*</span> or enter an interface's configuration page.
 
----
 
----
 
<font size="-1"><span class="asterisk">*</span> You can change the priority by dragging and dropping an interface to another position. Moving an interface changes its metric value in the configuration file. Interfaces that are higher on the list have greater priority.</font>
 
<font size="-1"><span class="asterisk">*</span> You can change the priority by dragging and dropping an interface to another position. Moving an interface changes its metric value in the configuration file. Interfaces that are higher on the list have greater priority.</font>
−
 
−
If you hover mouse over the question mark [[File:Networking_rutos_manual_wan_question_mark.png]] global IPv6 addresses and IPv6 prefix delegation will be displayed.
 
−
 
−
[[File:Networking_rutos_manual_wan_question_mark_info.png|border|class=tlt-border]]
 
  
 
==Interface configuration==
 
==Interface configuration==
Line 79: Line 69:
 
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_wan_interfaces_edit_button_v3.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_interfaces_edit_button.png|border|class=tlt-border]]
  
 
===General Setup===
 
===General Setup===
Line 89: Line 79:
 
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.  
  
−
[[File:Networking_rutos_manual_wan_configuration_general_settings_static_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_settings_static.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 104: Line 94:
 
     <tr>
 
     <tr>
 
       <td>IPv4 address</td>
 
       <td>IPv4 address</td>
−
       <td>ip4; default: <b>none</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>
 
     <tr>
 
     <tr>
 
       <td>IPv4 netmask</td>
 
       <td>IPv4 netmask</td>
−
       <td>netmask; default: <b>255.255.255.0</b></td>
+
       <td>netmask; default[for LAN]: <b>255.255.255.0</b></td>
 
       <td>The IPv4 netmask of this interface. A <b>[[What is a Netmask?|netmask]]</b> 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.</td>
 
       <td>The IPv4 netmask of this interface. A <b>[[What is a Netmask?|netmask]]</b> 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.</td>
 
     </tr>
 
     </tr>
Line 133: Line 123:
 
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_wan_configuration_general_setup_dhcp_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_setup_dhcp.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 157: Line 147:
 
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_wan_configuration_general_setup_dhcpv6_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_setup_dhcpv6.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 176: Line 166:
 
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)|}}.
 
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_wan_configuration_general_setup_pppoe_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_setup_pppoe.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 211: Line 201:
 
</table>
 
</table>
  
−
{{#ifeq:{{{mobile}}}|1|
 
 
====General Settings: Mobile====
 
====General Settings: Mobile====
 
----
 
----
Line 218: Line 207:
 
=====Mode: NAT=====
 
=====Mode: NAT=====
 
----
 
----
−
[[File:Networking_rutos_manual_wan_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 238: Line 227:
 
     <tr>
 
     <tr>
 
     <td>PDP Type</td>
 
     <td>PDP Type</td>
−
         <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4/IPv6</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>  
Line 282: Line 271:
 
=====Mode: Passthrough=====
 
=====Mode: Passthrough=====
 
----
 
----
−
[[File:Networking_rutos_manual_wan_configuration_general_mobile_passthrough_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_mobile_passthrough_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 371: Line 360:
 
=====Mode: Bridge=====
 
=====Mode: Bridge=====
 
----
 
----
−
[[File:Networking_rutos_manual_wan_configuration_general_mobile_bridge_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_general_mobile_bridge_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 440: Line 429:
 
         <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|TRB5|RUT36X =
 
−
| RUT9M = {{#ifeq: {{{name}}} | RUT901 | |
 
−
=====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]].}}
 
−
| RUT2M = {{#ifeq: {{{name}}} | RUT200 | |
 
−
=====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]].}}
 
−
| 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]].
 
−
}}
 
  
 
===IPv6 Settings===
 
===IPv6 Settings===
Line 470: Line 439:
 
<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_wan_configuration_ipv6_settings_static_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_ipv6_settings_static.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 514: Line 483:
 
<b>Advanced Settings</b> information for <b>DHCPv6</b> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <b>DHCPv6</b> protocol is provided in the table below.
  
−
[[File:Networking_rutos_manual_wan_configuration_ipv6_settings_dhcpv6_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_ipv6_settings_dhcpv6.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 543: Line 512:
 
<b>Advanced Settings</b> information for <b>PPPoE</b> protocol is provided in the table below.
 
<b>Advanced Settings</b> information for <b>PPPoE</b> protocol is provided in the table below.
  
−
[[File:Networking_rutos_manual_wan_configuration_ipv6_settings_pppoe_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_ipv6_settings_pppoe.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 599: Line 568:
 
         <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.<br>
 
         <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.<br>
 
           <ul>
 
           <ul>
−
                 <li>'''Note:''' Interface(s): have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
+
                 <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
−
                 <li>'''Note:''' Interface(s): have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
+
                 <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
 
           </ul>     
 
           </ul>     
 
         </td>
 
         </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>IP4 table</td>
+
         <td>IP4table</td>
 
         <td>integer [0..99999999]; default: <b>none</b></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>
 
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
Line 644: Line 613:
 
====Advanced Settings: DHCP====
 
====Advanced Settings: DHCP====
 
----
 
----
−
<b>Advanced Settings</b> information for <b>DHCP</b> 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_wan_configuration_advanced_settings_dhcp_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_advanced_settings_dhcp.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 699: Line 668:
 
         <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.<br>
 
         <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.<br>
 
           <ul>
 
           <ul>
−
                 <li>'''Note:''' Interface(s): have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
+
                 <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
−
                 <li>'''Note:''' Interface(s): have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
+
                 <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
 
           </ul></td>
 
           </ul></td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>IP4 table</td>
+
         <td>IP4table</td>
 
         <td>integer [0..99999999]; default: <b>none</b></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>
 
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
Line 712: Line 681:
 
====Advanced Settings: DHCPv6====
 
====Advanced Settings: DHCPv6====
 
----
 
----
−
<b>Advanced Settings</b> information for <b>DHCPv6</b> 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_wan_configuration_advanced_settings_dhcpv6_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_advanced_settings_dhcpv6.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 731: Line 700:
 
         <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 
         <td>off <nowiki>|</nowiki> 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 gateway metric</td>
 
−
        <td>integer; default: <b>2</b></td>
 
−
        <td>The configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Lower metric means higher priority.</td>
 
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 741: Line 705:
 
         <td>ip4; default: <b>none</b></td>
 
         <td>ip4; default: <b>none</b></td>
 
         <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
 
         <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
 +
    </tr>
 +
    <tr>
 +
        <td>Custom delegated IPv6-prefix</span></td>
 +
        <td>ip6 prefix; default: <b>none</b></td>
 +
        <td>Uses an (additional) user-provided IPv6 prefix for distribution to clients.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 757: Line 726:
 
         <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.<br>
 
         <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.<br>
 
           <ul>
 
           <ul>
−
                 <li>'''Note:''' Interface(s): have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
+
                 <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
−
                 <li>'''Note:''' Interface(s): have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
+
                 <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
 
           </ul></td>
 
           </ul></td>
−
    </tr>
 
 
     <tr>
 
     <tr>
−
         <td>IP6 table</td>
+
    <tr>
−
         <td>integer [0..2^46]; default: <b>none</b></td>
+
         <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>
 
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
Line 770: Line 739:
 
====Advanced Settings: PPPoE====
 
====Advanced Settings: PPPoE====
 
----
 
----
−
<b>Advanced Settings</b> information for <b>PPPoE</b> 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_wan_configuration_advanced_settings_pppoe_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_advanced_settings_pppoe.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 837: Line 806:
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>IP4 table</td>
+
         <td>IP4table</td>
 
         <td>integer [0..99999999]; default: <b>none</b></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>
 
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
−
 
+
{{#ifeq: {{{mobile}}} | 1 |
−
{{#ifeq:{{{mobile}}}|1|
 
 
====Advanced Settings: Mobile====
 
====Advanced Settings: Mobile====
 
----
 
----
−
<b>Advanced Settings</b> information for <b>Mobile</b> protocol is provided in the table below.
+
<b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
−
 
 
−
{{#switch: {{{name}}} | RUTM50 | RUTX50 | TRB500=
 
  
−
[[File:Networking_rutos_manual_wan_configuration_advanced_settings_mobile_v3.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_advanced_settings_mobile_dualsim_{{{dualsim}}}_v5.png|border|class=tlt-border]]
−
| #default=
 
−
[[File:Networking_rutos_manual_wan_configuration_advanced_settings_mobile_v2.png|border|class=tlt-border]]}}
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 865: Line 829:
 
         <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>
−
    {{#switch: {{{name}}} | RUTM50 | RUTX50 | TRB500=
 
−
    <tr>
 
−
        <td>Framed routing</td>
 
−
        <td>off {{!}} on; default: <b>off</b></td>
 
−
        <td>Allows static routes to be set up for subscribers, enabling connectivity from external networks to IP networks behind a user equipment.</td>
 
−
    </tr>
 
−
    | #default=}}
 
 
     <tr>
 
     <tr>
 
         <td>Use gateway metric</td>
 
         <td>Use gateway metric</td>
Line 884: Line 841:
 
     <tr>
 
     <tr>
 
         <td>Override MTU</td>
 
         <td>Override MTU</td>
−
         <td>integer [98..65535]; default: <b>none</b></td>
+
         <td>integer [1..9200]; default: <b>none</b></td>
−
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet. If Override MTU field will be left – empty dynamic MTU will be used.</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>
 
     <tr>
−
         <td>IP4 table</td>
+
         <td>IP4table</td>
 
         <td>integer [0..99999999]; default: <b>none</b></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>
 
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
Line 898: Line 855:
 
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_wan_configuration_physical_settings_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_wan_configuration_physical_settings.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 924: Line 881:
 
More firewall zone settings can be configured from the Network → Firewall → General Settings → [[{{{name}}}_Firewall#Zones|Zones]] section.
 
More firewall zone settings can be configured from the Network → Firewall → General Settings → [[{{{name}}}_Firewall#Zones|Zones]] section.
  
−
[[File:Networking_rutos_manual_wan_configuration_firewall_settings_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_interface_configuration_firewall_settings.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 939: Line 896:
 
</table>
 
</table>
  
−
{{#ifeq:{{{mobile}}}|1|
+
====Advanced Settings: DHCP====
−
===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.
+
<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_v4.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built-in IPv6 management</td>
 +
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</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>
 +
    </tr>
 +
    <tr>
 +
        <td>Use broadcast flag</td>
 +
        <td>off <nowiki>|</nowiki> 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 <nowiki>|</nowiki> 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>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>
 +
    </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>
 +
        <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>
 +
        <td>Override MAC address</td>
 +
        <td>mac; default: <b>none</b></td>
 +
        <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Override MTU</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.<br>
 +
          <ul>
 +
                <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
 +
                <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
 +
          </ul></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>
 +
</table>
  
−
<i>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to Mobile</b>.</i>
+
====Advanced Settings: DHCPv6====
 +
----
 +
<b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below.
  
−
[[File:Networking_rutos_manual_wan_configuration_mobile_mobile_data_limit_v3.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">
 
     <tr>
 
     <tr>
 
         <th>Field</th>
 
         <th>Field</th>
−
      <th>Value</th>
+
        <th>Value</th>
−
      <th>Description</th>
+
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built in IPv6-management</td>
 +
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</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>
 +
    </tr>
 +
    <tr>
 +
        <td>Use default gateway</td>
 +
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 +
        <td>When checked, creates a default route for the interface.</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>
 +
        <td>Custom delegated IPv6-prefix</span></td>
 +
        <td>ip6 prefix; default: <b>none</b></td>
 +
        <td>Uses an (additional) user-provided IPv6 prefix for distribution to clients.</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>Override MAC address</td>
 +
        <td>mac; default: <b>none</b></td>
 +
        <td>When set, uses a user-defined MAC address for the interface instead of the default one.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Override MTU</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.<br>
 +
          <ul>
 +
                <li>'''Note:''' Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.</li>
 +
                <li>'''Note:''' Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.</li>
 +
          </ul></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>
 +
</table>
 +
 
 +
====Advanced Settings: PPPoE====
 +
----
 +
<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_v5.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built-in IPv6 management</td>
 +
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</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>
 +
    </tr>
 +
    <tr>
 +
        <td>Obtain IPv6 address</td>
 +
        <td>Automatic <nowiki>|</nowiki> Disabled | Manual; default: <b>Automatic</b></td>
 +
        <td>Defines behaviour for obtaining an IPv6 address.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use default gateway</td>
 +
        <td>off <nowiki>|</nowiki> 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>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>
 +
    </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>
 +
        <td>VLAN tag value</td>
 +
        <td>integer [0..7]; default: <b>none</b></td>
 +
        <td>VLAN tag value.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>VLAN priority</td>
 +
        <td>integer [0..4095]; default: <b>none</b></td>
 +
        <td>VLAN priority.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>LCP echo failure threshold</td>
 +
        <td>integer; default: <b>none</b></td>
 +
        <td>Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>LCP echo interval</td>
 +
        <td>integer; default: <b>none</b></td>
 +
        <td>Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Host-Uniq tag content</td>
 +
        <td>raw hex-encoded bytes; default: <b>none</b></td>
 +
        <td>Leave empty unless your ISP require this.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Inactivity timeout</td>
 +
        <td>mac; default: <b>none</b></td>
 +
        <td>Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Override MTU</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>
 +
    </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>
 +
{{#ifeq: {{{mobile}}} | 1 |
 +
====Advanced Settings: Mobile====
 +
----
 +
<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}}}_v5.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 
     <tr>
 
     <tr>
−
      <td>Enable data connection limit</td>
+
        <th>Field</th>
−
      <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
+
        <th>Value</th>
−
      <td>Turns mobile data limitations on or off.</td>
+
        <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
      <td>Data limit<span class="asterisk">*</span> (MB)</td>
+
        <td>Use built in IPv6-management</td>
−
      <td>integer; default: <b>1000</b></td>
+
        <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
−
      <td>The amount of data that is allowed to be downloaded over the specified period of time. When the limit is reached, the device will no longer be able to establish a data connection until the period is over or the data limit is reset.</td>
+
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 
     <tr>
 
     <tr>
−
    <td>Reset period</td>
+
        <td>Force link</td>
−
         <td>Month <nowiki>|</nowiki> Week <nowiki>|</nowiki> Day; default: <b>Day</b></td>
+
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
−
         <td>Data limit period after which the data counter is reset on the specified <i>Start day</i>.</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>
 
     <tr>
 
     <tr>
−
    <td>Reset time <nowiki>|</nowiki> Reset day</td>
+
        <td>Use custom DNS servers</td>
−
         <td>day [1..31] <nowiki>|</nowiki> day [Monday..Sunday] {{!}} hour [1..24]; default: <b>hour 0</b></td>
+
         <td>ip4; default: <b>none</b></td>
−
      <td>Specifies when the period of counting data usage should begin. After the period is over, the limit is reset and the count begins over again.</td>
+
        <td>Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used. </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
      <td>Enable SMS warning</td>
+
        <td>Use gateway metric</td>
−
      <td>off <nowiki>|</nowiki> <span style="color:blue">on</span>; default: <b>off</b></td>
+
        <td>integer; default: <b>none</b></td>
−
      <td>Turns SMS warning on or off. When turned on and configured, sends an SMS message to a specified number after the SIM card uses a specified amount of data.</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>
−
      <td><span style="color:blue">Warning threshold* (MB) (%)</span></td>
+
        <td>Override MTU</td>
−
      <td><li>MB - positive integer; default: <b>none</b></li> <li>% - interger [1..100]; default: <b>none</b></li></td>
+
        <td>integer [1..9200]; default: <b>none</b></td>
−
      <td>Send warning SMS message after threshold in MB is reached. Warning threshold cannot be higher than data limit!</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>
 
     <tr>
−
    <td><span style="color:blue">Phone number</span></td>
+
        <td>IP4table</td>
−
         <td>phone number; default: <b>none</b></td>
+
         <td>integer [0..99999999]; default: <b>none</b></td>
−
         <td>A phone number to send warning SMS message to.</td>
+
         <td>ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.</td>
 
     </tr>
 
     </tr>
 +
</table>|}}
 +
 +
===Physical Settings===
 +
----
 +
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_v2.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 
     <tr>
 
     <tr>
−
    <td>Data limit clear due</td>
+
        <th>Field</th>
−
         <td><b>none</b></td>
+
        <th>Value</th>
−
         <td>Display the date of the next automatic data limit clear.</td>
+
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bridge interfaces</td>
 +
        <td>off <nowiki>|</nowiki> <span style="color: #1550bf; font-weight: bold;">on</span>; default: <b>on</b></td>
 +
        <td>Bridges physical interfaces specified in this configuration.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable STP</td>
 +
         <td>off <nowiki>|</nowiki> 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>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable IGMP</td>
 +
        <td>off <nowiki>|</nowiki> 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>
 +
        <td>Interface</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|}}.</td>
 +
    </tr>{{#ifeq: {{{name}}}| RUTXR1 |
 +
    <tr>
 +
        <td>Port priority</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.<br><b>Note:</b> this field becomes visible when 'Interface' is set to <i>eth1</i>.</td>
 +
    </tr>|}}
 +
</table>
 +
 
 +
===Firewall Settings===
 +
----
 +
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.
 +
 
 +
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">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Create / Assign firewall-zone</td>
 +
        <td>firewall zone; default: <b>none</b></td>
 +
        <td>Assigns this interface to the specified firewall zone.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
  
−
<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 15:54, 7 September 2023

Template:Networking rutos manual fw disclosure


Summary

The WAN page is used to to set up WAN network interfaces, which are used to connect device with external networks.

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

WAN

The WAN section displays WAN network interfaces currently existing on this device.

[[File:Networking_rutos_manual_wan_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}.png|border|class=tlt-border]]

From here you can turn the interfaces on or off, create interfaces, change their priority* or enter an interface's configuration page.

* You can change the priority by dragging and dropping an interface to another position. Moving an interface changes its metric value in the configuration file. Interfaces that are higher on the list have greater priority.

Interface configuration

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

Different types of interfaces can be configured under different protocols:

Static DHCP DHCPv6 PPPoE

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

Networking rutos manual wan interfaces edit button.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 Settings: Static

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

Networking rutos manual wan configuration general settings static.png

Field Value Description
Enable on | off; default: on Enable interface.
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 Settings: DHCP

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

Networking rutos manual wan configuration general setup dhcp.png

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

General Settings: 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 wan configuration general setup dhcpv6.png

Field Value Description
Enable on | off; default: on Enable interface.

General Settings: PPPoE

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

Networking rutos manual wan configuration general setup pppoe.png

Field Value Description
Enable on | off; default: on Enable interface.
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.

General Settings: Mobile

The Mobile protocol is used to set up an interface which can establish a mobile WAN connection.

Mode: NAT

[[File:Networking_rutos_manual_wan_configuration_general_setup_mobile_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]

Field Value Description
Mode NAT | Bridge | Passthrough; default: NAT Mobile connection operating mode.
  • NAT - the mobile connection uses NAT (network address translation).
  • Bridge - 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.
  • Passthrough - 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.
PDP Type IPv4 | IPv6 | IPv4/IPv6; default: IPv4 Specifies what of address will be requested from the operator.
Auto APN off | on; default: on 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.
APN / Custom APN string; default: none 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 public IP address) depending on the contract.
An APN Network Identifier cannot start with any of the following strings:
  • rac;
  • lac;
  • sgsn;
  • rnc;
it cannot end in:
  • .gprs;
and it cannot contain the asterisk symbol (*).
Authentication Type NONE | PAP | CHAP; default: NONE 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.
Mode: Passthrough

[[File:Networking_rutos_manual_wan_configuration_general_mobile_passthrough_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]

Field Value Description
Mode NAT | Bridge | Passthrough; default: NAT Mobile connection operating mode.
  • NAT - the mobile connection uses NAT (network address translation).
  • Bridge - 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.
  • Passthrough - 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.
Subnet selection Auto | P2P; default: Auto Subnet selection method.
PDP Type IPv4 | IPv6 | IPv4/IPv6; default: IPv4 Specifies what of address will be requested from the operator.
Auto APN off | on; default: on 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.
APN / Custom APN string; default: none 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 public IP address) depending on the contract.
An APN Network Identifier cannot start with any of the following strings:
  • rac;
  • lac;
  • sgsn;
  • rnc;
it cannot end in:
  • .gprs;
and it cannot contain the asterisk symbol (*).
Authentication Type NONE | PAP | CHAP; default: NONE 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.
Disable DHCP on | off; default: on Disables dynamic allocation of client addresses when toggled off
Lease Time integer; default: 1 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
Units Hours | Minutes | Second; default: Hours Specifies the time measurement unit
MAC Address mac; default: none Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode.
Note: this field only becomes visible when using Bridge or Passthrough mode.
Mode: Bridge

[[File:Networking_rutos_manual_wan_configuration_general_mobile_bridge_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]]

Field Value Description
Mode NAT | Bridge | Passthrough; default: NAT Mobile connection operating mode.
  • NAT - the mobile connection uses NAT (network address translation).
  • Bridge - 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.
  • Passthrough - 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.
Subnet selection Auto | P2P; default: Auto Subnet selection method.
PDP Type IPv4 | IPv6 | IPv4/IPv6; default: IPv4 Specifies what of address will be requested from the operator.
Auto APN off | on; default: on 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.
APN / Custom APN string; default: none 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 public IP address) depending on the contract.
An APN Network Identifier cannot start with any of the following strings:
  • rac;
  • lac;
  • sgsn;
  • rnc;
it cannot end in:
  • .gprs;
and it cannot contain the asterisk symbol (*).
Authentication Type NONE | PAP | CHAP; default: NONE 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.
MAC Address mac; default: none Specifies the MAC address of the device that will receive the mobile interface's IP address in Bridge or Passthrough mode.
Note: this field only becomes visible when using Bridge or Passthrough mode.

IPv6 Settings

The IPv6 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.

IPv6 Settings: Static

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

Networking rutos manual wan configuration ipv6 settings static.png

Field Value Description
Delegate IPv6 prefixes off | on; default: on Enable downstream delegation of IPv6 prefixes available on this interface.
IPv6 assignment length Disabled | 64 | Custom; default: Disabled A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).
IPv6 address IPv6 addresses with or without mask prefix are accepted; default: none Assigns an IPv6 address for this interface. CIDR notation: address/prefix.
IPv6 gateway IPv6 addresses are accepted. E.g. ::0000:8a2e:0370:7334; default: none IPv6 default gateway.
IPv6 routed prefix IPv6 addresses with mask prefix are accepted E.g ::1/128; default: none Public prefix routed to this device for distribution to clients.
IPv6 suffix Allowed values: "eui64", "random", fixed value like "::1" or "::1:2"; default: none Optional. Allowed values: 'eui64', 'random', fixed value like '::1' or '::1:2'. When IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use the suffix (like '::1') to form the IPv6 address ('a:b:c:d::1') for the interface.

IPv6 Settings: DHCPv6

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

Networking rutos manual wan configuration ipv6 settings dhcpv6.png

Field Value Description
Delegate IPv6 prefixes off | on; default: on Enable downstream delegation of IPv6 prefixes available on this interface.
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.

IPv6 Settings: PPPoE

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

Networking rutos manual wan configuration ipv6 settings pppoe.png

Field Value Description
Delegate IPv6 prefixes off | on; default: on Enable downstream delegation of IPv6 prefixes available on this interface.
Obtain IPv6 address Automatic | Disabled | Manual; default: Automatic Defines behaviour for obtaining an IPv6 address.

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 wan configuration advanced settings static.png

Field Value Description
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 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).
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.
  • Note: Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
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 wan configuration advanced settings dhcp.png

Field Value Description
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.
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: none A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).
Use custom DNS servers ip4; default: none Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used.
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.
  • Note: Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.

Advanced Settings: DHCPv6

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

Networking rutos manual wan configuration advanced settings dhcpv6.png

Field Value Description
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.
Use default gateway off | on; default: on When checked, creates a default route for the interface.
Use custom DNS servers ip4; default: none Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used.
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.
  • Note: Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.

Advanced Settings: PPPoE

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

Networking rutos manual wan configuration advanced settings pppoe.png

Field Value Description
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.
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 custom DNS servers ip4; default: none Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used.
VLAN tag value integer [0..7]; default: none VLAN tag value.
VLAN priority integer [0..4095]; default: none VLAN priority.
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.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.


Physical Settings

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

Networking rutos manual wan configuration physical settings.png

Field Value Description
Bridge interfaces off | on; default: off Bridges physical interfaces specified in this configuration.
Interface network interface(s); default: wan physical interface 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.

Advanced Settings: DHCP

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

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

Field Value Description
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.
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: none A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).
Use custom DNS servers ip4; default: none Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used.
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.
  • Note: Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.

Advanced Settings: DHCPv6

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

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

Field Value Description
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.
Use default gateway off | on; default: on When checked, creates a default route for the interface.
Use custom DNS servers ip4; default: none Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used.
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.
  • Note: Interface(s): lan have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): lan have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.

Advanced Settings: PPPoE

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

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

Field Value Description
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.
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 custom DNS servers ip4; default: none Specifies custom DNS servers. If left empty, DNS servers advertised by peer are used.
VLAN tag value integer [0..7]; default: none VLAN tag value.
VLAN priority integer [0..4095]; default: none VLAN priority.
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.
IP4table integer [0..99999999]; default: none ID of the routing table in [[{{{name}}}_Routing#Routing_Tables|Routing tables]] page.


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 v2.png

Field Value Description
Bridge interfaces off | on; default: on 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.
Enable IGMP off | on; default: off Enabless IGMP snooping on this bridge.
Note: this field becomes visible when 'Bridge interfaces' is set to on and 'Protocol' is set to PPPoE.
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.


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

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_wan&oldid=111124"