RUT240 WAN: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
 
(15 intermediate revisions by 7 users not shown)
Line 1: Line 1:
==Summary==
{{Template: Networking_rutos_manual_wan_rut2_rut9
 
<!------------------------DEVICE----------------------->
A wide area network (WAN) is a telecommunications network or computer network that extends over a large geographical distance. For example, the Internet is a wide are network. This chapter is an overview of RUTxxx routers' WAN section.
| name     = RUT240
 
| series    = RUT2
==Operation Modes==
<!----------------------SEPARATORS--------------------->
 
| mobile    = 1  <!-- 1 - has mobile WAN; 0 - doesn't have mobile WAN -->
The Operation Modes window lets you determine how the router will be connecting to the internet. You can chose between three types of WAN – Mobile, Wired and Wi-Fi. You can also setup backup WAN options in case your main connection goes down.
| dualsim  = 0  <!-- 1 - has dual SIM; 0 - doesn't have dual SIM -->
 
| dualmodem = 0  <!-- 1 - has dual modem; 0 - doesn't have dual modem -->
[[File:Network wan operation v2.png]]
| wired    = 1  <!-- 1 - has wired WAN; 0 - doesn't have wired WAN -->
 
| no_of_if  = 2  <!-- one - wired/mobile; two - wired & mobile -->
You can choose one main WAN and one or two (or none) backup WAN options. To choose your main WAN just check the desired option (wired, mobile or Wi-Fi) in the '''Main WAN''' column (first from the left), to choose a backup WAN(s), check the desired option(s) in the Backup WAN column (second from the left). Above is an example of a configuration that uses wired as Main WAN and mobile as Backup WAN.
}}
The Operation Modes tab also displays each interfaces name, WAN IP address and Protocol in use. To configure a WAN interface more in depth, click the '''Edit''' button located to the right of the desired interface. Each interface configures separately, to avoid redundancy this chapter will only overview the configuration of the wired WAN interface, since mobile contains less information and Wi-Fi is basically the same.
 
==Common Configuration==
 
The Common Configuration section is used to configure different protocols for WAN interfaces.
 
===Static===
----
The Static protocol is used when the source of your internet doesn’t have a DHCP server enabled. Therefore, in order to connect to the internet, you have to make configurations in accordance to that source.
 
