Difference between revisions of "Template:Networking rutos manual lan"

From Teltonika Networks Wiki
(17 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
{{Template: Networking_device_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
−
| series = {{{series}}}
+
| fw_version ={{Template: Networking_rutos_manual_latest_fw
−
| name  = {{{name}}}
 
−
| fw_version ={{Template: Networking_device_manual_latest_fw
 
 
  | series = {{{series}}}
 
  | series = {{{series}}}
 
  | name  = {{{name}}}
 
  | name  = {{{name}}}
 
  }}
 
  }}
 
}}
 
}}
−
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
+
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
−
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
+
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} LAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
 
==Summary==
 
==Summary==
  
Line 15: Line 13:
 
This manual page provides an overview of the LAN windows in {{{name}}} devices.
 
This manual page provides an overview of the LAN windows in {{{name}}} devices.
  
−
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
+
==LAN Configuration==
−
| series = {{{series}}}
 
−
}}
 
  
−
==LAN==
+
The <b>LAN Configuration</b> section displays LAN interfaces currently existing on this device.
  
−
The <b>LAN</b> section displays LAN interfaces currently existing on this device.
+
{{#ifeq: {{{series}}} | TRB1
−
 
+
| [[File:Networking_trb14x_manual_lan_settings_v1.png|border|class=tlt-border]]
−
[[File:Networking_rutos_manual_lan_settings_v3.png|border|class=tlt-border]]
+
| [[File:Networking_rutos_manual_lan_settings_v1.png|border|class=tlt-border]]
−
 
+
}}
−
If you hover mouse over the question mark [[File:Networking_rutos_manual_wan_question_mark.png]] global IPv6 prefix assignment addresses will be displayed.
 
−
 
 
−
[[File:Networking_rutos_manual_lan_question_mark_info.png|border|class=tlt-border]]
 
−
 
 
−
The <b>Add New Instance</b> section is used to create additional network interfaces. To create a new interface, simply enter a custom name for it and click the 'Add' button.
 
−
 
 
−
[[File:Networking_rutos_manual_interfaces_add_interface_v2.png|border|class=tlt-border]]
 
  
 
To begin configuring an interface, click the 'Edit' button on the right side of the interface:
 
To begin configuring an interface, click the 'Edit' button on the right side of the interface:
  
−
[[File:Networking_rutos_manual_lan_begin_to_edit_v3.png|border|class=tlt-border]]
+
{{#ifeq: {{{series}}} | TRB1
 +
| [[File:Networking_trb14x_manual_lan_begin_to_edit_v1.png]]
 +
| [[File:Networking_rutos_manual_lan_begin_to_edit_v1.png]]
 +
}}
  
−
===Interface configuration===
+
===General Setup===
 
----
 
----
−
====General settings====
+
The <b>General Setup</b> section is used to configure the main parameters of LAN.
−
The <b>General Settings</b> section is used to configure the main parameters of LAN.
 
  
−
[[File:Networking_rutos_manual_lan_general_settings.png|border|class=tlt-border]]
+
{{#switch: {{{series}}}
 +
| TRB1 = [[File:Networking_trb14x_manual_lan_configuration_general_setup_v1.png|border|class=tlt-border]]
 +
| TRB2 = [[File:Networking_trb24x_manual_lan_configuration_general_setup_v1.png|border|class=tlt-border]]
 +
| #default = [[File:Networking_rutos_manual_lan_configuration_general_setup_v1.png|border|class=tlt-border]]
 +
}}
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 49: Line 44:
 
       <th>Value</th>
 
       <th>Value</th>
 
       <th>Description</th>
 
       <th>Description</th>
−
    </tr>
 
−
        <tr>
 
−
      <td>Enable</td>
 
−
      <td>off | on; default: <b>on</b></td>
 
−
      <td>Enable interface</td>
 
−
    </tr>
 
−
        <tr>
 
−
      <td>Protocol</td>
 
−
      <td>Static | None; default: <b>Static</b></td>
 
−
      <td></td>
 
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>IPv4 address</td>
 
       <td>IPv4 address</td>
−
       <td>ip4; default: <b>192.168.1.1</b></td>
