View source for RUT240 LAN (legacy WebUI)

==Summary==

{{Template: webui_network_lan_summary}}

{{Template: Networking_device_manual_fw_disclosure
| series = RUT2XX
| name   = RUT240
| fw_version ={{Template: Networking_device_manual_latest_fw
 | series = RUT2XX
 | name   = RUT240
 }}
}}
==Configuration==

===General Setup===
----
The <b>General Setup</b> section provides you with the possibility to set the router's Private IP address, IP netmask and IP broadcast.

[[File:Networking_rut_manual_lan_general_setup.png|border|class=tlt-border]]

<table class="nd-mantable">
    <tr>
        <th>Field</th>
       	<th>Value</th>
       	<th>Description</th>
    </tr>
    <tr>
      	<td>IP address</td>
       	<td>ip; default: <b>192.168.1.1</b></td>
       	<td>IP address of this LAN interface.</td>
    </tr>
    <tr>
      	<td>IP netmask</td>
       	<td>ip; default: <b>255.255.255.0</b></td>
       	<td>A netmask is used to define how “large" the LAN network is.</td>
    </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>IPv6 Address</td>
        <td>ip6; default: <b>none</b></td>
        <td>Assigns an Ipv6 address for this interface. CIDR notation: address/prefix.</td>
    </tr>
    <tr>
    	<td>IPv6 Prefix Length</td>
        <td>hex; default: <b>60</b></td>
        <td>Delegates a prefix length for this interface.</td>
    </tr>
    <tr>
    	<td>IPv6 Prefix</td>
        <td>hex; default: <b>none</b></td>
        <td>Custom IPv6 prefix for this network interface.</td>
    </tr>
    <tr>
    	<td>ULA Prefix</td>
        <td>ip; default: <b>none</b></td>
        <td>Prefix used for the Unique Local Address.</td>
    </tr>
</table>

===Advanced Settings===
----
LAN Configurations Advanced Settings tab contains some less frequently used, more complicated configurations, such as custom MTUs and network interface metric values. 

[[File:Networking_rut_manual_lan_advanced_settings.png|border|class=tlt-border]]

<table class="nd-mantable">
    <tr>
        <th>Field</th>
       	<th>Value</th>
       	<th>Description</th>
    </tr>
    <tr>
      	<td>Override MTU</td>
       	<td>integer [0..1500]; default: <b>none</b></td>
       	<td>MTU (Maximum Transmission Unit) specifies the largest possible size of a data packet.</td>
    </tr>
    <tr>
    	<td>Use gateway metric</td>
        <td>integer; default: <b>none</b></td>
        <td>The LAN configuration generates an entry in the routing table. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
    </tr>
    <tr>
    	<td>Use WAN port as LAN</td>
        <td>yes | no; default: <b>no</b></td>
        <td>If this is enabled, the router's WAN port will act as if it were a LAN port. <u>This works only when WAN is not set to wired!</u></td>
    </tr>
</table>

==DHCP Server==

{{Template: webui_network_lan_dhcp_summary}}

===General Setup===
----
{{Template: webui_network_lan_dhcp_general_setup}}

[[File:Networking_rut_manual_lan_dhcp_server_general_setup.png|border|class=tlt-border]]

