Changes

Template:Networking rutos manual interfaces (view source)

Revision as of 19:47, 11 May 2020

25,373 bytes added ,  19:47, 11 May 2020
no edit summary
Line 33: Line 33:     
<ul>
 
<ul>
−
     <li><b>Ethernet LAN</b> - </li>
+
     <li><b>Ethernet LAN</b></li>
 
{{#ifeq: {{{eth}}} | 1
 
{{#ifeq: {{{eth}}} | 1
−
   |<li><b>Ethernet WAN</b> - </li>
+
   |<li><b>Ethernet WAN</b></li>
 
   |</ul>
 
   |</ul>
 
}}
 
}}
 
{{#ifeq: {{{modem}}} | 1
 
{{#ifeq: {{{modem}}} | 1
−
   |<li><b>Mobile WAN</b> - </li>
+
   |<li><b>Mobile WAN</b></li>
 
   |</ul>
 
   |</ul>
 
}}
 
}}
Line 101: Line 101:  
====General Setup====
 
====General Setup====
 
----
 
----
−
The <b>General Setup</b> section is used to configure the protocol and all the different parameters that go along with each protocol.
+
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.
    
=====General Setup: Static=====
 
=====General Setup: Static=====
Line 294: Line 294:  
</font>
 
</font>
 
|}}
 
|}}
 +
 
====Advanced Settings====
 
====Advanced Settings====
 
----
 
----
−
<b></b>
+
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=====
 +
----
 +
<b>Advanced Settings</b> information for <b>Static</b> protocol is provided in the table below.
 +
 
 +
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_static_v1.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bring up on boot</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built in IPv6-management</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>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>
 +
    <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>IPv6 assignment length</td>
 +
        <td>integer [0..64] | <span style="color: red;">disabled</span>; default: <b>60</b></td>
 +
        <td>Delegates a prefix of given length to the interface.</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: red;">IPv6 address</span></td>
 +
        <td>ip6; default: <b>none</b></td>
 +
        <td>The interface's IPv6 address. An IP address identifies a device on a network and allows it to communicate with other devices.<br><b>NOTE</b>: this field only becomes visible when IPv6 assignment length is set to disabled.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i></td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: red;">IPv6 gateway</span></td>
 +
        <td>ip6; default: <b>none</b></td>
 +
        <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color: red;">IPv6 routed prefix</span></td>
 +
        <td>ip6; default: <b>none</b></td>
 +
        <td>IPv6 prefix routed here for use on other interfaces.<br><b>Note:</b> this field only becomes visible when IPv6 assignment length is set to <i>disabled</i>.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IPv6 assignment hint</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>The subprefix-ID that should be delegated as hexadecimal number.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IPv6 suffix</td>
 +
        <td>ip6 suffix; default: <b>none</b></td>
 +
        <td>When an IPv6 prefix (like 'a:b:c:d::') is received from a delegating server, use a suffix (like '::1') to form an IPv6 address ('a:b:c:d::1') for the interface. Leave empty to generate a random suffix.</td>
 +
    </tr>
 +
</table>
 +
 
 +
=====Advanced Settings: DHCP=====
 +
----
 +