====General====
----
[[Image:Network wan static general.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Protocol</td>
      <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td>
      <td>The protocol used by the WAN interface</td>
    </tr>
    <tr>
      <td>IPv4 address</td>
      <td>ip; Default: " "</td>
      <td>Your router’s address on the WAN network</td>
    </tr>
    <tr>
    <td>IPv4 netmask</td>
        <td>ip; Default: '''255.255.255.0'''</td>
        <td>Netmask defines how "large" a network is</td>
    </tr>
    <tr>
    <td>IPv4 gateway</td>
        <td>ip; Default: " "</td>
        <td>The address where the router will send all the outgoing traffic</td>
    </tr>
    <tr>
    <td>IPv4 broadcast</td>
        <td>ip; Default: " "</td>
        <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
    </tr>
    <tr>
    <td>Use custom DNS servers</td>
        <td>ip; Default: " "</td>
        <td>When the router needs to resolve a hostname (“www.google.com”, “www.cnn.com”, etc.) to an IP address, it will forward all the DNS requests to the gateway. By entering custom DNS servers the router will take care of the host name resolution. You can enter multiple DNS servers to provide redundancy in case one of the servers fails</td>
    </tr>
</table>
 
====Advanced====
----
The Advanced Settings tab will change in accordance to which network protocol is selected. For the Static protocol you can turn NAT on or off, override the router’s MAC address, MTU and define the gateway's metric.
 
[[Image:Network wan static advanced.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Disable NAT</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
    </tr>
    <tr>
      <td>Override MAC address</td>
      <td>mac; Default: '''router's mac'''</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 router). 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 [0..1500]; Default: '''1500'''</td>
        <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td>
    </tr>
    <tr>
    <td>Use gateway metric</td>
        <td>integer; Default: '''0'''</td>
        <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
    </tr>
</table>
 
===DHCP===
----
The DHCP protocol should be used when the source of your internet has a DHCP server enabled. If that is the case, when you select the DHCP protocol you can use it as is, because most networks will not require any additional advanced configuration.
 
====General====
----
[[Image:Network wan dhcp general.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Protocol</td>
      <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td>
      <td>The protocol used by the WAN interface</td>
    </tr>
    <tr>
      <td>Hostname to send when requesting DHCP</td>
      <td>ip {{!}} hostname; Default: '''router's hostname'''</td>
      <td>Host name to which the DHCP request will be sent to</td>
    </tr>
</table>
 
====Advanced====
----
For the DHCP protocol you can turn NAT on or off, specify custom DNS servers, define the gateway metric, override the router’s MAC address, set MTU and more.
 
[[Image:Network wan dhcp advanced.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Disable NAT</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
    </tr>
    <tr>
      <td>Use broadcast flag</td>
      <td>yes {{!}} no; Default: '''no''' </td>
      <td>Required for certain ISPs (Internet Service Providers), e.g. Charter with DOCSIS 3</td>
    </tr>
    <tr>
      <td>Use default gateway</td>
      <td>yes {{!}} no; Default: '''yes'''</td>
      <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td>
    </tr>
    <tr>
    <td>Use DNS servers advertised by peer</td>
        <td>yes {{!}} no; Default: '''no'''</td>
        <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td>
    </tr>
    <tr>
    <td>Use custom DNS servers</td>
        <td>ip; Default: " "</td>
        <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td>
    </tr>
    <tr>
    <td>Use gateway metric</td>
        <td>ip; Default: " "</td>
        <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority </td>
    </tr>
    <tr>
      <td>Client ID to send when requesting DHCP</td>
      <td>string; Default: " "</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: " "</td>
      <td>Vendor class which will be sent when requesting a DHCP lease</td>
    </tr>
    <tr>
    <td>Override MAC address</td>
        <td>mac; Default: '''router's mac'''</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 router). 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>nteger [0..1500]; Default: '''1500'''</td>
        <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td>
    </tr>
</table>
 
===PPPoE===
----
The PPPoE protocol is mainly used if you have a DSL internet provider.
 
====General====
----
The General configuration tab for the PPPoE protocol is mainly used to specify your PAP/CHAP login information, but you can also configure some additional, more specific settings.
 
[[Image:Network wan pppoe general2.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Protocol</td>
      <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td>
      <td>The protocol used by the WAN interface</td>
    </tr>
    <tr>
      <td>PAP/CHAP username</td>
      <td>string; Default: " "</td>
      <td>The username that you use to connect to your carrier’s network </td>
    </tr>
    <tr>
    <td>PAP/CHAP password</td>
        <td>string; Default: " "</td>
        <td>The password that you use to connect to your carrier’s network </td>
    </tr>
    <tr>
    <td>Access concentrator</td>
        <td>string; Default: " "</td>
        <td>The name of the access concentrator. Leave empty to auto detect</td>
    </tr>
    <tr>
    <td>Service name</td>
        <td>string; Default: " "</td>
        <td>The name of the service. Leave empty to auto detect</td>
    </tr>
</table>
 
====Advanced====
----
For the PPPoE protocol you can turn NAT on or off, specify custom DNS servers, define the gateway metric, configure LCP echo settings and more.
 
[[Image:Network wan pppoe advanced.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Disable NAT</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
    </tr>
    <tr>
      <td>Use default gateway</td>
      <td>yes {{!}} no; Default: '''yes'''</td>
      <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td>
    </tr>
    <tr>
    <td>Use gateway metric</td>
        <td>integer; Default: '''0'''</td>
        <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
    </tr>
    <tr>
    <td>Use DNS servers advertised by peer</td>
        <td>yes {{!}} no; Default: '''yes'''</td>
        <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td>
    </tr>
    <tr>
      <td>Use custom DNS servers</td>
      <td>ip; Default: " "</td>
      <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td>
    </tr>
    <tr>
      <td>LCP echo failure threshold</td>
      <td>integer; Default: '''0'''</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: '''5'''</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>Inactivity timeout</td>
        <td>integer; Default: '''0'''</td>
        <td>Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection</td>
    </tr>
</table>
 
==IP Aliases==
 
IP Aliases are a way of defining or reaching a subnet that works in the same space as the regular network. This is useful if you need to reach the router that is located in the same network but in a different subnet. If you have a static IP configuration on your computer and don’t want to change it every time you need to reach a router in a different subnet, you can configure an IP alias in order to do so.
 
===General setup===
----
[[Image:Network lan ipaliases.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>IP address</td>
      <td>ip; Default: " "</td>
      <td>An alternate IP address used to reach the router by a device(s) that resides in the router's LAN but has a different subnet</td>
    </tr>
    <tr>
      <td>Netmask</td>
      <td>ip; Default: '''255.255.255.0'''</td>
      <td>Netmask defines how "large" a network is</td>
    </tr>
    <tr>
    <td>Gateway</td>
        <td>ip; Default: " "</td>
        <td>A gateway is a network node that connects two networks using different protocols together</td>
    </tr>
</table>
 
As you can see, the configuration is very similar to the static protocol; in the example above an IP address with a 99th subnet is defined. In this case, if some device has an IP in the 99th subnet (e.g., 192.168.99.xxx) and the subnet’s gateway metric is “higher” and the device is trying to reach the internet it will reroute it’s traffic not to the gateway that is defined in common configurations but through the one that is specified in IP aliases.
 
===Advanced Settings===
----
You may also define a broadcast address and a custom DNS server for your IP Aliases in the Advanced Settings tab.
 
[[Image:Network lan ipaliases advanced.PNG]]
 
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IP Broadcast
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | DNS
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | A separate DNS server to be used by the IP Alias address
|-
|}
 
==Backup Configuration==
 
Backup WAN is a function that allows you to back up your primary connection in case it goes down. There can be up to two backup connections selected at one time. In that case, when the primary connection fails, the router tries to use the backup with the higher priority and if this one is unavailable or fails too, then the router tries the backup with the lower priority.
 
[[Image:Network wan backup configuration.PNG]]
 
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Health monitor interval
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; Default: '''10 sec.'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The interval at which health checks are performed
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Health monitor ICMP host(s)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; Default: '''8.8.4.4'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Health monitor ICMP timeout
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; Default: '''3 sec.'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes)
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Attempts before failover
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The number of failed ping attempts after which the connection is to be declared as “'''down'''”
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Attempts before recovery
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The number of successful ping attempts after which the connection is to be declared as “'''up'''”
|-
|}
 
The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down.

Latest revision as of 08:49, 9 April 2024

Main Page > EOL Products > RUT240 > RUT240 Manual > RUT240 WebUI > RUT240 Network section > RUT240 WAN

The information in this page is updated in accordance with firmware version RUT2_R_00.07.06.16.


Note: click here for the old style WebUI (FW version RUT2XX_R_00.01.14.7 and earlier) user manual page.

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 RUT240 devices.

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

WAN

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

From here you can turn the interfaces, enable/disable interface's failover, 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.

If you hover mouse over the question mark global IPv6 addresses and IPv6 prefix delegation will be displayed.

Interface configuration

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

  • Ethernet WAN
  • Mobile WAN

Different types of interfaces can be configured under different protocols:

Static DHCP DHCPv6 PPPoE Mobile
Ethernet WAN
Mobile WAN

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

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.

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

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.

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.

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

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 RUT240 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 RUT240 instead of LAN IP. Using Passthrough mode will disable most of the device’s capabilities.
PDP Type IPv4 | IPv6 | IPv4/IPv6; default: IPv4/IPv6 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

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 RUT240 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 RUT240 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

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 RUT240 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 RUT240 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.
Multi-APN

RUT240 supports Multiple PDN feature in order to establish connections to multiple mobile networks using a single SIM card. You can find a configuration example here.

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.

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.

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.

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.

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): have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP4 table integer [0..99999999]; default: none ID of the routing table in Routing tables page.

Advanced Settings: DHCP

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

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): have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP4 table integer [0..99999999]; default: none ID of the routing table in Routing tables page.

Advanced Settings: DHCPv6

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

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: 2 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.
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.
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): have mtu lower than 1280 it will make all interfaces on same physical interface no longer support IPv4.
  • Note: Interface(s): have mtu lower than 576 it will make all interfaces on same physical interface no longer support DHCP.
IP6 table integer [0..2^46]; default: none ID of the routing table in Routing tables page.

Advanced Settings: PPPoE

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

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.
IP4 table integer [0..99999999]; default: none ID of the routing table in Routing tables page.

Advanced Settings: Mobile

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

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 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.
Override MTU integer [98..65535]; default: none 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.
IP4 table integer [0..99999999]; default: none ID of the routing table in Routing tables page.

Physical Settings

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

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 → Zones section.

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

Mobile Data Limit

The Mobile Data Limit 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.

In order to view the Mobile Data Limit section, the interface protocol must be set to Mobile.

Field Value Description
Enable data connection limit off | on; default: off Turns mobile data limitations on or off.
Data limit* (MB) integer; default: 1000 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.
Period Month | Week | Day; default: Day Data limit period after which the data counter is reset on the specified Start day.
Start day | Start hour day [1..31] | day [Monday..Sunday] | hour [1..24]; default: hour 0 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.
Enable SMS warning off | on; default: off 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.
Data limit* (MB) integer; default: none The received data limit before sending an SMS warning. After reaching using the the amount of data specified in this field, the router will send an SMS warning message to the specified phone number.
Phone number phone number; default: none Recipient's phone numbers.
Data limit clear due none Display the date of the next automatic data limit clear.

*Your carrier's data usage accounting may differ. Teltonika is not liable should any accounting discrepancies occur.

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=RUT240_WAN&oldid=122861"