|
|
(26 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
| {{Template:Networking_rutos_manual_fw_disclosure | | {{Template: Networking_rutos_manual_fw_disclosure |
| | fw_version = {{{series}}}_R_00.02.04.1 | | | fw_version = {{{series}}}_R_00.07.01 |
| | series = {{{series}}} | | | series = {{{series}}} |
| }} | | }} |
| | | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT9XX_R_00.06.08.3 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 RUT2XX_R_00.01.14.1 and earlier) user manual page.</i>|}} |
| ==Summary== | | ==Summary== |
|
| |
|
Line 9: |
Line 10: |
|
| |
|
| 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 18: |
Line 15: |
| 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. |
|
| |
|
| {{#ifeq: {{{series}}} | RUTX
| | [[File:Networking_rutos_manual_wan_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}_wired_{{{wired}}}.png|border|class=tlt-border]] |
| | [[File:Networking_rutos_manual_wan_modem_{{{modem}}}.png|border|class=tlt-border]]
| |
| | [[File:Networking_{{lc:{{{series}}}}}_manual_wan.png|border|class=tlt-border]]
| |
| }}
| |
|
| |
|
| From here you can turn the interfaces on or off, change their priority<span class="asterisk">*</span> or enter an [[#Interface_configuration|interface's configuration page]]. | | From here you can turn the interfaces on or off, change their priority<span class="asterisk">*</span> or enter an [[#Interface_configuration|interface's configuration page]]. |
Line 29: |
Line 23: |
| ==Interface configuration== | | ==Interface configuration== |
|
| |
|
| This section provides information on <b>WAN interface configuration</b>. There {{#ifeq:{{{eth}}}|{{{modem}}}|are two types of WAN interfaces|is one type of WAN interface}} on the device: | | This section provides information on <b>WAN interface configuration</b>. There {{#ifeq:{{{wired}}}|{{{mobile}}}|are two types of WAN interfaces|is one type of WAN interface}} on the device: |
|
| |
|
| <ul> | | <ul> |
| {{#ifeq: {{{eth}}} | 1 | | {{#ifeq: {{{wired}}} | 1 |
| |<li><b>Ethernet WAN</b></li> | | |<li><b>Ethernet WAN</b></li> |
| |}}{{#ifeq: {{{modem}}} | 1 | | |}}{{#ifeq: {{{mobile}}} | 1 |
| |<li><b>Mobile WAN</b></li> | | |<li><b>Mobile WAN</b></li> |
| |}} | | |}} |
| </ul>{{#ifeq:{{{eth}}}|{{{modem}}}|Each supports different types of protocols and setups, which are described in the sections below.|}} | | </ul>{{#ifeq:{{{wired}}}|{{{mobile}}}|Each supports different types of protocols and setups, which are described in the sections below.|}} |
| 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: |
|
| |
|
| {{#ifeq: {{{series}}} | RUTX | | {{#ifeq: {{{wired}}} | 1 | |
| | [[File:Networking_rutos_manual_wan_begin_to_edit_v1.png]]
| | [[File:Networking_rutos_manual_wan_begin_to_edit_eth_{{{wired}}}.png]] |
| | [[File:Networking_trb_manual_wan_begin_to_edit_v1.png]]
| |
| }}
| |
| {{#ifeq: {{{eth}}} | 1 |
| |
| ===Wired WAN===
| |
| ----
| |
| This section covers all parameters directly related to a <b>wired (Ethernet) WAN</b> interface.
| |
|
| |
|
| ====General Setup==== | | ===Static=== |
| ---- | | ---- |
| The <b>General Setup</b> section is used to configure the protocol and all the different parameters that go along with each protocol. This section is different for each protocol. | | The <b>static address</b> protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease. |
|
| |
|
| =====General Setup: Static address===== | | ====Static: General Settings==== |
| ---- | | ---- |
| The <b>static address</b> protocol uses a predefined manual configuration instead of obtaining parameters automatically via a DHCP lease.
| |
|
| |
| [[File:Networking_rutos_manual_wan_wan_configuration_general_setup_static_address.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_wan_wan_configuration_general_setup_static_address.png|border|class=tlt-border]] |
|
| |
|
Line 87: |
Line 73: |
| </table> | | </table> |
|
| |
|
| =====General Setup: DHCP client===== | | ====Static: DHCP Server==== |
| ---- | | ---- |
| The <b>DHCP client</b> protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease.
| | A <b>DHCP</b> (<b>Dynamic Host Configuration Protocol</b>) server is a service that can automatically configure the TCP/IP settings of any device that requests such a service. If you connect a device that has been configured to obtain an IP address automatically, the DHCP server will lease out an IP address from the available IP pool and the device will be able to communicate within the private network. |
|
| |
|
| [[File:Networking_rutos_manual_wan_wan_configuration_general_setup_dhcp_client_v1.png|border|class=tlt-border]] | | [[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]] |
|
| |
|
| <table class="nd-mantable">
| | This section is used to set up the main operating parameters of the DHCP server. |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Hostname to send when requesting DHCP</td>
| |
| <td>string; default: <b>none</b></td>
| |
| <td>A hostname for this interface used to identify this machine on the DHCP server.</td>
| |
| </tr>
| |
| </table>
| |
|
| |
|
| =====General Setup: DHCPv6 client=====
| | [[File:Networking_rutos_manual_wan_wan_configuration_static_dhcp_server.png|border|class=tlt-border]] |
| ----
| |
| The <b>DHCPv6 client</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_wan_configuration_general_setup_dhcpv6_client_v1.png|border|class=tlt-border]]
| |
| | |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Request IPv6-address</td>
| |
| <td>try <nowiki>|</nowiki> force <nowiki>|</nowiki> disabled; default: <b>try</b></td>
| |
| <td>Defines the behaviour for requesting an address.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Request IPv6-prefix of length</td>
| |
| <td>integer [0..64] <nowiki>|</nowiki> Automatic <nowiki>|</nowiki> disabled ; default: <b>Automatic</b></td>
| |
| <td>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.</td>
| |
| </tr>
| |
| </table>
| |
| | |
| =====General Setup: PPPoE=====
| |
| ----
| |
| The <b>PPPoE</b> protocol is used to set up a PPP (Point-to-Point Protocol) connection over the Ethernet port{{#ifeq:{{{series}}}|TRB1| (in this case: an Ethernet connection simulated over the USB port)|}}.
| |
| | |
| [[File:Networking_rutos_manual_wan_wan_configuration_general_setup_pppoe_v1.png|border|class=tlt-border]] | |
|
| |
|
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 143: |
Line 90: |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>PAP/CHAP username</td> | | <td>Enable DHCP</td> |
| <td>string; default: <b>none</b></td> | | <td>Enable <nowiki>|</nowiki> Disable <nowiki>|</nowiki> DHCP Relay<span class="asterisk">*</span>; default: <b>Enable</b></td> |
| <td>Username used in PAP/CHAP authentication.</td>
| | <td>Turns the DHCP server on or off or enables DHCP relay<span class="asterisk">*</span>.<br>If DHCP Relay<span class="asterisk">*</span> is selected, you will be prompted to enter an IP address of another DHCP server in your LAN. In this case, whenever a new machine connects to this device, it will redirect any DHCP requests to the specified DHCP Server.</td> |
| </tr>
| |
| <tr>
| |
| <td>PAP/CHAP password</td>
| |
| <td>string; default: <b>none</b></td> | |
| <td>Password used in PAP/CHAP authentication.</td>
| |
| </tr> | | </tr> |
| </table>
| |
|
| |
| ====Advanced Settings====
| |
| ----
| |
| The <b>Advanced Settings</b> section is used to set up some of the more specific and less frequently used interface parameters. This section is different for each protocol.
| |
|
| |
| =====Advanced Settings: Static address=====
| |
| ----
| |
| <b>Advanced Settings</b> information for <b>Static</b> protocol is provided in the table below.
| |
|
| |
| [[File:Networking_rutos_manual_wan_wan_configuration_advanced_settings_static_address.png|border|class=tlt-border]]
| |
|
| |
| <table class="nd-mantable">
| |
| <tr> | | <tr> |
| <th>Field</th> | | <td>Start</td> |
| <th>Value</th> | | <td>integer [1..255]; default: <b>100</b></td> |
| <th>Description</th> | | <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> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Override MAC address</td> | | <td>Limit</td> |
| <td>mac; default: <b>none</b></td> | | <td>integer [1..255]; default: <b>150</b></td> |
| <td>When set, uses a user-defined MAC address for the interface.</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> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Override MTU</td> | | <td>Lease time</td> |
| <td>integer [1..9200]; default: <b>none</b></td> | | <td>integer [1..999999]; default: <b>none</b></br>integer [2..999999]<span class="asterisk">*</span></br>integer [120..999999]<span class="asterisk">**</span></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>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> |
| <tr> | | <tr> |
| <td>Use gateway metric</td> | | <td>Units</td> |
| <td>integer; default: <b>0</b></td> | | <td>Hours <nowiki>|</nowiki> Minutes <nowiki>|</nowiki> Seconds; default: <b>Hours</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>Lease time units.</td> |
| </tr> | | </tr> |
| </table> | | </table> |
|
| |
|
| | <span class="asterisk">*</span> When an interface is set to act as a DHCP Relay, it redirects all received DHCP request messages to another specified DHCP server: |
|
| |
|
| =====Advanced Settings: DHCP client=====
| | [[File:Networking_rutx_manual_lan_static_dhcp_server_relay_scheme_v2.png]] |
| ----
| |
| <b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below.
| |
| | |
| [[File:Networking_rutos_manual_wan_wan_configuration_advanced_settings_dhcp_client.png|border|class=tlt-border]] | |
|
| |
|
| <table class="nd-mantable">
| | ===DHCP=== |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Use default gateway</td>
| |
| <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
| |
| <td>When enabled, add a default route for this interface.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Use DNS servers advertised by peer</td>
| |
| <td><span style="color: red;">off</span> <nowiki>|</nowiki> 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 <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>
| |
| <td>Use gateway metric</td>
| |
| <td>integer; default: <b>0</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>Override MAC address</td>
| |
| <td>mac; default: <b>none</b></td>
| |
| <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your device). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer.</td>
| |
| </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.</td>
| |
| </tr>
| |
| </table>
| |
| | |
| =====Advanced Settings: DHCPv6 client=====
| |
| ---- | | ---- |
| <b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below. | | The <b>DHCP client</b> protocol is used to set up an interface which obtains its configuration parameters automatically via a DHCP lease. |
|
| |
|
| [[File:Networking_rutos_manual_wan_wan_configuration_advanced_settings_dhcpv6_client.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_wan_wan_configuration_general_setup_dhcp_client.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> |
| <tr> | | <tr> |
| <td>Use default gateway</td>
| | <td>Hostname to send when requesting DHCP</td> |
| <td>off <nowiki>|</nowiki> on; default: <b>on</b></td>
| | <td>string; default: <b>none</b></td> |
| <td>When enabled, add a default route for this interface.</td>
| | <td>A hostname for this interface used to identify this machine on the DHCP server.</td> |
| </tr> | | </tr> |
| <tr>
| | </table>|}} |
| <td>Use DNS servers advertised by peer</td>
| |
| <td><span style="color: red;">off</span> <nowiki>|</nowiki> 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 <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>
| |
| <td>Override MAC address</td>
| |
| <td>mac; default: <b>none</b></td>
| |
| <td>When set, uses a user-defined MAC address for the interface.</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.</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_wan_wan_configuration_advanced_settings_pppoe.png|border|class=tlt-border]]
| |
| | |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Obtain IPv6 address</td>
| |
| <td>Automatic <nowiki>|</nowiki> Disabled <nowiki>|</nowiki> 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 enabled, add a default route for this interface.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Use gateway metric</td>
| |
| <td>integer; default: <b>0</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 DNS servers advertised by peer</td>
| |
| <td><span style="color: red;">off</span> <nowiki>|</nowiki> 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 <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>
| |
| <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>
| |
| </table> | |
| | |
| ====DHCP Server: IPv6 Settings====
| |
| ----
| |
| Refer to the table below for information on the <b>IPv6 Settings</b> section.
| |
| | |
| [[File:Networking_rutos_manual_wan_wan_configuration_dhcp_server_ipv6_settings.png|border|class=tlt-border]]
| |
|
| |
|
| <table class="nd-mantable">
| | {{#ifeq: {{{mobile}}} | 1 | |
| <tr>
| | ===Mobile=== |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Router Advertisement-Service</td>
| |
| <td>Disabled <nowiki>|</nowiki> Relay mode <nowiki>|</nowiki> Server mode <nowiki>|</nowiki> Hybrid mode; default: <b>Disabled</b></td>
| |
| <td>Specifies whether router advertisements should be enabled (server mode), relayed or disabled. </td>
| |
| </tr>
| |
| <tr>
| |
| <td>DHCPv6-Service</td>
| |
| <td>Disabled <nowiki>|</nowiki> Relay mode <nowiki>|</nowiki> Server mode <nowiki>|</nowiki> Hybrid mode; default: <b>Disabled</b></td>
| |
| <td>Specifies whether DHCPv6 server should be enabled (server), relayed (relay) or disabled (disabled).</td>
| |
| </tr>
| |
| <tr>
| |
| <td>NDP Proxy</td>
| |
| <td>Disabled <nowiki>|</nowiki> Relay mode <nowiki>|</nowiki> Hybrid mode; default: <b>Disabled</b></td>
| |
| <td>Specifies whether NDP should be relayed or disabled.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Announced DNS server</td>
| |
| <td>ip; default: <b>none</b></td>
| |
| <td>Supplements DHCP-assigned DNS server entries with ones specified in this field.</td>
| |
| </tr>
| |
| <tr>
| |
| <td>Announced DNS domains</td>
| |
| <td>ip; default: <b>none</b></td>
| |
| <td>DNS domain handed out to DHCP clients.</td>
| |
| </tr>
| |
| </table>|}}
| |
| {{#ifeq: {{{modem}}} | 1 | | |
| ===Mobile WAN=== | |
| ---- | | ---- |
| This section covers all parameters directly related to a <b>mobile WAN</b> interface.
| | The <b>Mobile</b> protocol is used to set up an interface which can establish a mobile WAN connection. |
|
| |
|
| ====General Setup: Mobile==== | | ====Mobile: General Settings==== |
| ---- | | ---- |
| The <b>General Setup</b> section is used to configure the main parameters of a mobile WAN connection.
| | [[File:Networking_rutos_manual_wan_mobile_configuration_general_setup_dualsim_{{{dualsim}}}_dualmodem_{{{dualmodem}}}.png|border|class=tlt-border]] |
| | |
| [[File:Networking_{{lc:{{{series}}}}}_manual_wan_mobile_configuration_general_setup.png|border|class=tlt-border]] | |
|
| |
|
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 380: |
Line 164: |
| </ul> | | </ul> |
| </td> | | </td> |
| </tr> | | </tr>{{#ifeq: {{{dualsim}}} | 1 | |
| {{#ifeq: {{{series}}} | TRB1 | | <tr> |
| |
| |
| | <tr>
| |
| <td>PDP Type</td> | | <td>PDP Type</td> |
| <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4</b></td> | | <td>IPv4 <nowiki>|</nowiki> IPv6 <nowiki>|</nowiki> IPv4/IPv6; default: <b>IPv4</b></td> |
Line 391: |
Line 173: |
| <td>SIM</td> | | <td>SIM</td> |
| <td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td> | | <td>SIM1 <nowiki>|</nowiki> SIM2; default: <b>SIM1</b></td> |
| <td>Select which sim will be used for this interface.</td> | | <td>Selects which SIM slot will be used for this interface.</td> |
| </tr>}} | | </tr>|}}{{#ifeq: {{{dualmodem}}} | 1 | |
| | <tr> |
| | <td>Modem</td> |
| | <td>Primary modem <nowiki>|</nowiki> Secondary modem; default: <b>Primary modem</b></td> |
| | <td>Selects which modem will be used for this interface.</td> |
| | </tr>|}} |
| <tr> | | <tr> |
| <td>Auto APN</td> | | <td>Auto APN</td> |
Line 421: |
Line 208: |
| </table> | | </table> |
|
| |
|
| ====Advanced Settings: Mobile==== | | ====Mobile: Mobile Data Limit==== |
| ----
| |
| <b>Advanced Settings</b> information for <i>mobile</i> WAN is provided in the table below.
| |
| | |
| {{#ifeq: {{{series}}} | TRB1
| |
| | [[File:Networking_trb1_manual_wan_mobile_configuration_advanced_settings.png|border|class=tlt-border]]
| |
| | [[File:Networking_rutos_manual_wan_mobile_configuration_advanced_settings.png|border|class=tlt-border]]
| |
| }}
| |
| | |
| <table class="nd-mantable">
| |
| <tr>
| |
| <th>Field</th>
| |
| <th>Value</th>
| |
| <th>Description</th>
| |
| </tr>
| |
| <tr>
| |
| <td>Use DNS servers advertised by peer</td>
| |
| <td><span style="color: red;">off</span> <nowiki>|</nowiki> on; default: <b>on</b></td>
| |
| <td>Specifies whether to use DNS servers obtained automatically or specified manually.</td>
| |
| </tr>{{#ifeq: {{{series}}} | TRB1 ||
| |
| <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>
| |
| <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>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.</td>
| |
| </tr>}}
| |
| </table>
| |
| | |
| ====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. |
Line 464: |
Line 214: |
| <u>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to <i>Mobile</i></b></i>.</u> | | <u>In order to view the Mobile Data Limit section, the interface <b>protocol must be set to <i>Mobile</i></b></i>.</u> |
|
| |
|
| [[File:Networking_rutos_manual_wan_mobile_configuration_mobile_data_limit_v1.png|border|class=tlt-border]] | | [[File:Networking_rutos_manual_wan_mobile_configuration_mobile_data_limit.png|border|class=tlt-border]] |
|
| |
|
| <table class="nd-mantable"> | | <table class="nd-mantable"> |
Line 488: |
Line 238: |
| <tr> | | <tr> |
| <td>Start day <nowiki>|</nowiki> Start hour</td> | | <td>Start day <nowiki>|</nowiki> Start hour</td> |
| <td>day [1..31] <nowiki>|</nowiki> day [Monday..Sunday] {{!}} hour [1..24]; default: <b>hour 0</b></td> | | <td>day [1..31] <nowiki>|</nowiki> day [Monday..Sunday] <nowiki>|</nowiki> hour [1..24]; default: <b>hour 0</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 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> |
| </tr> | | </tr> |
Line 505: |
Line 255: |
| <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>Clear Collected Data</td> |
| | <td>- (interactive button)</td> |
| | <td>Clears the data limit counter.</td> |
| </tr> | | </tr> |
| </table>|}} | | </table>|}} |
| | |
| [[Category:{{{name}}} Network section]] | | [[Category:{{{name}}} Network section]] |