31,703
edits
Changes
Template:Networking rut9xx manual wan legacy (view source)
Revision as of 13:30, 3 June 2021
, 13:30, 3 June 2021Created page with "{{Template: Networking_rutxxx_manual_fw_disclosure | fw_version = {{{series}}}_R_00.06.08.2 | series = {{{series}}} }} <i><b>Note</b>: this user manual page is for {{{nam..."
{{Template: Networking_rutxxx_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.06.08.2
| series = {{{series}}}
}}
<i><b>Note</b>: this user manual page is for {{{name}}}'s old WebUI style available in earlier FW versions. <b>[[{{{name}}} Services|Click here]]</b> for information based on the latest FW version.</i>
==Summary==
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 area network. This chapter is an overview of {{{name}}} routers' WAN section.
==Operation Modes==
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.
[[Image:{{{wan_operation_modes}}}]]
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====
----
[[File:{{{wan_static_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: <b>none</b></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: <b>none</b></td>
<td>The address where the router will send all the outgoing traffic</td>
</tr>
<tr>
<td>IPv4 broadcast</td>
<td>ip; default: <b>none</b></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: <b>none</b></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.
[[File:{{{wan_static_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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====
----
[[File:{{{wan_dhcp_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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.
[[File:{{{wan_dhcp_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: '''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: <b>none</b></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: <b>none</b></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: <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: '''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>
</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.
[[File:{{{wan_pppoe_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: <b>none</b></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: <b>none</b></td>
<td>The password that you use to connect to your carrier’s network </td>
</tr>
<tr>
<td>Access concentrator</td>
<td>string; default: <b>none</b></td>
<td>The name of the access concentrator. Leave empty to auto detect</td>
</tr>
<tr>
<td>Service name</td>
<td>string; default: <b>none</b></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.
[[File:{{{wan_pppoe_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: <b>none</b></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===
----
[[File:{{{wan_lan_ip_aliases}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IP address</td>
<td>ip; default: <b>none</b></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: <b>none</b></td>
<td>A gateway is a network node that connects two networks using different protocols together</td>
</tr>
<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.
[[File:{{{wan_lan_ip_aliases_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IP Broadcast</td>
<td>ip; default: <b>none</b></td>
<td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
</tr>
<tr>
<td>DNS</td>
<td>ip; default: <b>none</b></td>
<td>A separate DNS server to be used by the IP Alias address</td>
</tr>
</table>
==Failover 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.
[[File:{{{wan_failover_configuration}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Health monitor interval</td>
<td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; default: <b>5 sec.</b></td>
<td>The interval at which health checks are performed.</td>
</tr>
<tr>
<td>Health monitor ICMP host(s)</td>
<td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; default: <b>8.8.8.8</b></td>
<td>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).</td>
</tr>
<tr>
<td>Health monitor ICMP timeout</td>
<td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; default: <b>1 sec.</b></td>
<td>The frequency at which ICMP requests will be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes).</td>
</tr>
<tr>
<td>Attempts before failover</td>
<td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td>
<td>The number of failed ping attempts before the connection is to be declared as "down". </td>
</tr>
<tr>
<td>Attempts before recovery</td>
<td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td>
<td>The number of successful ping attempts before the connection is to be declared as "up".</td>
</tr>
<tr>
<td>Execute command</td>
<td>yes {{!}} no; default: <b>no</b></td>
<td>Executes a user specified command when the WAN fails over to this interface.</td>
</tr>
<tr>
<td>Command</td>
<td>string; default: <b>none</b></td>
<td>A command that will executed when the WAN fails over to this interface.</td>
</tr>
</table>
<b>Additional notes</b>:
<ul>
<li>Failover configuration field's default values may differ based on WAN type.</li>
<li>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.</li>
</ul>
==UDP Broadcast Relay==
The <b>UDP Broadcast Relay</b> will listen for broadcast traffic on the specified port and relay that traffic to the specified interface(s).
[[File:Networking_rut_manual_wan_udp_broadcast_relay.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>on | off; default: <b>off</b></td>
<td>Turns UDP Broadcast Relay on or off.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>UDP port to listen for broadcast traffic.</td>
</tr>
<tr>
<td>Interfaces</td>
<td>network interface(s); default: <b>none</b></td>
<td>The interface(s) to which the traffic will be redirected to.</td>
</tr>
</table>
[[Category:{{{name}}} Network section (legacy)]]
| fw_version = {{{series}}}_R_00.06.08.2
| series = {{{series}}}
}}
<i><b>Note</b>: this user manual page is for {{{name}}}'s old WebUI style available in earlier FW versions. <b>[[{{{name}}} Services|Click here]]</b> for information based on the latest FW version.</i>
==Summary==
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 area network. This chapter is an overview of {{{name}}} routers' WAN section.
==Operation Modes==
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.
[[Image:{{{wan_operation_modes}}}]]
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====
----
[[File:{{{wan_static_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: <b>none</b></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: <b>none</b></td>
<td>The address where the router will send all the outgoing traffic</td>
</tr>
<tr>
<td>IPv4 broadcast</td>
<td>ip; default: <b>none</b></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: <b>none</b></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.
[[File:{{{wan_static_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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====
----
[[File:{{{wan_dhcp_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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.
[[File:{{{wan_dhcp_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: '''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: <b>none</b></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: <b>none</b></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: <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: '''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>
</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.
[[File:{{{wan_pppoe_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: <b>none</b></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: <b>none</b></td>
<td>The password that you use to connect to your carrier’s network </td>
</tr>
<tr>
<td>Access concentrator</td>
<td>string; default: <b>none</b></td>
<td>The name of the access concentrator. Leave empty to auto detect</td>
</tr>
<tr>
<td>Service name</td>
<td>string; default: <b>none</b></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.
[[File:{{{wan_pppoe_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</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: <b>none</b></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===
----
[[File:{{{wan_lan_ip_aliases}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IP address</td>
<td>ip; default: <b>none</b></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: <b>none</b></td>
<td>A gateway is a network node that connects two networks using different protocols together</td>
</tr>
<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.
[[File:{{{wan_lan_ip_aliases_advanced}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>IP Broadcast</td>
<td>ip; default: <b>none</b></td>
<td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
</tr>
<tr>
<td>DNS</td>
<td>ip; default: <b>none</b></td>
<td>A separate DNS server to be used by the IP Alias address</td>
</tr>
</table>
==Failover 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.
[[File:{{{wan_failover_configuration}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Health monitor interval</td>
<td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; default: <b>5 sec.</b></td>
<td>The interval at which health checks are performed.</td>
</tr>
<tr>
<td>Health monitor ICMP host(s)</td>
<td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; default: <b>8.8.8.8</b></td>
<td>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).</td>
</tr>
<tr>
<td>Health monitor ICMP timeout</td>
<td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; default: <b>1 sec.</b></td>
<td>The frequency at which ICMP requests will be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes).</td>
</tr>
<tr>
<td>Attempts before failover</td>
<td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td>
<td>The number of failed ping attempts before the connection is to be declared as "down". </td>
</tr>
<tr>
<td>Attempts before recovery</td>
<td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td>
<td>The number of successful ping attempts before the connection is to be declared as "up".</td>
</tr>
<tr>
<td>Execute command</td>
<td>yes {{!}} no; default: <b>no</b></td>
<td>Executes a user specified command when the WAN fails over to this interface.</td>
</tr>
<tr>
<td>Command</td>
<td>string; default: <b>none</b></td>
<td>A command that will executed when the WAN fails over to this interface.</td>
</tr>
</table>
<b>Additional notes</b>:
<ul>
<li>Failover configuration field's default values may differ based on WAN type.</li>
<li>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.</li>
</ul>
==UDP Broadcast Relay==
The <b>UDP Broadcast Relay</b> will listen for broadcast traffic on the specified port and relay that traffic to the specified interface(s).
[[File:Networking_rut_manual_wan_udp_broadcast_relay.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>on | off; default: <b>off</b></td>
<td>Turns UDP Broadcast Relay on or off.</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; default: <b>none</b></td>
<td>UDP port to listen for broadcast traffic.</td>
</tr>
<tr>
<td>Interfaces</td>
<td>network interface(s); default: <b>none</b></td>
<td>The interface(s) to which the traffic will be redirected to.</td>
</tr>
</table>
[[Category:{{{name}}} Network section (legacy)]]