+
       <td>ip4; default: <b>{{#ifeq:{{{series}}}|TRB1|192.168.2.1|192.168.1.1}}</b></td>
−
       <td>Your router's address on the network </td>
+
       <td>The IPv4 address interface of this interface. An IP address identifies a device on a network and allows it to communicate with other devices.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 69: Line 54:
 
       <td>netmask; default: <b>255.255.255.0</b></td>
 
       <td>netmask; default: <b>255.255.255.0</b></td>
 
       <td>The IPv4 netmask of this interface. A <b>[[What is a Netmask?|netmask]]</b> 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.</td>
 
       <td>The IPv4 netmask of this interface. A <b>[[What is a Netmask?|netmask]]</b> 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.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>IPv4 gateway</td>
 +
      <td>ip4; default: none</td>
 +
      <td>The IPv4 gateway address used by this interface. An interface's default gateway is the default address through which all outgoing traffic is directed.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>DNS servers</td>
 +
      <td>ip4; default: <b>none</b></td>
 +
      <td>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 <i>/tmp/resolv.conf.auto</i> file.</td>
 
     </tr>
 
     </tr>
 
{{#ifeq:{{{LAN_to_WAN}}}| 1 |
 
{{#ifeq:{{{LAN_to_WAN}}}| 1 |
Line 78: Line 73:
 
|}}
 
|}}
 
</table>
 
</table>
−
====IPV6 settings====
 
−
The <b>IPV6 settings</b> section is used to configure the IPv6 parameters of LAN.
 
−
 
−
[[File:Networking_rutos_manual_lan_ipv6_settings.png|border|class=tlt-border]]
 
−
 
−
<table class="nd-mantable">
 
−
    <tr>
 
−
        <th>Field</th>
 
−
      <th>Value</th>
 
−
      <th>Description</th>
 
−
    </tr>
 
−
        <tr>
 
−
      <td>Delegate IPv6 prefixes</td>
 
−
      <td>off | on; default: <b>on</b></td>
 
−
      <td>Enable downstream delegation of IPv6 prefixes available on this interface.</td>
 
−
    </tr>
 
−
    <tr>
 
−
      <td>IPv6 assignment length</td>
 
−
      <td>Disabled | 64 | Custom - integer [0..6]; default: <b>60</b></td>
 
−
      <td>Assign a part of given length of every public IPv6-prefix to this interface.</td>
 
−
    </tr>
 
−
    <tr>
 
−
      <td>IPv6 assignment hint</td>
 
−
      <td>A hexadecimal string of symbols: a-f, A-F and 0-9 is accepted; default: <b>none</b></td>
 
−
      <td>Assign prefix parts using this hexadecimal subprefix ID for this interface.</td>
 
−
    </tr>
 
−
        <tr>
 
−
      <td>IPv6 suffix</td>
 
−
      <td>Allowed values: "eui64", "random", fixed value like "::1" or "::1:2"; default: <b>none</b></td>
 
−
      <td>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.</td>
 
−
    </tr>
 
−
</table>
 
−
====Advanced settings====
 
−
The <b>Advanced settings</b> section is used to configure the advanced parameters of LAN.
 
−
 
−
[[File:Networking_rutos_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>Force link</td>
 
−
      <td>off | on; default: <b>on</b></td>
 
−
      <td>Set interface properties regardless of the link carrier (If set, carrier sense events do not invoke hotplug handlers).</td>
 
−
    </tr>
 
−
    <tr>
 
−
      <td>Use gateway metric</td>
 
−
      <td>integer [0..10000]; default: <b>0</b></td>
 
−
      <td>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.</td>
 
−
    </tr>
 
−
    <tr>
 
−
      <td>Override MAC address</td>
 
−
      <td>Mac address of six groups of two hexadecimal digits are accepted. E.g. 00:23:45:67:89:AB; default: <b>none</b></td>
 
−
      <td>Override MAC address of the 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 select your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer. You can select the MAC address of a currently connected computer, or use a custom one. When changing MAC address on LAN interface be careful to avoid MAC address collisions.</td>
 
−
    </tr>
 
−
        <tr>
 
−
      <td>Override MTU</td>
 
−
      <td>integer [98..65535]; default: <b>none</b></td>
 
−
      <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet.</td>
 
−
    </tr>
 
−
        <tr>
 
−
      <td>IP4 table</td>
 
−
      <td>Value must be a valid unsigned integer; default: <b>none</b></td>
 
−
      <td>IPv4 routing table for routes of this interface.</td>
 
−
    </tr>
 
−
</table>
 
−
====Physical settings====
 
−
The <b>Physical settings</b> section is used to configure the physical parameters of LAN.
 
−
 
−
[[File:Networking_rutos_manual_lan_physical_settings.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>Creates a bridge over specified interface(s).</td>
 
−
    </tr>
 
−
    <tr>
 
−
      <td>Enable STP</td>
 
−
      <td>off | on; default: <b>off</b></td>
 
−
      <td>Enables the Spanning Tree Protocol on this bridge.</td>
 
−
    </tr>
 
−
    <tr>
 
−
      <td>Enable IGMP</td>
 
−
      <td>off | on; default: <b>off</b></td>
 
−
      <td>Enables IGMP snooping on this bridge.</td>
 
−
    </tr>
 
−
        <tr>
 
−
      <td>Interface</td>
 
−
      <td>network interface(s); default: <b>lan physical interface</b></td>
 
−
      <td>Physical interface name to assign to this section, list of interfaces if type bridge is set.</td>
 
−
    </tr>
 
−
</table>
 
−
====Firewall settings====
 
−
The <b>Firewall settings</b> section is used to configure the firewall parameters of LAN.
 
−
 
−
[[File:Networking_rutos_manual_lan_firewall_settings.png|border|class=tlt-border]]
 
  
−
<table class="nd-mantable">
+
===DHCP Server===
−
    <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>Choose the firewall zone you want to assign to this interface. Select 'Unspecified' to remove the interface from the associated zone or define a new zone and attach the interface to it.</td>
 
−
    </tr>
 
−
</table>
 
−
===DHCP server configuration===
 
 
----
 
----
 
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.
 
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.
Line 202: Line 80:
 
[[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]
 
[[File:Networking_rutx_manual_lan_static_dhcp_server_scheme_v1.png]]
  
−
<i>To make the DHCP Server section visible, <b>set interface protocol to Static</b>.</i>
+
{{#ifeq: {{{series}}} | TRB1
−
 
+
| [[File:Networking_trb14x_manual_lan_configuration_dhcp_server_general_setup_v1.png|border|class=tlt-border]]
−
====General setup====
+
| [[File:Networking_rutos_manual_lan_configuration_dhcp_server_general_setup_v1.png|border|class=tlt-border]]
−
The <b>General Setup</b> section is used to set up the main operating parameters of the DHCP server.
+
}}
−
 
 
−
[[File:Networking_rutos_manual_lan_configuration_dhcp_server_general_setup.png|border|class=tlt-border]]
 
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 217: Line 93:
 
     <tr>
 
     <tr>
 
         <td>Enable DHCP</td>
 
         <td>Enable DHCP</td>
−
         <td>Enable | Disable | Relay<span class="asterisk">*</span>; default: <b>Enable</b></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>
 
         <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>
 
     <tr>
 
     <tr>
−
         <td>Start IP</td>
+
         <td>Start</td>
 
         <td>integer [1..255]; default: <b>100</b></td>
 
         <td>integer [1..255]; default: <b>100</b></td>
−
         <td>The DHCP server's IP address range start value.</td>
+
         <td>The starting IP address value. e.g., if your device’s LAN IP is 192.168.1.1 and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [192.168.1.0..192.168.1.254] (192.168.1.255 is a special unavailable address). If the Start value is set to 100 then the DHCP server will only lease out addresses starting from 192.168.1.<b>100</b>.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
         <td>End IP</td>
+
         <td>Limit</td>
−
         <td>integer [1..255]; default: <b>254</b></td>
+
         <td>integer [1..255]; default: <b>150</b></td>
−
         <td>End IP, i.e., the last possible IP in the selected range for the DHCP server.</td>
+
         <td>How many addresses the DHCP server can lease out. Continuing from the example above: if the start address is 192.168.1.100 and the server can lease out 150 addresses, available addresses will be from 192.168.1.<b>100</b> to 192.168.1.<b>249</b> (<i>100 + 150 – 1 = 249</i>; this is because the first address is inclusive).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Lease time</td>
 
         <td>Lease time</td>
−
         <td>integer [1..999999]; default: <b>12</b>integer [2..999999]<span class="asterisk">*</span>integer [120..999999]<span class="asterisk">**</span></td>
+
         <td>integer [1..999999]; default: <b>12</b></br>integer [2..999999]<span class="asterisk">*</span></br>integer [120..999999]<span class="asterisk">**</span></td>
−
         <td>A DHCP lease will expire after the amount of time specified in this field and the device that was using the lease will have to request a new one. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes (e.g., if lease time is 12 hours, then every 6 hours the device will ask the DHCP server to renew its lease).<br>The minimal amount of time that can be specified is 2 minutes.<br><span class="asterisk">*</span>If selected Units is Minutes.<br><span class="asterisk">**</span>If selected Units is seconds.</td>
+
         <td>A DHCP lease will expire after the amount of time specified in this field and the device that was using the lease will have to request a new one. However, if the device stays connected, its lease will be renewed after half of the specified amount of time passes (e.g., if lease time is 12 hours, then every 6 hours the device will ask the DHCP server to renew its lease).<br>The minimal amount of time that can be specified is 2 minutes.</br><span class="asterisk">*</span>If selected Units is Minutes.</br><span class="asterisk">**</span>If selected Units is seconds.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 239: Line 115:
 
         <td>Hours | Minutes | Seconds; default: <b>Hours</b></td>
 
         <td>Hours | Minutes | Seconds; default: <b>Hours</b></td>
 
         <td>Lease time measurement units.</td>
 
         <td>Lease time measurement units.</td>
−
    </tr>
 
−
</table>
 
−
====Advanced settings====
 
−
Refer to the table below for information on the <b>Advanced Settings</b> section.
 
−
 
−
[[File:Networking_rutos_manual_lan_configuration_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>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>Custom DHCP Options</td>
 
−
        <td>-(interactive button)</td>
 
−
        <td>Opens the edit window of DHCP options.</td>
 
−
    </tr>
 
−
    <tr>
 
−
        <td>Force DHCP options</td>
 
−
        <td>off | on; default: <b>off</b></td>
 
−
        <td>If enabled, DHCP options will be sent even if it's not requested.</td>
 
−
    </tr>
 
−
</table>
 
−
=====Custom DHCP options=====
 
−
Custom DHCP options are number and value pairs used to configure advanced DHCP functionality. It does not configure DHCP ipv6!. The <b>DHCP options</b> modal is used to 'Add', 'Delete', 'Save' multiple options.
 
−
 
−
[[File:Networking_rutos_manual_lan_configuration_dhcp_server_advanced_settings_dhcp_options.png|border|class=tlt-border]]
 
−
 
−
<table class="nd-mantable">
 
−
    <tr>
 
−
        <th>Field</th>
 
−
        <th>Value</th>
 
−
        <th>Description</th>
 
−
    </tr>
 
−
    <tr>
 
−
        <td>Option code</td>
 
−
        <td>Custom | Time offset (2) | Router (3) | DNS (6) | Domain name (15) | NTP server (43); default: <b>Time offset (2)</b></td>
 
−
        <td>Standartized DHCP option code.</td>
 
−
    </tr>
 
−
    <tr>
 
−
        <td>Option value</td>
 
−
        <td>Custom  | Time offset (2) - integer | Router (3)- IPv4 | DNS (6) - IPv4 | Domain name (15) - string | NTP server (43) - IPv4; default: <b>empty</b></td>
 
−
        <td>Value that will be set for selected option.</td>
 
−
    </tr>
 
−
</table>
 
−
 
−
====DHCP Server: IPv6 Settings====
 
−
----
 
−
Refer to the table below for information on the <b>IPv6 Settings</b> section.
 
−
 
−
[[File:Networking_rutos_manual_lan_configuration_dhcp_server_ipv6_settings.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>Announced DNS server</td>
 
−
        <td>ip; default: <b>none</b></td>
 
−
        <td>Supplements DHCP-assigned DNS server entries with ones specified in this field.</td>
 
−
    </tr>
 
−
    <tr>
 
−
        <td>Announced DNS domains</td>
 
−
        <td>ip; default: <b>none</b></td>
 
−
        <td>DNS domain handed out to DHCP clients.</td>
 
 
     </tr>
 
     </tr>
 
</table>
 
</table>

Revision as of 11:50, 19 May 2022

Template:Networking rutos manual fw disclosure


Summary

The LAN page is used to create and set up local area network interfaces.

This manual page provides an overview of the LAN windows in {{{name}}} devices.

LAN Configuration

The LAN Configuration section displays LAN interfaces currently existing on this device.

Networking rutos manual lan settings v1.png

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

Networking rutos manual lan begin to edit v1.png

General Setup

The General Setup section is used to configure the main parameters of LAN.

Networking rutos manual lan configuration general setup v1.png

Field Value Description
IPv4 address ip4; default: 192.168.1.1 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.
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.

DHCP Server

A DHCP (Dynamic Host Configuration Protocol) 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.

Networking rutx manual lan static dhcp server scheme v1.png

Networking rutos manual lan configuration dhcp server general setup v1.png

Field Value Description
Enable DHCP Enable | Disable | DHCP Relay*; default: Enable Turns the DHCP server on or off or enables DHCP relay*.
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 machine connects to this device, it will redirect any DHCP requests to the specified DHCP Server.
Start integer [1..255]; default: 100 The starting IP address value. e.g., if your device’s LAN IP is 192.168.1.1 and your subnet mask is 255.255.255.0 that means that in your network a valid IP address has to be in the range of [192.168.1.0..192.168.1.254] (192.168.1.255 is a special unavailable address). If the Start value is set to 100 then the DHCP server will only lease out addresses starting from 192.168.1.100.
Limit integer [1..255]; default: 150 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.100 to 192.168.1.249 (100 + 150 – 1 = 249; this is because the first address is inclusive).
Lease time integer [1..999999]; default: 12
integer [2..999999]*
integer [120..999999]**		 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).
The minimal amount of time that can be specified is 2 minutes.
*If selected Units is Minutes.
**If selected Units is seconds.
Units Hours | Minutes | Seconds; default: Hours Lease time measurement units.

* When an interface is set to act as a DHCP Relay, it redirects all received DHCP request messages to another specified DHCP server:

Networking rutx manual lan static dhcp server relay scheme v2.png

[[Category:{{{name}}} Network section]]

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_lan&oldid=91563"