<b>Advanced Settings</b> information for <i>DHCP</i> protocol is provided in the table below.
 +
 
 +
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_dhcp_v1.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bring up on boot</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built-in IPv6 management</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use broadcast flag</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Required for certain ISPs. For example, Charter with DOCSIS 3.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use default gateway</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>When checked, creates a default route for the interface.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use DNS servers advertised by peer</td>
 +
        <td><span style="color: red;">off</span> | 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 | 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>Client ID to send when requesting DHCP</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>Client ID which will be sent when requesting a DHCP lease.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Vendor Class to send when requesting DHCP</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>Vendor class which will be sent when requesting a DHCP lease.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Override MAC address</td>
 +
        <td>mac; default: <b>none</b></td>
 +
        <td>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 [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=====
 +
----
 +
<b>Advanced Settings</b> information for <i>DHCPv6</i> protocol is provided in the table below.
 +
 
 +
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_dhcpv6_v1.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bring up on boot</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built in IPv6-management</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use default gateway</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>When checked, creates a default route for the interface.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use DNS servers advertised by peer</td>
 +
        <td><span style="color: red;">off</span> | 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 | 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>Custom delegated IPv6-prefix</span></td>
 +
        <td>ip6 prefix; default: <b>none</b></td>
 +
        <td>Uses an (additional) user-provided IPv6 prefix for distribution to clients.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Client ID to send when requesting DHCP</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>Client ID which will be sent when requesting a DHCP lease.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Override MAC address</td>
 +
        <td>mac; default: <b>none</b></td>
 +
        <td>When set, uses a user-defined MAC address for the interface.</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_interfaces_network_interfaces_lan_advanced_settings_pppoe_v1.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bring up on boot</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built-in IPv6 management</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Obtain IPv6 address</td>
 +
        <td>Automatic | Disabled | Manual; default: <b>Automatic</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use default gateway</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>When checked, creates a default route for the interface.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use gateway metric</td>
 +
        <td>integer; default: <b>none</b></td>
 +
        <td>A metric specifies the priority of the gateway. The lower the metric, the higher the priority (0 for highest priority).</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use DNS servers advertised by peer</td>
 +
        <td><span style="color: red;">off</span> | 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 | 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>LCP echo failure threshold</td>
 +
        <td>integer; default: <b>none</b></td>
 +
        <td>Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>LCP echo interval</td>
 +
        <td>integer; default: <b>none</b></td>
 +
        <td>Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Host-Uniq tag content</td>
 +
        <td>raw hex-encoded bytes; default: <b>none</b></td>
 +
        <td>Leave empty unless your ISP require this.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Inactivity timeout</td>
 +
        <td>mac; default: <b>none</b></td>
 +
        <td>Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Override MTU</td>
 +
        <td>integer [1..1500]; default: <b>none</b></td>
 +
        <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</td>
 +
    </tr>
 +
</table>
 +
{{#ifeq: {{{modem}}} | 1 |
 +
=====Advanced Settings: Mobile=====
 +
----
 +
<b>Advanced Settings</b> information for <i>Mobile</i> protocol is provided in the table below.
   −
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_v1.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_advanced_settings_mobile_v1.png|border|class=tlt-border]]
    +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bring up on boot</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether the interface should be launched during the boot process. If set to <i>off</i>, the interface would have to be brought up manually after each boot.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use built in IPv6-management</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Specifies whether to enable prefix delegation.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Force link</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Specifies whether interface settings (IP, route, gateway) are assigned to the interface regardless of the link being active or only after the link has become active.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Use DNS servers advertised by peer</td>
 +
        <td><span style="color: red;">off</span> | 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 | 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>|}}
 
====Physical Settings====
 
====Physical Settings====
 
----
 
----
−
<b></b>
+
The <b>Physical Settings</b> section is used to create associations with physical interfaces and bridge network interfaces.
−
 
  −
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_physical_settings_v1.png|border|class=tlt-border]]
      +
{{#ifeq: {{{series}}} | TRB14x
 +
| [[File:Networking_trb14x_manual_interfaces_network_interfaces_lan_physical_settings_v1.png|border|class=tlt-border]]
 +
| [[File:Networking_rutos_manual_interfaces_network_interfaces_lan_physical_settings_wifi_{{{wifi}}}_v1.png|border|class=tlt-border]]
 +
}}
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Bridge interfaces</td>
 +
        <td>off | on; default: <b>on</b></td>
 +
        <td>Bridges physical interfaces specified in this configuration.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable STP</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>Turns the use of Spanning Tree Protocol (STP) for this interface on or off.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Interface</td>
 +
        <td>network interface(s); default: <b>{{#ifeq:{{{series}}}|TRB14X|rndis0|eth0}}{{#ifeq:{{{wifi}}}|1| wlan0 wlan1|}}</b></td>
 +
        <td>Ties this network interface to physical device interfaces such as Ethernet{{#ifeq:{{{wifi}}}|1| or WiFi radios|}}.</td>
 +
    </tr>
 +
</table>
    
====Firewall Settings====
 
====Firewall Settings====
 
----
 
----
−
<b></b>
+
The <b>Firewall Settings</b> section is used to specify to which firewall zone if any this interface belongs.
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_firewall_settings_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_firewall_settings_v1.png|border|class=tlt-border]]
    +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Create / Assign firewall-zone</td>
 +
        <td>firewall zone; default: <b>lan</b></td>
 +
        <td>Assigns this interface to the specified firewall zone.</td>
 +
    </tr>
 +
</table>
    
===DHCP Server===
 
===DHCP Server===
 
----
 
----
−
<b></b>
+
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_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]
 +
 
 +
<u>In order to view the DHCP server configuration, the interface <b>protocol must be set to <i>Static</i></b></i>.</u>
    
====DHCP Server: General Setup===
 
====DHCP Server: General Setup===
 
----
 
----
−
<b></b>
+
The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_general_setup_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_general_setup_v1.png|border|class=tlt-border]]
    +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Enable DHCP</td>
 +
        <td>Enable | Disable | DHCP Relay<span class="asterisk">*</span>; default: <b>Enable</b></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>Start</td>
 +
        <td>integer [1..255]; default: <b>100</b></td>
 +
        <td>The starting IP address value. e.g., if your router’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>
 +
        <td>Limit</td>
 +
        <td>integer [1..255]; default: <b>150</b></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>
 +
        <td>Lease time</td>
 +
        <td>integer [2..999999]m/h; default: <b>12h</b></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.</td>
 +
    </tr>
 +