<table class="nd-mantable">
    <tr>
        <th>Field</th>
       	<th>Value</th>
       	<th>Description</th>
    </tr>
    <tr>
      	<td>DHCP</td>
       	<td>Enable | Disable | DHCP Relay; default: <b>Enable</b></td>
       	<td>Enables or disables DHCP Server. If DHCP Relay is selected, you will be prompted to enter an IP address of another DHCP server in your LAN. In this case, Whenever a new device connects to the router, the router will redirect any DHCP requests to the specified DHCP Server.</td>
    </tr>
    <tr>
      	<td>Start</td>
       	<td>integer [1..253]; default: <b>100</b></td>
       	<td>The starting IP address value. e.g., if your router’s LAN IP is 192.168.2.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.2.0..192.168.2.254] (192.168.2.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.2.100.</td>
    </tr>
    <tr>
    	<td>Limit</td>
        <td>integer [1..4294967296]; default: <b>150</b></td>
        <td>How many addresses the DHCP server can lease out. Continuing from the above example: if the start address is 192.168.2.100 and the server can lease out 150 (default limit value), available addresses will be from 192.168.2.100 to 192.168.2.249 (100 + 150 – 1 = 249; this is because the first address is inclusive).</td>
    </tr>
    <tr>
    	<td>Lease time</td>
        <td>time in 'h' (hours) or 'm' (minutes); default: <b>12 Hours</b></td>
        <td>he duration of an IP lease. Leased out addresses 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 DHCP lease. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes, e.g., if the lease time is 12 hours, then every 6 hours the device will send a request to the DHCP server asking to renew its lease<br>
Lease time can be set in hours (h) or minutes (m). The minimal amount of time that can be specified is 2 minutes (2m).</td>
    </tr>
</table>

===Advanced Settings===
----
{{Template: webui_network_lan_dhcp_andvanced_settings}}

[[File:Networking_rut_manual_lan_dhcp_server_advanced_settings.png|border|class=tlt-border]]

<table class="nd-mantable">
    <tr>
        <th>Field</th>
       	<th>Value</th>
       	<th>Description</th>
    </tr>
    <tr>
      	<td>Dynamic DHCP</td>
       	<td>yes | no; default: <b>yes</b></td>
       	<td>Enables Dynamic allocation of client addresses. If this is disabled, only clients that have static IP leases will be served.</td>
    </tr>
    <tr>
      	<td>Enable DNS rebind protection</td>
       	<td>yes | no; default: <b>yes</b></td>
       	<td>Enables DNS rebind attack protection by discarding upstream RFC1918 responses (leave default unless necessary otherwise)b</td>
    </tr>
    <tr>
    	<td>Force</td>
        <td>yes | no; default: <b>no</b></td>
        <td>The DHCP force function ensures that the router will always start it’s DHCP server, even if there is another DHCP server already running in the router’s network. By default the router’s DHCP server will not start when it is connected to a network segment that already has a working DHCP serverb</td>
    </tr>
    <tr>
    	<td>IP netmask</td>
        <td>ip; default: <b>255.255.255.0</b></td>
        <td>Overrides your LAN netmask, thus making the DHCP server think that it’s serving a larger or smaller network than it actually isb</td>
    </tr>
    <tr>
    	<td>DHCP Options</td>
        <td>DHCP options; default: <b>none</b></td>
        <td>Additional options to be added to the DHCP server. For example with '26,1470' or 'option:mtu, 1470' you can assign an MTU value per DHCP. You can find more information on DHCP Options [https://technet.microsoft.com/en-us/library/cc958941.aspx here] <br> You can add more options by clicking the plus symbol ([[Image:Services sms gateway auto reply plus symbol.PNG]]) located next to the field.</td>
    </tr>
    <tr>
    	<td>Force DHCP options</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Forces DHCP option to be sent even if its not requested.</td>
    </tr>
</table>

==Static Leases==

Static IP leases are used to reserve specific IP addresses for specific devices by binding them to their MAC address. This is useful when you have a stationary device connected to your network that you need to reach frequently, e.g., printer, IP phone, etc.

[[File:Network lan staticleases.PNG]]

<table class="nd-mantable">
    <tr>
        <th>field name</th>
       	<th>value</th>
       	<th>description</th>
    </tr>
    <tr>
      	<td>Hostname</td>
       	<td>string; Default: " "</td>
       	<td>A custom name that will be linked with the device</td>
    </tr>
    <tr>
      	<td>MAC address</td>
       	<td>mac; Default: " "</td>
       	<td>Device’s MAC address</td>
    </tr>
    <tr>
    	<td>IP address</td>
        <td>ip; Default: " "</td>
        <td>The desirable IP address that will be reserved for the specified device</td>
    </tr>
</table>

==IPv6 Server Configuration==

[[File:Networking rut manual lan ipv6 server configuration.png|border|class=tlt-border]]

<table class="nd-mantable">
    <tr>
        <th>field name</th>
       	<th>value</th>
       	<th>description</th>
    </tr>
    <tr>
      	<td>DHCPv6 server</td>
       	<td>Enabled | Relayed | Disabled; Default: '''Enabled'''</td>
       	<td>State of DHCPv6 server</td>
    </tr>
    <tr>
      	<td>RA server</td>
       	<td>Enabled | Relayed | Disabled; Default: '''Enabled'''</td>
       	<td>State of Router Advertisement server</td>
    </tr>
    <tr>
      	<td>NDP server</td>
       	<td>Enabled | Relayed | Disabled; Default: '''Enabled'''</td>
       	<td>State of the Neighbour Discovery Protocol server</td>
    </tr>
 <tr>
      	<td>DHCPv6 server type</td>
       	<td>Stateless | Stateless + Stateful | Stateful; Default: '''Stateless'''</td>
       	<td>Type of router advertisements sent by the DHCPv6 server</td>
    </tr>
    <tr>
      	<td>DNS servers</td>
       	<td>string; Default: " "</td>
       	<td>DNS servers advertised by the DHCPv6 server</td>
    </tr>
    <tr>
      	<td>Domain names</td>
       	<td>string; Default: " "</td>
       	<td>Domain names advertised by the DHCPv6 server</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:Network lan ip alias general.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>
</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, a custom DNS server and Gateway for your IP Aliases in the Advanced Settings tab.

[[File:Network lan ip alias advanced.png]]

<table class="nd-mantable">
    <tr>
        <th>field name</th>
       	<th>value</th>
       	<th>description</th>
    </tr>
    <tr>
      	<td>IP 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>DNS</td>
       	<td>ip; Default: " "</td>
       	<td>A separate DNS server to be used by the IP Alias address</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>

==Relayd==

'''Relayd''' is a daemon to relay and dynamically redirect incoming connections to a target host. Its main purpose in RUT routers is extending the wireless network. For example, when RUT is in STA (Wireless Station) mode, it can be used to bridge WAN and LAN interfaces to create a larger Wireless network. You can find a detailed example on how to use Relayd '''[[Relayd|here]]'''.

[[File:Network lan relayd.png]]

<table class="nd-mantable">
    <tr>
        <th>field name</th>
       	<th>value</th>
       	<th>description</th>
    </tr>
    <tr>
      	<td>Enable</td>
       	<td>yes {{!}} no; Default: '''no'''</td>
       	<td>Toggles Relayd ON or OFF</td>
    </tr>
</table>

[[Category:RUT240 Network section (legacy)]]