</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:
 +
 +
[[File:Networking_rutx_manual_lan_static_dhcp_server_relay_scheme_v2.png]]
    
====DHCP Server: Advanced Settings====
 
====DHCP Server: Advanced Settings====
 
----
 
----
−
<b></b>
+
Refer to the table below for information on the <b>Advanced Settings</b> section.
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_advanced_settings_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_advanced_settings_v1.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>off | on; default: <b>on</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>Force</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td>The DHCP force function ensures that the device will always start it’s DHCP server, even if there is another DHCP server already running in the its network. By default the device’s DHCP server will not start when it is connected to a network segment that already has a working DHCP server.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>IPv4 Netmask</td>
 +
        <td>netmask; default: <b>none</b></td>
 +
        <td>Sends a different netmask than the LAN netmask to DHCP clients.</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].</td>
 +
    </tr>
 +
</table>
    
====DHCP Server: IPv6 Settings====
 
====DHCP Server: IPv6 Settings====
 
----
 
----
−
<b></b>
+
Refer to the table below for information on the <b>IPv6 Settings</b> section.
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_ipv6_settings_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_dhcp_server_ipv6_settings_v1.png|border|class=tlt-border]]
    +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Router Advertisement Service</td>
 +
        <td>disabled | relay mode | server mode | 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 | relay mode | server mode | 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 | relay mode | hybrid mode; default: <b>Disabled</b></td>
 +
        <td>Specifies whether NDP should be relayed or disabled.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>DHCPv6 Mode</td>
 +
        <td>stateless | stateful-only | stateless + stateful; default: <b>stateless + stateful</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Always announce default router</td>
 +
        <td>off | on; default: <b>off</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Announced DNS server</td>
 +
        <td>ip; default: <b>none</b></td>
 +
        <td></td>
 +
    </tr>
 +
    <tr>
 +
        <td>Announced DNS domains</td>
 +
        <td>ip; default: <b>none</b></td>
 +
        <td></td>
 +
    </tr>
 +
</table>
    
===Static Lease===
 
===Static Lease===
 
----
 
----
−
<b></b>
+
<b>Static IP leases</b> 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.
 +
 
 +
This section displays static IP leases currently existing on this device.
 +
 
 +
<u>In order to view the Static Lease section, the interface <b>protocol must be set to <i>Static</i></b></i>.</u>
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_v1.png|border|class=tlt-border]]
−
      
====Static Lease: Settings====
 
====Static Lease: Settings====
 
----
 
----
−
<b></b>
+
To access a lease's <b>settings</b> page, click the 'Edit' button located to the right of the lease:
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_edit_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_edit_v1.png|border|class=tlt-border]]
   −
 
+
You should be directed to a window that looks like this:
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_settings_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_static_lease_settings_v1.png|border|class=tlt-border]]
    +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>MAC address</td>
 +
      <td>mac; default: <b>none</b></td>
 +
      <td>MAC address of a device that is on this interface's network.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>IP address</td>
 +
        <td>ip; default: <b>none</b></td>
 +
        <td>The IP address that will be reserved for the specified device.</td>
 +
    </tr>
 +
</table>
    
====Static Lease: Add Lease====
 
====Static Lease: Add Lease====
 
----
 
----
−
<b></b>
+
The <b>Add Lease</b> section is used to create new static leases. To create a new lease, simply enter a custom name for it and click the 'Add' button.
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_add_lease_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_add_lease_v1.png|border|class=tlt-border]]
−
 
+
{{#ifeq: {{{wifi}}} | 1 |
−
 
  −
 
   
===Relay Configuration===
 
===Relay Configuration===
 
----
 
----
−
<b></b>
+
The <b>Relay Configuration</b> section is used to relay and dynamically redirect incoming connections to a target host. Its main purpose is extending the wireless network. For example, when the device is in Wireless Station (client) mode, it can be used to bridge WAN and LAN interfaces to create a larger wireless network.<br>You can find a detailed usage example <b>[[Relayd|here]]</b>.
 +
 
 +
<u>In order to view the Relay Configuration section, the interface <b>protocol must be set to <i>Static</i></b></i>.</u>
    
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_relay_configuration_v1.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_interfaces_network_interfaces_lan_relay_configuration_v1.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enabled</td>
 +
      <td>off | on; default: <b>off</b></td>
 +
      <td>Turns the relay configuration on or off.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Interface</td>
 +
        <td>network interface; default: <b>none</b></td>
 +
        <td>Network interface associated with the relay configuration.</td>
 +
    </tr>
 +
</table>|}}
    
[[Category:{{{name}}} Services section]]
 
[[Category:{{{name}}} Services section]]
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/61976"

Navigation menu